[Beaker-devel] Enforcing a unique constraint on the RPM name for tasks

Luigi Toscano ltoscano at redhat.com
Mon Sep 2 09:00:36 UTC 2013


On Sunday 01 of September 2013 19:46:58 Amit Saha wrote:
> Hi all,
> 
> This bug [1] was filed and is being worked upon to ensure that we do not end
> up with the case of having different tasks pointing to the same RPM.
> Looking at the task upload/save code, one of the first checks that is being
> done is that an RPM with the same filename doesn't already exist on disk.
> And thus, Beaker would reject if an attempt was made to upload an RPM (with
> the same filename).

Hi,
the RPM name is built also using the repository name iirc. What does it happen 
if a test is moved from one repository to another, but keeping the same tasks 
ID? Would this require some help from the beaker instance administrators to 
remove the old tasks RPMs? Or would it be possible to add a --force mode 
somewhere when pushing?

Regards
-- 
Luigi


More information about the Beaker-devel mailing list