On Wed, 2009-09-30 at 06:59 -0500, Andy Speagle wrote: > Hi Folks, > > I'm still having a problem with errata cloning. I've narrowed the > problem down a bit. > > It seems when you clone an errata, if the channel to which you're going > to publish the cloned errata already has the packages listed in the > errata, then it works just fine. The published-cloned errata shows that > it has packages. > > However, if the destination channel for publishing a cloned errata does > NOT already have the packages listed in the errata, then after the > publish, the errata shows that it doesn't have any packages. > > So, what it looks like is that the publish action for a cloned errata > isn't pushing packages to the channel. > > Can a developer weigh in on this functionality, please?
Ok, so I dug more deeply myself and am finding that if I use: server.errata.clone () via the API, the errata gets cloned and published to the destination channel, packages and all ... just fine. So... I'm wondering if this functionality is broken in the WebUI. Does anyone have any insight on this? -- 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
