[Spacewalk-list] API. Merge single new errata and packages

[Matt Micene]

Will,

I haven't looked at the Errata workflow in a while but I believe the next step isn't to mergePackages but to use the errata.publish call.

If you look at the UI after your clone step, the errata should show up in the clone as unpublished.  The next step is publish, which moves the package into the channel.  You can also use errata.listUnpublishedErrata to make sure the errata you are trying to merge are ready.

One thing to note, you say you are trying to merge a single errata.  errata.mergeErrata will merge all errata from the source channel constrained by the date range or list.  While you are probably passing a single value in that list, it may have odd side effects.  You may want to look at the errata.clone* methods which only operate on the provided list rather than using that list as a constraint.

HTH,
Matt

> -----Original Message-----
> From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-
> bounces at redhat.com] On Behalf Of wm-lists
> Sent: Tuesday, September 24, 2013 8:45 PM
> To: spacewalk-list at redhat.com
> Subject: [Spacewalk-list] API. Merge single new errata and packages
> 
> I'm sure there's a simple way to do this, but I'm probably over-
> complicating it.
> I'm looking to write a python script, that, given an Errata Advisory
> Name, will merge the Errata and associated package from one channel
> (say Red Hat source) to another channel (say our development channel).
> 
> I've got the Errata merge fine with the mergeErrata api call,
> lient.channel.software.mergeErrata(key,channelinfo.get('clone_original'
> ), mychannel.get('label'),[errata])
> 
> But there isn't a mergePackage that only merges one package.
> 
> Any help or guidance?
> 
> Thanks
> Will
> 
> Sent from my iPhone
> Sent from my iPhone
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list