Hi Romain,
On Tue, Oct 20, 2020 at 10:39:34PM +0200, Romain Porte wrote: > I intent to salvage this package with your approval, or after the 21 > days delay as mentioned in the developer guide: > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#how-to-salvage-a-package > > I have reworked the package locally to fix almost all lintian warnings, > moved format from 1.0 to 3.0 (quilt) and updated to the latest standards > version. I already did a previous NMU (on top of another NMU) that > fixed the IPv6 bugs. I received thanks from bug authors as it solved > their issues (and mine too). > > I was originally trying to publish this big change as a NMU, but it > would make more sense to first adopt the package and then make a proper > -2 release instead of a 1.3 NMU. I've been AFK a fair bit lately (and so sorry for this slow reply too, I've only just caught up on mail enough to see this now) - so you have my thanks for taking an interest in keeping this one maintained too. I do still actively use this package on systems I maintain, so whatever happens I am still going to have an enduring interest in ensuring it works as needed for those too, whether that's as a (co)maintainer for the distro package, or in a local repository of my own. I can't say I'm a huge fan of format 3.0 (quilt), especially in this day and age where both the package and upstream are maintained in git, and doubly so for a package like this one, where I was able to upstream all the local patches it was carrying in about the first week that I started maintaining it ... So if you can be happy not to make major changes that are essentially gratuitous and don't actually add anything of value or fix any really existing problem (or at least not go down that road without first talking about what real advantage you think it might add), I would certainly be happy to see this package have all the people with a genuine interest in it helping to actively maintain it. It is essentially a "finished" piece of software - it does the job of implementing the protocol - so mostly the only work it should need is when something external changes that breaks its environment. If you want to add yourself to uploaders and contribute to fixing real bugs with a Proper Maintainer hat on, I'd absolutely welcome that. Does that sound like a more long-term viable way forward on this one to you? It is the nature of this game for people's needs with packages like this one to be cyclical, and I'll guess it will be no different for you once your immediate need is scratched as well. Cheers, Ron
