hi. > The dpatch patch management system has been deprecated for some time. The > Lintian currently flags use of dpatch packages as an error. The new 3.0
Sorry, but I DO NOT CARE. Dpatch works well and will be maintained for some time, in the worst case because some friends and me are going to maintain it. Until quilt knows about how to work with svn-buildpackage and to merge sources while editing a patch, dpatch will stay. > packaging format is an improved version which, among other things, contains > patch management built-in. For more information, see: > > http://wiki.debian.org/Projects/DebSrc3.0 > > I had some free time; see attached patch to migrate to new package > format. Note that all files in debian/patches/* are canocalized to > *.patch. Thanks but - NO WAY. There is absolutely NO reason to convert something to source format 3.0. Not only but also for reasons mentioned above. > Let me know if there is anything that needs adjusting or if it is ok > to upload this version in a NMU in case you are working on other > issues needing attention. Opening a bug which does cosmetic fixes is nothing that needs a NMU. Also the way you've introduced dh_python2 is completely WRONG. You should learn about how dh_python2 works before you start to mess with it. hint: read the manpage or the documentation in the wiki. See what it does and what it requires. I've taken some of the ideas from your patch, thanks for proposing them. But please refrain from reopening this bug because I did not take everything. Regards, Bernd -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
