On 01/24/2014 12:34 PM, Amit Saha wrote:
----- Original Message -----
> From: "Nick Coghlan" <ncoghlan(a)redhat.com>
> To: "beaker-devel" <beaker-devel(a)lists.fedorahosted.org>
> Sent: Thursday, January 23, 2014 6:13:24 PM
> Subject: [Beaker-devel] Compatibility issue with the new rhts default task RPM
naming
>
> With the current master branch in RHTS, the default behaviour of "make
> rpm" and "make bkradd" is now to leave out the repo name.
>
> However, due to the way the per-recipe task library snapshotting
> currently works (as described in
>
https://bugzilla.redhat.com/show_bug.cgi?id=1055815), I believe that's a
> problematic change until we fix
>
https://bugzilla.redhat.com/show_bug.cgi?id=1055821 in order to handle
> task RPM *renames* in addition to outright deletion.
>
> If we release RHTS in its current state, people may generate RPMs with
> the new names, upload them, and then find
> scheduled-but-not-yet-executing jobs aborting as they're told to try to
> find the *new* name in the *old* snapshot, which isn't going to work.
> The trick of providing the old package name in the new RPM that we
> thought handled this doesn't actually help, because it gets the problem
> backwards.
If I understand correctly, these changes are part of the rhts-devel package.
So, we may not be able to "release" rhts, but it seems to me that we may still
be able to deploy the upgrade to rhts-test-env, so that the fix to this bug [1]
is released.
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1026670
Indeed, and that's what we're going to do while Ray works on flipping
the behaviour of the updated task creation (i.e. generate RPMs with the
old name, add a new provides for the naming scheme we'd eventually like
to migrate to, in order to avoid running into
https://bugzilla.redhat.com/show_bug.cgi?id=1040258).
The new RHTS_RPM_NAME setting will cover the case of moving a task to a
different repo, while keeping the old name.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane
Testing Solutions Team Lead
Beaker Development Lead (
http://beaker-project.org/)