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

Amit Saha asaha at redhat.com
Mon Sep 2 23:15:11 UTC 2013


Hi,

----- Original Message -----
> From: "Luigi Toscano" <ltoscano at redhat.com>
> To: beaker-devel at lists.fedorahosted.org
> Sent: Monday, September 2, 2013 7:00:36 PM
> Subject: Re: [Beaker-devel] Enforcing a unique constraint on the RPM name	for tasks
> 
> 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?

Sorry, I am not sure I understand your question. However, this change shouldn't 
affect users. Beaker already does the unique name checking, although not from a 
DB point of view.

If you mean that you will move your task to a new repository, but the resulting
RPM will have the same filename, Beaker will not allow you to upload it.
You will either have to change the version name or write the testinfo.desc (I believe)
such that your RPM's filename is different.

Hope that answers your query.

Best,
Amit.

-- 
Amit Saha <http://echorand.me>
Infrastructure Engineering and Development
Red Hat, Inc.


More information about the Beaker-devel mailing list