On Wednesday, 15 March 2017 18:37 Bruno Friedmann wrote:
Ludwig as Leap Leader, I've this question. For shorewall 4.6.13.4 is the last stable of 4x series (but it doesn't receive any fixes from upstream right now).
There in between a 5.0 and now the new 5.1x version. Moving from 4 to 5 works (tested hopefully, at least in my usecases), but a migration of configuration is needed by admin (it is somewhat automated shorewall -a ... do most of the jobs, but a review by the firewall admin is mandatory (at least this is the advise I apply to myself).
I will in few hours get the new 5.1.3 in netfilter repo. And of course I can push that to Leap (I use both of them). My question is : upgrading to such new version isn't against Leap spirit ?
I'm not Ludwig but this is my view. Incompatible configuration requiring (in general) manual intervention is IMHO something we should try to avoid withing Leap 42.x series whenever possible. If we don't, we lose the main advantage we have compared to the pre-Leap era. On the other hand, maintaining version abandoned by upstream isn't really desirable either. In the end, it should be maintainer's call, IMHO, because it's the maintainer who is going to handle the fallout in either case, whether it's going to be angry users whose setups breaks on 42.2 -> 42.3 migration or having to address bugs and security issues in version no longer supported by upstream. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org