Procedure to push a package causing broken deps to f15?
mmaslano at redhat.com
Wed Feb 16 16:12:28 UTC 2011
----- Original Message -----
> From: "Bruno Wolff III" <bruno at wolff.to>
> To: "Ralf Corsepius" <rc040203 at freenet.de>
> Cc: "Development discussions related to Fedora" <devel at lists.fedoraproject.org>, "Tom Callaway" <tcallawa at redhat.com>
> Sent: Monday, February 14, 2011 6:51:21 PM
> Subject: Re: Procedure to push a package causing broken deps to f15?
> 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 ).
> 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
> and it isn't critpath. You can set the karma required to one and get
> else to do a test and sign off on it and move it to stable right after
Or it should be possible to fix such bugs with request on release
engineering ;-) https://fedorahosted.org/rel-eng/ticket/4443
BaseOS team Brno
More information about the devel