Dear Benoît, On Mon, May 7, 2012 at 6:21 PM, Benoît Knecht <benoit.kne...@fsfe.org> wrote: > A few months ago, after I did some triaging on rtorrent's bugs, Rogério > asked if I was interested in helping out with the package's maintenance. > I said yes, but after that nothing really happened (I think a few mails > were lost between him and me, and I haven't insisted since).
First of all, I am very sorry to not have replied earlier. In the past 2 months I have barely slept, since my wife was in the end of her pregnancy (with all the troubles that this emcompasses) and now our son is sucking all of our time (including our time to sleep). Second, you should have insisted. :) I would have sent you an status update earlier. :) > But at the > time, I took a shot at packaging what was then the unstable version of > rtorrent, and put the result on gitorious [1,2] (in a debian/0.9.0 > branch for rtorrent, and a debian/0.13.0 branch for libtorrent). > > [1] git://gitorious.org/debian-pkg/rtorrent.git > [2] git://gitorious.org/debian-pkg/libtorrent.git I am looking at your packaging of rtorrent right now and it is very good, with just one observation: to be more consistent with what has been done and also to be more consistent with what tools like git-buildpackage expect, it would be good we kept the following things: * the upstream source in the upstream branch (automatically done when you call git-import-orig). * the potential differences in a tarball taken from upstream and what is generated from the upstream branch in a branch called pristine-tar (automatically done when you call git-import-orig --pristine-tar). * the specific debian changes in the master branch of the repository. Then, debian/0.9.0-1 or someting would change from being branches to being tags (automatically done when you call git-buildpackage --git-pristine-tar --git-tag). Tags like upstream/0.9.0 will be automatically created by the previous calls to git-import-orig. Can you do those changes? If you don't, then I think that I can. > Now that 0.9.2/0.13.2 is out and considered stable upstream, I've > packaged it for unstable (essentially just imported the new upstream > version on top of my 0.9.0/0.13.0 package) and put it on gitorious as > well (branches debian/0.9.2 and debian/0.13.2). Superb. > It compiles and runs fine on amd64 at least, and fixes the following > bugs: > > * http://bugs.debian.org/667361 > ftbfs with GCC-4.7 > (apparently fixed upstream, no patch was required) > * http://bugs.debian.org/649959 > log.execute option doesn't work > (fixed in 0.9.0 already) > * http://bugs.debian.org/671582 > Please enable hardening build flags > (fixed by using debhelper compat 9) Excellent. > I'd be glad if someone could take a look and perhaps merge it on alioth > and upload it. If everything's fine, please consider adding me as an > uploader (I'm not a DM, so I'd still need someone to sponsor my uploads) > and let me join collab-maint [3] (I need a DM or DD to send an email to > n...@debian.org; my username is bknecht-guest). I'm sending this e-mail asap, as I think that your job is indeed a very good fit for the improvement of {r,lib}torrent in Debian. > [3] http://lists.debian.org/debian-devel-announce/2012/01/msg00006.html > > Thanks in advance. Thanks -- Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/ DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
