Closed nickwales closed 11 years ago
liedekef
commented
11 years ago Yes, you're right: it works on a channel-per-channel basis. So you need to run it for eg. centos 5 32 bit updates, another run for 64 bit, and again for centos6. And for EPEL: I didn't know there were EPEL errata, I need to add the code for the EPEL xml file ... shouldn't be too hard to add though.
nickwales
commented
11 years ago I'm with you, thanks for the clarification.
With regard to EPEL all I know is I have a few errata looking like this in my epel channel from having used David Nutters script.
CL-FEDORA-EPEL-2013-0031 - Product Enhancement Advisory
which points to:
liedekef
commented
11 years ago Ok, I'll close this one and try to add the code for EPEL later on.
How does this work for child channels?
I've got updates and epel in their own child channels and having run once pointing directly at the updates channel I got an openipmi errata:
"INFO: Creating errata CEBA-2012:1406:C5-64 for CEBA-2012:1406 (CentOS 5 OpenIPMI Update) (All 9 packages present in the corresponding channel)"
I then deleted the errata and ran the script pointing to the OS / parent channel I got a different result.
"INFO: Skipping CEBA-2012:1406 since not all packages are present INFO: this should be fixed by the next channel sync, or the errata is already superseded by another one"
Given this behaviour am I right in thinking that the script isn't cascading through the child channels? If so it seems to me the answer is to run the script against multiple channels (EPEL, Updates and maybe some others) but I thought I'd confirm first.