EPEL Moving to testing repo?

Daniel Pocock daniel at pocock.com.au
Mon Jan 20 10:31:48 UTC 2014


On 17/01/14 07:27, Mathieu Bridon wrote:
> On Fri, 2014-01-17 at 07:11 +0100, Daniel Pocock wrote:
>
>> I've been trying to do this for a new package, cajun-jsonapi
>>
>> bodhi refuses to let me request the update, it always gives the
>> message:
>>
>> "cajun-jsonapi-2.0.3-1.el6 not tagged as an update candidate"
>>
>>  
>> It is in the Git repository branch for EPEL6
>>
>> http://pkgs.fedoraproject.org/cgit/cajun-jsonapi.git/tree/?h=el6
>>
>> and it is built on EPEL6:
>>
>> http://koji.fedoraproject.org/koji/buildinfo?buildID=489563
>>
>> Would anybody know what I am doing wrong?  Or is there some cooling off period before new packages can go to EPEL?
> The build is indeed not tagged as an update candidate, it is tagged as
> "trashcan".

The change to trashcan happened some time after I tried to request the
update.  I received an email telling me that I had not made any update
and that it would be tagged trashcan.

> That means is has been (or soon will be, I forgot) removed.
>
> That being said, the build never succeeded:
>     http://koji.fedoraproject.org/koji/taskinfo?taskID=6385065
>
> It is quite weird though that it is the tagging task which failed,
> something seems to have gone wrong here.
>
> What you could do is:
>   koji tag-pkg dist-6E-epel-testing-candidate cajun-jsonapi-2.0.3-1.el6
>
> That should put the build back in the proper state, and then Bodhi will
> let you create the update.
>
>
It looks like this worked, thanks for the feedback




More information about the epel-devel mailing list