the gentoo ebuild for logwatch has for many versions now contained a 'emerge' script to give emerge statistics. these scripts add glsa-check functionality to logwatch. This is important because it will run 'glsa-check -p affected' on the system every day when logwatch is run, and notify the system administrator that they need to examine the glsa and scheule an upgrade to their server (or just emerge the new packages). These scripts go in: /usr/share/logwatch/scripts/services/aa-glsa-check /usr/share/logwatch/default.conf/services/aa-glsa-check.conf
Created attachment 104366 [details] scripts/aa-glsa-check
Created attachment 104367 [details] default.conf/aa-glsa-check.conf
dont cc me, i'm in the base-system alias already
should be added to the package that installs glsa-check ... aka gentoolkit
Since this hasn't gotten any attention in months, I'm adding the most recent maintainers of gentoolkit as direct CC's of this bug. A simple test and commit is all that's required here...
(In reply to comment #0) > the gentoo ebuild for logwatch has for many versions now contained a 'emerge' > script to give emerge statistics. (In reply to comment #4) > should be added to the package that installs glsa-check ... aka gentoolkit Mike, this should really be handled in a consistent way, so either logwatch should provide both or none of the scripts.
PING All that's required here is a test and commit. This is not complicated. In my opinion, this should go in the logwatch ebuild and package, as it will then apply if glsa-check is installed, but installing it with gentoolkit would be fine too...
Not going to add this in gentoolkit, especially as glsa-check will be moved from gentoolkit into portage.
added to sys-apps/logwatch-7.3.7_pre20091204
