On 30.09.2011 21:50, Rogério Brito wrote: > Hi, Kurt. > > Thank you very much for your feedback. It is really appreciated. > > 2011/9/30 Kurt Roeckx <k...@roeckx.be>: >> On Thu, Sep 29, 2011 at 08:55:14PM -0300, Rogério Brito wrote: >>> I will upload a new version of the combo libtorrent/rtorrent and they will >>> have the IPv6 support removed for the reason you mention and for breaking >>> compilation. >> >> I think I would rather see a package that only works on hosts that >> have ipv6 loaded than no ipv6 support at all. And I have a >> feeling I'm not the only one.
I would rather see a package which works in all cases. Uploading something that works just by a chance is wrong, and arguing which is better to break these or those installs is not a Debian Way. Just IMHO anyway. > OK, the package provided by upstream is not flexible enough, in the > sense that it doesn't have IPv6 supported and that others have > implemented patches, but are not supporting it (well, Steinar did take > the trouble of updating some times), but, right now, libtorrent > doesn't compile with the patch applied. > > (It may be truly trivial, but I have not see the cause of the > compilation errors). Can you show me the patches and versions you're trying to build? >> It should probably be easy to change the patch to do the right >> thing. Steinar can you take a look at that? > > Hopefully, if he does, I can keep it updated to Debian. But with one > catch: as I am only a lowly Debian Maintainer, I can't upload a new > version of libtorrent to the main archive by myself, as upstream has > changed the SONAME to libtorrent14 and DM's can't upload such a > package. > > Having my hands tied this way is a major bummer. > >> Which compilation issues are you talking about? I can't find >> any open bug report? > > Indeed, you can't. They are not present with the versions in Debian, > but they appeare with libtorrent that I would upload + Steinar's IPv6 > patch. I only discovered that yesterday, as I wanted to upload a new > version of rtorrent/libtorrent to the archive. > > But: > > http://identi.ca/notice/84342327 That one is easy, if we will find a solution to the problems I can sponsor the upload for you (I'm a DD). Your first upload was done by a sponsor too ;) >> So linux 3.x thing you mean is #635700. > > Yes, that's the one. Note that it didn't work before that change anyway, at least with the IPv6 patch applied. It needs more careful changes - as far as i can see, libtorrent is trying to open v6 or v4 socket without "telling" that to rtorrent, which tries to bind "some" addresss to it. The two needs to be coordinated obviously. >> Which also seems to be because the kernel doesn't have IPv6 support, and the >> code >> is then trying to do the wrong thing. > > Yes, but we lack a fix and upstream is not really responsive: > > http://thread.gmane.org/gmane.linux.network/199373 > >>> But I'm using rtorrent less and less, as my primary bittorrent client is, >>> right now, qbittorrent. >> >> Please consider an request for adoption or orphaning the package >> if you feel you don't want to maintain it anymore. > > I'm not exactly sure if we need to orphan the package, as it 3 current > maintainers: 2 DDs (ghostbar and unera), and 1 DM (me). Especially as the package has 2 more maintainers. > I told ghostbar that I planned the past upload of libtorrent/rtorrent > to be my last ones of this package, but as he was busy with school, I > waited so that the package should have at least some support. > > So, summarizing the various points here: > > * Despite me having a half prepared upload in our git trees (which, > BTW, I am already using myself), I can't upload it... It may have been > past the time for me to become a DD, it seems. > * Upstream has not given many signs of life and the project seems moribund. > * We have patches from the community, but they are not integrated in > the main project, which means that they are very likely to break from > update from update, unless the project is forked. > * The other maintainers of the package seem to be busy. > > Further feedback is appreciated. The first step - just in my opinion anyway - is to understand what's up with the upstream. The fact that the project shows no signs of life is not good... :( Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
