On Sat, 19 May 2012, Christoph Anton Mitterer wrote:

> Hi.
>
> Especially for automated nagios/icinga checks it's nice if one could
> differ between critical and non-critical upgrades in SL repos.
>
> This is what the yum security plugin should do but this doesn't work
> apparently:
>
> # /usr/bin/yum check-update -C
> Loaded plugins: changelog, downloadonly, fastestmirror, keys, priorities, protectbase, ps, security, verify
> 96 packages excluded due to repository priority protections
> 0 packages excluded due to repository protections
>
> kernel.x86_64            2.6.32-220.17.1.el6   sl-security
> kernel-devel.x86_64      2.6.32-220.17.1.el6   sl-security
> kernel-doc.noarch        2.6.32-220.17.1.el6   sl-security
> kernel-firmware.noarch   2.6.32-220.17.1.el6   sl-security
> kernel-headers.x86_64    2.6.32-220.17.1.el6   sl-security
>
>
> But the invocation of claims that ne security updates would be avialable
>
> # /usr/bin/yum --security check-update -C
> Loaded plugins: changelog, downloadonly, fastestmirror, keys, priorities, protectbase, ps, security, verify
> 96 packages excluded due to repository priority protections
> 0 packages excluded due to repository protections
> Limiting package lists to security relevant ones
> No packages needed for security; 5 packages available
>

The repository should have an additional updateinfo.xml file which should 
contain some information from RHSA announcements. Also the repomd.xml must 
be updated to
include name and checksum for updateinfo.xml  I once wrote scripts that 
handled all of that automatically. First the initial filling of the 
security data and then
handling of email of specially created email account to receive only RHSA 
announcements, extract from those the needed fields, and add to 
updateinfo. I don't know how
well those would work with 6.x as the scripts were done about two years 
ago for 5.x.

Apparently SL repo doesn't have updateinfo.xml.