Re: Deluge port for FreeBSD
Yes, thanks, I saw that today. Next I was asking for feedback from Ruslan on net-p2p/deluge and peers. Thanks, Yuri. - Chris > On Mar 27, 2020, at 21:06, Yuri wrote: > > On 2020-03-02 13:33, Chris Ross wrote: >> Yuri, will you be able to un-BROKEN net-p2p/py-libtorrent-rasterbar sometime >> soon? From reading and my own testing, version 1.2.4 does not have the >> "doesn't install any files" problem that earlier releases did on FreeBSD. >> Fixing that port will also allow deluge to be updated. > > > net-p2p/py-libtorrent-rasterbar isn't currently labeled BROKEN. Please update > your ports tree. > > > Yuri > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Deluge port for FreeBSD
On 2020-03-02 13:33, Chris Ross wrote: Yuri, will you be able to un-BROKEN net-p2p/py-libtorrent-rasterbar sometime soon? From reading and my own testing, version 1.2.4 does not have the "doesn't install any files" problem that earlier releases did on FreeBSD. Fixing that port will also allow deluge to be updated. net-p2p/py-libtorrent-rasterbar isn't currently labeled BROKEN. Please update your ports tree. Yuri ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Deluge port for FreeBSD
> On Feb 24, 2020, at 12:20, Ruslan Mahmatkhanov wrote: > > Hello. > > 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 > working python binding for libtorrent-rasterbar. I can't test w/o it. Hello again. I wanted to inquire as to whether there have been any progress on updating the ports tree to deluge 2. It looks like libtorrent-rasterbar (and py-libtorrent-rasterbar) should be available now. Thank you. - Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Deluge port for FreeBSD
Yuri, will you be able to un-BROKEN net-p2p/py-libtorrent-rasterbar sometime soon? From reading and my own testing, version 1.2.4 does not have the "doesn't install any files" problem that earlier releases did on FreeBSD. Fixing that port will also allow deluge to be updated. - Chris > On Feb 24, 2020, at 16:19, Chris Ross wrote: > > +yuri > >> On Feb 24, 2020, at 15:50, Chris Ross wrote: >>> >>> 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. > > It looks like there are a few changes in libtorrent 1.2, > https://www.libtorrent.org/upgrade_to_1.2-ref.html > > I notice that net-p2p/libtorrent-rasterbar has already been updated to 1.2.4. > I think this means that the python module would work now if similarly > updated. > > Also, I notice that according to the 1.2 release notes, boost has been > replaced by std, but both libtorrent-rasterbar and py-libtorrent-rasterbar > still seem to require boost. Is this an oversight, or am I misreading > https://www.libtorrent.org/upgrade_to_1.2-ref.html ? > > Thanks! > > - Chris > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Deluge port for FreeBSD
+yuri > On Feb 24, 2020, at 15:50, Chris Ross wrote: >> >> 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. It looks like there are a few changes in libtorrent 1.2, https://www.libtorrent.org/upgrade_to_1.2-ref.html I notice that net-p2p/libtorrent-rasterbar has already been updated to 1.2.4. I think this means that the python module would work now if similarly updated. Also, I notice that according to the 1.2 release notes, boost has been replaced by std, but both libtorrent-rasterbar and py-libtorrent-rasterbar still seem to require boost. Is this an oversight, or am I misreading https://www.libtorrent.org/upgrade_to_1.2-ref.html ? Thanks! - Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Deluge port for FreeBSD
> On Feb 24, 2020, at 14:21, Chris Ross 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Deluge port for FreeBSD
> On Feb 24, 2020, at 12:20, Ruslan Mahmatkhanov wrote: > > Hello. > > 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 > working python binding for libtorrent-rasterbar. I can't test w/o it. 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. :-) I see: : pkg ver | grep torrent libtorrent-0.13.8 = libtorrent-rasterbar-1.1.10_5 < mktorrent-1.1_1= 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. Maybe I'll have to get back to it. Contact me off-list and I can start with 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=NK1UM1m88Y-2BE3GDttDA4-2B-2BOY87hLcDtmHUYa8fuR44Alybx4gVVkXMtZYKqSk6o9saqFKg5ZAkGVcKtzxZzY6g-3D-3DbjLL_oHh3B724HUwoeDcrGdlJYVhOCvY4lcmdpia5Yeq194ykkKcAt751VYpCC-2B5Ia-2FNIERE7T-2Fm7pprfBwrUQG91zj0SZZco7Q3S4GSGkH6hqqGeVpv6h1QBrY62Psi-2Bb80w80-2F7CVw0EWmRtfzw9bZrFrORjiSF-2BFibTaomrBdeSmFqhiIXtG-2BgY6DeeRlJCrgC5IOHOw6olGIM4tKXXxdkGxWjf-2Fw3Illh4BlqJEZu4Bl7s-2BOJpu8xUQgFd01hdiSh something was merged on Jan 7 that someone reported fixing this issue for FreeBSD. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Deluge port for FreeBSD
Hello. 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 working python binding for libtorrent-rasterbar. I can't test w/o it. 24.02.2020, 19:25, "Chris Ross" : > Hello all. Deluge 2.0 was created last year, using python3. I had been > waiting for a new deluge2 port to be added, but now see that there is still > not one, and the older deluge 1.3.15 has been deprecated because it uses > EOL'd python27. > > https://u13739864.ct.sendgrid.net/ls/click?upn=NK1UM1m88Y-2BE3GDttDA4-2B3fqjRJC5obnVcxBoDcVoxzMpqQ5fXed7CIe-2BZ9zBquSgpV9kT30uAqWmsOEueNQ0A-3D-3DGmIa_9P-2FllkRu-2FgTZT7WocElCz837oGdJ-2B6luy3Bd6fimbL3hTyzkfScBrUZCuZUQZxKZUtc79JL-2B0lHQcwbTZoXEeIdUwUsZpOzVH30kx1-2FnK2BtKYoEvpACa64FcprVnGtU2e9L1gzy-2BUhOf8GprFRoBQo8xIlzRWft9BaD8CxCDC1wR7yZkyOcDmb-2F9UgY4jke-2BEwJ18Myl3U25VrhVe8KTzYeb02I3PF8nGJ3q0it1ks-3D > > Ruslan, as the maintainer of the prior port, any possibility you could put > together a new port for deluge2? Myself and another tested getting it running > on FreeBSD 12 last year, so it's known compatible. > > https://u13739864.ct.sendgrid.net/ls/click?upn=NK1UM1m88Y-2BE3GDttDA4-2BwlxOo-2FihJSFnPbu5Az7R876WPbQ9QyFOmGgDze3zWWMpO7d-2FIlxFxh1tB1u4GzDSLsDaMmPix-2BurwC1hoK14A8-3DOSw2_9P-2FllkRu-2FgTZT7WocElCz837oGdJ-2B6luy3Bd6fimbL3hTyzkfScBrUZCuZUQZxKZm1ctgbVOOGgXQ6KdrsNsKqXUJtWdFeoqrrWlBn-2BlHq0EVJXlQH4lAuXbE5vV0MIcgQSNTFdLVw5ugoMItmgCxCy7WTGsYNpD-2FH0VvZp7bN45K6-2FD7-2FizKLkAr6TWz6q4-2FeersOVVGJZ4m-2BM9K-2BiJzddANltTFKtdN-2F7Uk0uowb8-3D > > Thanks all. > > - Chris -- Regards, Ruslan ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Deluge port for FreeBSD
Hello all. Deluge 2.0 was created last year, using python3. I had been waiting for a new deluge2 port to be added, but now see that there is still not one, and the older deluge 1.3.15 has been deprecated because it uses EOL'd python27. https://u13739864.ct.sendgrid.net/ls/click?upn=NK1UM1m88Y-2BE3GDttDA4-2B3fqjRJC5obnVcxBoDcVoxzMpqQ5fXed7CIe-2BZ9zBquSgpV9kT30uAqWmsOEueNQ0A-3D-3DjOKj_oHh3B724HUwoeDcrGdlJYVhOCvY4lcmdpia5Yeq194zH75eqL5mjSHDpwQeThJBvdFuNLxEHMyTEmCB3kZiYtkQxg614Xn55vI21c7EQSMyBaQdh1ndg8cVfDo31TRv-2FiWUvXCz5XNxzaZTeOqqagoLkqdwdy02Y6DwcnCqVn2pEb7ZWWyz-2FVj5T-2F3RCGpWSIUHQixQcyvPXHrWTB6hwPZfdHkoSXqoYRtdlUu5KLIlTL2yIYh8SZuTCrEotcFlE Ruslan, as the maintainer of the prior port, any possibility you could put together a new port for deluge2? Myself and another tested getting it running on FreeBSD 12 last year, so it's known compatible. https://u13739864.ct.sendgrid.net/ls/click?upn=NK1UM1m88Y-2BE3GDttDA4-2BwlxOo-2FihJSFnPbu5Az7R876WPbQ9QyFOmGgDze3zWWMpO7d-2FIlxFxh1tB1u4GzDSLsDaMmPix-2BurwC1hoK14A8-3DHISj_oHh3B724HUwoeDcrGdlJYVhOCvY4lcmdpia5Yeq194zH75eqL5mjSHDpwQeThJBvdFuNLxEHMyTEmCB3kZiYtmAT-2FwyQNy4sYYggfTnAP-2FuQKl26uKOgsurk-2FkNyF1HQz8j11ylodameVUFWSBWhwAh5C47rxf6hsKYj4RAXpAClwUGDFrzz-2FehHq-2FIQEI2y6o8wuwPEjCTgjWLjA-2B-2BShbGbhEH8s6CPyk3WGN7OVSmx6-2B-2F2xWFTrK-2BcB5AFRYU8 Thanks all. - Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
