Date: Mon, 24 Feb 2020 20:50:03 +0000 (UTC) From: Chris Ross <cross+freebsd@distal.com> To: Ruslan Mahmatkhanov <cvs-src@yandex.ru> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>, Chris Ross <cross+freebsd@distal.com> Subject: Re: Deluge port for FreeBSD Message-ID: <A073050F-54CA-4B42-9504-4A26DFAE0F19@distal.com> In-Reply-To: <AD1B370B-A5F0-437A-85A2-F97C323AD85E@distal.com> References: <511E2F3A-EC92-43D0-AB97-83F821DFAFA7@distal.com> <8525381582564848@myt2-a7d7570d35ff.qloud-c.yandex.net> <AD1B370B-A5F0-437A-85A2-F97C323AD85E@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Feb 24, 2020, at 14:21, Chris Ross <cross+freebsd@distal.com> wrote: >=20 > Okay. Well, I got it all running last fall. I see I have a "py36-libtor= rent-rasterbar" on my NetBSD 12 system. I'm not sure where it came from th= ough, but I'm sure it's something I installed as part of the deluge 2.0.3 e= ffort.=20 > py27-libtorrent-rasterbar-1.1.10_3 < > py36-libtorrent-rasterbar-1.1.10_5 ? >=20 > Updating my packages tree now, for the first time since Sept, I see that = py-libtorrent-rasterbar has been moved to 1.2, and py-libtorrent-rasterbar1= 1 is marked as broken. But, I did something in September to get one built = and installed. I don't have anything where I was building deluge-2.0.3. A= nd I have no changes to my deluge-2.0.3. >=20 > - Chris >=20 > ps, looking at the noted https://github.com/arvidn/libtorrent/issues/4204= something was merged on Jan 7 that someone reported fixing this issue for = FreeBSD. Okay. So, looking at the sources and the aforementioned "fix": That commi= t that fixes it for FreeBSD was merged into lib torrent-rasterbar, and shou= ld be available in version 1.2.4. Also, I applied the diff by hand to my s= ources of py-libtorrent-rasterber11 in the ports tree, and was able to get = it to install the shared library properly. I'm guessing the 1.1.10 version= didn't have that problem, but 1.1.14 and 1.2 did. Or, I did something sim= ilar to the 1.1.10_5 version of py-libtorrent-rasterbar in my tree and fail= ed to keep track of it. So, if deluge 2.0.x works with libtorrent-rasterbar 1.2 there's a clear pat= h forward. If it works with 1.1.x and not 1.2.x, it's more complicated. L= et me know how you can proceed after trying libtorrent-rasterbar 1.2.4. - Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A073050F-54CA-4B42-9504-4A26DFAE0F19>