Procedure to push a package causing broken deps to f15?

Paul Howarth paul at city-fan.org
Wed Feb 16 07:46:46 UTC 2011


On Mon, 14 Feb 2011 11:51:21 -0600
Bruno Wolff III <bruno at wolff.to> wrote:

> On Mon, Feb 14, 2011 at 18:35:54 +0100,
>   Ralf Corsepius <rc040203 at freenet.de> 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 http://www.fedora.redhat.com/wiki/Updates_Policy.
> 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
https://admin.fedoraproject.org/updates/perl-Net-SSH-Perl-1.34-11.fc15
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?

Paul.


More information about the devel mailing list