Procedure to push a package causing broken deps to f15?

Paul Howarth paul at
Wed Feb 16 09:43:18 UTC 2011

On 16/02/11 09:39, Peter Robinson wrote:
> On Wed, Feb 16, 2011 at 7:46 AM, Paul Howarth<paul at>  wrote:
>> On Mon, 14 Feb 2011 11:51:21 -0600
>> Bruno Wolff III<bruno at>  wrote:
>>> On Mon, Feb 14, 2011 at 18:35:54 +0100,
>>>    Ralf Corsepius<rc040203 at>  wrote:
>>>> I was looking into fixing the 10-15 perl-packages, which have made
>>>> it into current f15, even though they carry broken deps. Waiting
>>>> the usual 8-10 days of delay is not helpful for such cases, because
>>>> they will cause f15 to remain broken for at minimum this delay time
>>>> (Which in case of dep chains, can easily evolve to several weeks
>>>> [1]).
>>> The policy is at
>>> For branched (pre-beta) you only need to wait three days if you get
>>> no karma and it isn't critpath. You can set the karma required to one
>>> and get someone else to do a test and sign off on it and move it to
>>> stable right after that.
>> I just tried marking
>> as stable; it's been in testing for 3 days and 4 hours now so I
>> expected it to work but was told by bodhi that it hadn't been in
>> testing for the required period yet. Does bodhi know that the pre-beta
>> testing period is a minimum of 3 days rather than 7?
> Its the date that its pushed to testing not the date its submitted.

I know. It was pushed to testing on 2011-02-13 at 03:23:21 and I tried 
to mark it stable on 2011-02-16 at 07:40:00 (+3 days and 4 hours).

> Looking at it now it has a message that it can be pushed to stable.

That's because Ralf has since tested it and given it karma to make it to 
the stable threshold (thanks Ralf).


More information about the devel mailing list