Please stabilize.
Fine for me. Only problem is that rb_libtorrent-1.0.10 is not stable. I'm quite sure we can change back the dependency to >=net-libs/rb_libtorrent-0.16.17 without any ill effects. Kristian, do you want a patch, or is it trivial enough and you can do it on your own?
(In reply to Paolo Pedroni from comment #1) > Fine for me. Only problem is that rb_libtorrent-1.0.10 is not stable. I'm Is there a problem with making it stable as part of the process? > quite sure we can change back the dependency to > >=net-libs/rb_libtorrent-0.16.17 without any ill effects. keep in mind that such a change will restart the count of package in ~arch for 30 days before stabilization so you might want to consider option #1 above. > > Kristian, do you want a patch, or is it trivial enough and you can do it on > your own? If going this route; patch please :) (remember to revbump) NB! I've run into certain issues with configuration getting lost on update and difficulties starting deluged (it is OK from the web interface, but not from init scripts). I haven't had time / bothered to debug this properly, but it should certainly be handled before stabilization (or at least properly tested to verify if it is specific to my setup).
(In reply to Kristian Fiskerstrand from comment #2) > (In reply to Paolo Pedroni from comment #1) > > Fine for me. Only problem is that rb_libtorrent-1.0.10 is not stable. I'm > > Is there a problem with making it stable as part of the process? rb_libtorrent mantainer (hwoarang) is quite slow to respond. There's a couple of security bug (#585278 and #593288) and a version bump (#580760) open for the package with no response from him yet. Were it for me, I'd wait for rb_libtorrent-1.1.1 to show up and stabilize that in due course, or patch 1.0.10 for #593288.
(In reply to Kristian Fiskerstrand from comment #2) > (In reply to Paolo Pedroni from comment #1) > > quite sure we can change back the dependency to > > >=net-libs/rb_libtorrent-0.16.17 without any ill effects. > > keep in mind that such a change will restart the count of package in ~arch > for 30 days before stabilization so you might want to consider option #1 > above. At this point, it's fine for me, and I'll fix bug #602424 at the same time. Expect a patch in the next few days, work permitting. > NB! I've run into certain issues with configuration getting lost on update > and difficulties starting deluged (it is OK from the web interface, but not > from init scripts). I haven't had time / bothered to debug this properly, > but it should certainly be handled before stabilization (or at least > properly tested to verify if it is specific to my setup). Never happened to me, and no trace of currently open bugs regarding this at the time. If you can debug it more, please let me know.
Created attachment 456290 [details, diff] 0002-net-p2p-deluge-Fix-dependency-on-net-libs-rb_libtorr.patch This patch reverts the dependency on net-libs/rb_libtorrent to current stable and beyond and revbumps the package accordingly. In 30 days I'll send a patch to stabilize it if no bugs crop up. I changed the dependency for all other unstable ebuilds too, for uniformity's sake. Kristian, please review and apply.
Sorry to bother you again, Kristian, but when you fixed bug #602424, you forgot to apply the patch in this bug to revert the dependency on rb_libtorrent to the older, stable version. Can you please do it? Thanks in advance.
Dear Maintainer (or who is mainly involved in this stable request), This is an auto-generated message that will move the current component to the new component Stabilization. To ensure that the stabilization will proceed correctly, please fill the fields "Atoms to stabilize" and "Runtime testing required" as described here: https://archives.gentoo.org/gentoo-dev/message/4b2ef0e9aa7588224b8ae799c5fe31fa
(In reply to Paolo Pedroni from comment #6) > Sorry to bother you again, Kristian, but when you fixed bug #602424, you > forgot to apply the patch in this bug to revert the dependency on > rb_libtorrent to the older, stable version. Can you please do it? > > Thanks in advance. Please, Kristian, apply the attached patch which reverts the dependency on newer, unstable rb_libtorrent, so we can proceed with stabilization in due course. Thanks.
(In reply to Paolo Pedroni from comment #8) > (In reply to Paolo Pedroni from comment #6) > > Sorry to bother you again, Kristian, but when you fixed bug #602424, you > > forgot to apply the patch in this bug to revert the dependency on > > rb_libtorrent to the older, stable version. Can you please do it? > > > > Thanks in advance. > > Please, Kristian, apply the attached patch which reverts the dependency on > newer, unstable rb_libtorrent, so we can proceed with stabilization in due > course. > > Thanks. The patch renames 1.3.13 to 1.3.13-r1, however this revision already exists, so I applied the fix manually for 1.3.13-r2. 1.3.12 should be removed once stabilization of this is done, so not needed to do anything about, the -9999 versions can't go stable so likely no reason to downgrade here. commit 6e64dbcb7789e65ba12420a0369dc0de61640663 Author: Kristian Fiskerstrand <k_f@gentoo.org> Date: Thu Jan 5 20:11:07 2017 +0100 net-p2p/deluge: Fix dependency on net-libs/rb_libtorrent. The newer version of the library is not strictly necessary and requires additional stabilization if to be used, so reducing the version requirement for 1.3.13 in order to stabilize the point version. Proxied-Maintainer: Paolo Pedroni Gentoo-Bug: 601048 Package-Manager: Portage-2.3.3, Repoman-2.3.1
All the packages need to go together in bug 530720 *** This bug has been marked as a duplicate of bug 530720 ***
