On Tue, 2009-09-01 at 13:00 -0500, Andy Speagle wrote: > Again, I'm working on a script to clone errata from RHN to Spacewalk. > As part of that, the user can opt to publish the errata at creation > time > to channels that already have the relevant packages. > > One problem that I'm coming up against is that the > "server.errata.publish" function in the API seems to time-out if > there's > a lot of work to be done. The act of publishing isn't the quickest > thing in general. I have programmed in a few retries, but it just > doesn't seem to be enough.
Ok, so I worked around this issue by publishing individually to separate channels, one at a time. However, this brought another issue to light for me as I dug into this more. There's really no way for the publish function to know what packages to push to a given channel. For instance, I have a recent errata for "gnutls" which contains packages for both RHEL 4&5 32-&64-bit. What ended up happening is that the the RHEL4 channels got RHEL5 packages. Again, there's no way for it to know better. I remember from my Satellite days that you could "merge" errata if you pulled down the errata for different channels at different times, you could merge everything under the same advisory. When it came time to publish those you rather tediously (via the WebUI) had to select which packages belonged in which channels. blah blah Bottom line, is there any way via the API to merge errata? If there is, then I can manager the auto-publishing separately. If not a merge, then perhaps an extension to the publish function such that you could specify exactly which packages in the errata are pushed. Thanks, -- Andy Speagle "THE Student" - UCATS Wichita State University
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
