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. This is why we ended up having to add the RHTS_RPM_NAME to override the names of our relocated tasks to match the names they had in the old repo. So, I think we need to at least partially revert that particular change and keep using the legacy repo-specific names until BZ#1055821 has been implemented. For our use case (handling the relocation from the main beaker repo to the separate beaker-core-tasks repo without tripping over the renaming bug), the RHTS_RPM_NAME override does the trick. Regards, Nick. P.S. Yes, http://beaker-project.org/dev/proposals/external-tasks.html is *definitely* going to be the focus of 0.16 :) -- Nick Coghlan Red Hat Hosted & Shared Services Software Engineering & Development, Brisbane Testing Solutions Team Lead Beaker Development Lead (http://beaker-project.org/) _______________________________________________ Beaker-devel mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
