Date: Mon, 24 Feb 2020 19:21:37 +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> Subject: Re: Deluge port for FreeBSD Message-ID: <AD1B370B-A5F0-437A-85A2-F97C323AD85E@distal.com> In-Reply-To: <8525381582564848@myt2-a7d7570d35ff.qloud-c.yandex.net> References: <511E2F3A-EC92-43D0-AB97-83F821DFAFA7@distal.com> <8525381582564848@myt2-a7d7570d35ff.qloud-c.yandex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Feb 24, 2020, at 12:20, Ruslan Mahmatkhanov <cvs-src@yandex.ru> wrote:
>=20
> Hello.=20
>=20
> I'm holding deluge2 port, that is supposed to work and that needs testing=
before pushing to ports tree. But as far I understand there is still no wo=
rking python binding for libtorrent-rasterbar. I can't test w/o it.=20
Okay. Well, I got it all running last fall. I see I have a "py36-libtorre=
nt-rasterbar" on my NetBSD 12 system. I'm not sure where it came from thou=
gh, but I'm sure it's something I installed as part of the deluge 2.0.3 eff=
ort. :-)
I see:
: pkg ver | grep torrent
libtorrent-0.13.8 =3D
libtorrent-rasterbar-1.1.10_5 <
mktorrent-1.1_1 =3D
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 an=
d 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.
Maybe I'll have to get back to it. Contact me off-list and I can start wit=
h what you had ready and I'll try to see what it takes to get it running...
- Chris
ps, looking at the noted https://u13739864.ct.sendgrid.net/ls/click?upn=3DN=
K1UM1m88Y-2BE3GDttDA4-2B-2BOY87hLcDtmHUYa8fuR44Alybx4gVVkXMtZYKqSk6o9saqFKg=
5ZAkGVcKtzxZzY6g-3D-3DbjLL_oHh3B724HUwoeDcrGdlJYVhOCvY4lcmdpia5Yeq194ykkKcA=
t751VYpCC-2B5Ia-2FNIERE7T-2Fm7pprfBwrUQG91zj0SZZco7Q3S4GSGkH6hqqGeVpv6h1QBr=
Y62Psi-2Bb80w80-2F7CVw0EWmRtfzw9bZrFrORjiSF-2BFibTaomrBdeSmFqhiIXtG-2BgY6De=
eRlJCrgC5IOHOw6olGIM4tKXXxdkGxWjf-2Fw3Illh4BlqJEZu4Bl7s-2BOJpu8xUQgFd01hdiS=
h something was merged on Jan 7 that someone reported fixing this issue for=
FreeBSD.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AD1B370B-A5F0-437A-85A2-F97C323AD85E>