Currently, the Beaker task makefile takes the git repo name into account when generating tags and RPM files. This can cause problems if a task is moved from one repo (say, beaker) to another (say, beaker-core-tasks), since uploading a task with a different RPM name from the original can cause errors in tasks that have been scheduled, but haven't actually started running yet (they end up trying to install using the wrong RPM name). The simplest solution to this is to make it easy to force a particular prefix for tasks, instead of using the repo name.
(In reply to Nick Coghlan from comment #0) > since uploading a task with a different > RPM name from the original can cause errors in tasks that have been > scheduled, but haven't actually started running yet (they end up trying to > install using the wrong RPM name). For reference this is bug 1040258.
Instead of keeping these annoying pointless prefixes, another possible solution would be to drop the prefixes entirely from the RPM name but add the prefixed name as a virtual Provides. We would also need a mechanism to add other prefixed names as virtual Provides too, to cover this case. Then in another few months/years we can just drop all that logic entirely.
http://gerrit.beaker-project.org/#/c/2662/
As per the email to beaker-devel-list, we need to change this to use the old name by default, since the task snapshotting behaves badly if the RPM name changes. We can start providing the new shorter name as well, though, which will make it easier to switch the actual name in the future.
http://gerrit.beaker-project.org/2717 added a new RHTS_RPM_NAME setting to force a particular RPM name (the actual workaround needed to avoid bug 1040258 when moving to a task to a different repo)
This was fixed by http://gerrit.beaker-project.org/#/c/2730/ and included in the rhts 4.58-1 release.