<quote who="Thomas Goirand" date="Mon, Mar 17, 2014 at 07:42:44PM +0800"> > You still didn't reply to this message. #740311 was submited on the 28 > Feb 2014 (18 days ago), and #738327 on the Sun, 09 Feb (37 days ago), > and you replied to none of them.
I'm sorry for the slow response Thomas. Thank you for patience and for your help and interest in the package. I've looked at both the open bugs. #740311 is bug. I haven't looked at the patch (I am catching up on my volunteer software work now while offline) but I assume if it is a minimal change and it fixes an important issue with the package, go ahead and prepare an NMU fixing it. Of course, I'd like make sure that upstream has the patch but if it's been forwarded on (or applied), I don't object to applying the patch here at all. In terms of #738327, I'm not wild about gutting CDBS and essentially redoing the package because you're not familiar with how to handle Python3 support. I don't love the idea of NMUs that redo the entire package because the person doing the NMU is not familiar with the packaging software used. It seems like to a lot to change to a relatively simple and stable package for something that is likely unnecessary. I should be able to get around preparing a package this week. If you want to prepare a minimal fix for the Python 3 issue, I've got no problems with that either. > If you don't have time for this package, would you agree that I NMU it, > and set the Python module team as Maintainer: ? Or maybe just add me as > Uploaders: for the package? I'm happy for to add you as uploader for the package. Later, Mako -- Benjamin Mako Hill http://mako.cc/ Creativity can be a social contribution, but only in so far as society is free to use the results. --GNU Manifesto
signature.asc
Description: Digital signature
