In file included from web_connection_base.cpp:44: In file included from ../include/libtorrent/web_connection_base.hpp:56: ../include/libtorrent/peer_connection.hpp:910:3: error: incomplete type 'boost::asio::io_service' named in nested name specifier io_service::work m_work; ^~~~~~~~~~~~ ../include/libtorrent/io_service_fwd.hpp:57:8: note: forward declaration of 'boost::asio::io_service' class io_service; ^ [...] http://package22.nyi.freebsd.org/data/103amd64-default-PR223922/2017-12-02_11h06m39s/logs/errors/libtorrent-rasterbar-1.1.4_3.log http://package23.nyi.freebsd.org/data/103i386-default-PR223922/2017-12-02_11h06m37s/logs/errors/libtorrent-rasterbar-1.1.4_3.log
Upstream fix is incomplete (refer to See Also link). I plan to mark this port BROKEN. Unless other bustage is decimated this will probably happen at the start of 2018Q1 to avoid spoiling /quarterly.
Fixed upstream in libtorrent to 1.1.6.
Created attachment 189070 [details] update to 1.1.5.41 (RC_1_1 snapshot) This is what I've used to help upstream with testing. Just in case 1.1.6 is not released after bug 223922 lands. - LOGGING enabled by default per https://github.com/arvidn/libtorrent/commit/e36b06602067
Created attachment 189328 [details] update to 1.1.6 (commit message included) 2018Q1 has branched in ports r457769, so I'm just waiting for a more recent exp-run before marking everything not fixed as BROKEN. OTOH, 1.1.6 is out: https://github.com/arvidn/libtorrent/releases/tag/libtorrent-1_1_6 Build logs for libtorrent-rasterbar: 10.3 amd64 - https://clbin.com/LZgaG 10.3 i386 - https://clbin.com/OYnZv 10.4 amd64 - https://clbin.com/OosbH 10.4 i386 - https://clbin.com/WJWxt 11.1 aarch64 - https://clbin.com/AY2xi 11.1 amd64 - https://clbin.com/8OHLZ 11.1 armv6 - https://clbin.com/NVTS2 11.1 i386 - https://clbin.com/DLDYx 12.0 amd64 - https://clbin.com/GtUIc 12.0 armv6 - https://clbin.com/nPxTU 12.0 armv7 - https://clbin.com/cdbL9 12.0 i386 - https://clbin.com/mHUdr 12.0 aarch64 - https://clbin.com/VYI3V Build logs for libtorrent-rasterbar-python: 10.3 amd64 - https://clbin.com/ymzcr 10.3 i386 - https://clbin.com/Ao8v9 10.4 amd64 - https://clbin.com/dPSpD 10.4 i386 - https://clbin.com/Xa44e 11.1 aarch64 - https://clbin.com/11T7X 11.1 amd64 - https://clbin.com/e4Epw 11.1 armv6 - https://clbin.com/rhNIi 11.1 i386 - https://clbin.com/i8rDm 12.0 amd64 - https://clbin.com/GldGt 12.0 armv6 - https://clbin.com/EI3Vm 12.0 armv7 - https://clbin.com/ETY3v 12.0 i386 - https://clbin.com/IVbSz 12.0 aarch64 - https://clbin.com/DsCFp Build logs for qbittorrent: 10.3 i386 - https://clbin.com/ezEJK 11.1 amd64 - https://clbin.com/bIhZd
No feedback and no runtime QA. Do maintainers of consumer ports care?
Thank you for the patch.
Does 1.1.6 work for you? I'm not confident to land under maintainer timeout otherwise.
Confirmed: qbittorrent-4.0.2 works fine with this patch.
A commit references this bug: Author: jbeich Date: Thu Jan 18 18:27:26 UTC 2018 New revision: 459367 URL: https://svnweb.freebsd.org/changeset/ports/459367 Log: net-p2p/libtorrent-rasterbar: update to 1.1.6 - LOGGING is now enabled by default, following upstream, see https://github.com/arvidn/libtorrent/commit/e36b06602067 Changes: https://github.com/arvidn/libtorrent/releases/tag/libtorrent-1_1_5 Changes: https://github.com/arvidn/libtorrent/releases/tag/libtorrent-1_1_6 Changes: https://github.com/arvidn/libtorrent/compare/libtorrent-1_1_4...libtorrent-1_1_6 PR: 224060 Tested by: yuri Approved by: maintainer timeout (2 weeks) Changes: head/net-p2p/libtorrent-rasterbar/Makefile head/net-p2p/libtorrent-rasterbar/distinfo head/net-p2p/libtorrent-rasterbar/files/patch-include_libtorrent_config.hpp