Franky Its a little more complicated than that look at the ticket the API overrides the package IDs because when you add the package via the API it does an other NVREA search and propagates the first package it finds to the rest of the channels. Even if it doesn't match the package id you defined in the creation of the errata. This isn't by accident by the way it explicitly stated in comment in the code that it was done that way on purpose. Its not actually the fault of the developers of the errata sync scripts. So don't blame it on David Nutter by saying he wrote a bad script. I did a lot of digging into the subject and would be glad to share notes with you on the developers list. Just start the thread and I'll jump in. That being said there are a few options for sync scripts. There Frankys script There is mine <a href="https://github.com/prmarino1/Extravehicular-Activity-Admin/blob/master/errata-tools/eva-direct-errata-sync.pl" type="url">https://github.com/prmarino1/Extravehicular-Activity-Admin/blob/master/errata-tools/eva-direct-errata-sync.pl</a> And many more <div style="font-family: arial, sans-serif; font-size: 12px;color: #999999;">-- Sent from my HP Pre3</div> <hr align="left" style="width:75%">On Jan 28, 2013 5:11 PM, Franky Van Liedekerke <liedekef@telenet.be> wrote: On Mon, 28 Jan 2013 12:54:27 -0600 Nick Wales <nick@nickwales.co.uk> wrote: > Using David Nutters script > https://github.com/davidnutter/Centos-Errata > > I have a centos 5 machine and a centos 6 machine pushing errata. The > centos 6 errata is entered fine, but for errata which spans both > releases the second release that is attempted, in this case 5, the > log reads > > "Errata CEEA-2012:1488 already exists on server, skipping" > > Any thoughts on how this can be overcome? This is one of the scripts that can (and will) lead to channel-crosscontamination, so I suggest you don't use it. See this line in the code: if len(result) > 0: pkg_details = result[0] ==> the package info is searched upon based on it's NVREA (name, version, release, epoch and architecture), but this can be the same for redhat and centos, so the solution in the script: if you find more than one package, just use the first one found ... and as a result that package gets pushed in your channel (and so redhat packages can get in centos channels). Please consider using another script (in this case I'll advertise mine but there are others) that has no such issues: https://github.com/liedekef/spacewalk_scripts Franky _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list