On 1/14/19 12:08 AM, Bruno Friedmann wrote: > On dimanche, 13 janvier 2019 19.56:46 h CET Tom Eastep wrote: >> On 1/13/19 9:58 AM, Bruno Friedmann wrote: >>>>> But perhaps instead of just warn the user, and perhaps got people stuck >>>>> out of their boxes I should propose to run the update in any case ? >>>>> >>>>> Is it safe to consider this, I doubt as the changes for example in nat >>>>> -> >>>>> snat can't be automated and safe in all kind of configuration people can >>>>> have. >>>>> >>>>> Anyway a loop feedback is welcomed to best serve the product and its >>>>> packaging. >>>> >>>> I guess that behavior could be desirable for point release and mayby for >>>> minor release. >>>> >>>> http://shorewall.org/NewRelease.html >>>> >>>> -Matt >>> >>> Hi Matt, I personnally not found any trouble with the update procedure >>> (except the nat -> snat) changes. Now the quest is are we sure (we as >>> shorewall dealers ;-) to not break a working system. >> >> Bruno -- what problem did you have with nat -> snat conversion? >> >> Thanks, >> -Tom > > Oh just that it was a manual operation, so kind of operation that can't be > handled automatically, otherwise work great. >
I believe that Foobar Linux is doing a 'shorewall[6] update' unconditionally after rpm update is complete. Maybe Tuomo can comment. -Tom -- Tom Eastep \ Q: What do you get when you cross a mobster with Shoreline, \ an international standard? Washington, USA \ A: Someone who makes you an offer you can't http://shorewall.org \ understand \_______________________________________________
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Shorewall-devel mailing list Shorewall-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-devel
