> On mercredi, 7 octobre 2020 18.26:36 h CEST Matt Darfeuille wrote: >> Following Tom's advice, moving this (entire thread (1)) to the devel >> list. >> >> Any thoughts on the below (the patch in question (2) is reattached >> here)? >> >> 1) >> https://sourceforge.net/p/shorewall/mailman/shorewall-users/thread/d83aa9a26 >> 26c6459f58f671af768b570.squirrel%40webmail.bi.corp.invoca.ch/#msg37121743 >> 2) >> Release repository, master branch, patch file: >> release-master-1-20.10.07.17.04.57-rfc.patch >> >> -------- Forwarded Message -------- >> Subject: Re: [Shorewall-users] Shorewall reload doesn't reload? >> Date: Wed, 7 Oct 2020 08:49:47 -0700 >> From: Tom Eastep <teas...@shorewall.net> >> Reply-To: Shorewall Users <shorewall-us...@lists.sourceforge.net> >> To: shorewall-us...@lists.sourceforge.net > > Moving files in a pre/post section is normally creating orphan files, > which > afterward belong to no packages, which is not what we have as rules at > least > on openSUSE.
Well, in most shorewall packages I've seen they don't control anything in /var/lib/shorewall so moving files there doesn't make anything worse. The only way to handle it would be to define %ghost files in the RPM and I've never tried that because the files in /var/lib/shorewall changed between releases and it's too much work to find them out. > > I agree with Simon point of view. Upgrade the system, but no automatic > upgrade, as you can too easily lockup everyone out if a problem occur. > Better save than sorry, yes :-) Regards, Simon _______________________________________________ Shorewall-devel mailing list Shorewall-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-devel
