Andy Speagle wrote:
On Thu, 2009-10-01 at 09:55 -0500, Greg DeKoenigsberg wrote:
Fascinating. Not that I have any deeper insight, other than that
next
step is obviously to compare the errata cloning code in the two
different
parts of the codebase. :)
Indeed. Sadly, I'm not skilled
On Thu, 1 Oct 2009, Andy Speagle wrote:
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?
Fascinating.
On Thu, 2009-10-01 at 09:55 -0500, Greg DeKoenigsberg wrote:
Fascinating. Not that I have any deeper insight, other than that
next
step is obviously to compare the errata cloning code in the two
different
parts of the codebase. :)
Indeed. Sadly, I'm not skilled enough to tackle this.
Hi Team,
I'm having an odd issue with cloning of errata via the WebUI. I am able
to clone the errata just fine. When I look at it in an unpublished
state, I can see that it has a package assigned to it. However, the
moment I publish the cloned errata to one of my production-level
channels, the
