> On Feb 24, 2020, at 14:21, Chris Ross <[email protected]> wrote:
>
> Okay. Well, I got it all running last fall. I see I have a
> "py36-libtorrent-rasterbar" on my NetBSD 12 system. I'm not sure where it
> came from though, but I'm sure it's something I installed as part of the
> deluge 2.0.3 effort.
> py27-libtorrent-rasterbar-1.1.10_3 <
> py36-libtorrent-rasterbar-1.1.10_5 ?
>
> 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-rasterbar11
> 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. And I
> have no changes to my deluge-2.0.3.
>
> - Chris
>
> 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 commit
that fixes it for FreeBSD was merged into lib torrent-rasterbar, and should be
available in version 1.2.4. Also, I applied the diff by hand to my sources 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 similar to the 1.1.10_5
version of py-libtorrent-rasterbar in my tree and failed to keep track of it.
So, if deluge 2.0.x works with libtorrent-rasterbar 1.2 there's a clear path
forward. If it works with 1.1.x and not 1.2.x, it's more complicated. Let me
know how you can proceed after trying libtorrent-rasterbar 1.2.4.
- Chris
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
