On Thu, Aug 14, 2014 at 10:29:26PM +0100, ray klassen wrote: > Aha, so you're the maintainer of those packages are you... Didn't see > that. So at least you could reliably tell me if running the latest > shorewall won't trigger any other issues with any other wheezy package? > generally I avoid sid on production machines. (that said, to solve a > specific problem I did just pull down libreswan, compiled the debs and got > rid of openswan) The only other thing I worry about with shorewall is when > stuff I've included to solve specific issues in a complex environment is > now deprecated and what will I do when it's gone? it's a matter of > re-hashing (that's desperately trying to remember) why it got included in > the first place and then implementing the new, preferred solution without > breaking anything. > I can tell you that I run only stock Wheezy on my production systems, with the latest Shorewall. I have not encountered any issues using the latest Shorewall on stable, and have been doing so since Shorewall 4.0 (when I took over as maintainer of the Debian packages).
I only run sid for development and building packages. Tom tends to leave deprecated features for a fair amount of time. My experience has been that I always have ample time to sort out any changes I need to make. Of course, as you point out, sometimes it is hard to remember *why* you did a specific thing. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
------------------------------------------------------------------------------
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
