On Sun, Oct 07, 2007 at 09:18:19PM -0400, Roberto C. S?nchez wrote: > > That's why i think the best compromise would be to maintain a Debian > > repository for the project that keeps up to date with Shorewall's stable > > version, and ensure that this package is fully Debian-compliant, so that > > people can smoothly integrate the latest Shorewall versions into their > > Debian systems. (We should start with the packages that Lorenzo has > > created to ensure maximum compatibility.) > > > Please don't misunderstand me. I am not strictly opposed to this. > However, I think that the first step would be to ask Lorenzo to either > relinquish the shorewall packages (Andrew and I are both Debian > developers and he if is not willing/able to maintain or co-maintain the > packages, I certainly would be; I don't mean to insult you Andrew, I > just don't want to speak for you without knowing).
I retired from Debian years ago. > Failing that, perhaps inviting Lorenzo to be more involved in the > upstream development would probably result in better packages and also > Debian more closely tracking the upstream releases. > > If we can get that, then it would be possible to just tell people to pin > their shorewall packages to unstable. If we have a hand in the > packaging, we can always make sure that the unstable version also works > in stable. This is almost certainly a better idea. Debian's more than just a bunch of rules; you can't really duplicate what it does in an external effort. More than anything else, having hundreds of highly skilled people looking at things is what really makes Debian work the way it does. There are several measures in place to deal with packages that are both fast-moving and reasonably reliable, they just need to be used; it would be straightforward to include shorewall in volatile-sloppy, for example. The package needs either more manpower or more attention, it should be easy to sort out. The procedure for dealing with these things is detailed here: http://www.debian.org/doc/developers-reference/ch-beyond-pkging.en.html#s-mia-qa Just follow it. These things can usually be sorted out fairly quickly, so long as somebody (preferably within Debian) kicks the process into action - it's presumed that if nobody is making any noise about it, it cannot possibly be important enough to bother with. Start by hunting down Lorenzo and finding out what's going on. He's a relatively new developer and was a student when he signed up; people like that very frequently graduate and then find they lack time to work on Debian stuff. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
