On Mon, Mar 11, 2013 at 12:50:53PM -0400, Kamil Paral wrote:
> > - bugs that break the rawhide buildroot. In practice these are
> > usually
> > noticed pretty quickly and the offending build is just untagged
> > until
> > it can be fixed, but there could be cases where the fix is more
> > c
On Mon, 11 Mar 2013 12:16:31 -0500
Bruno Wolff III wrote:
> Still when gdm breaks (which it is right now for me - probably due to
> software rendering not doing enough) it might be nice to have a bug
> with suggested work arounds (c-a-f2, login as root, stop gdm, start
> kdm) so that people can
On Mon, Mar 11, 2013 at 11:07:35 -0600,
Kevin Fenzi wrote:
Well, we could look at adding critpath, but I think that could get us
into more hazy territory, and some subjective issues around 'broken'.
Especially since rawhide packages can change interfaces, and something
behaving differently on
On Mon, 11 Mar 2013 12:50:53 -0400 (EDT)
Kamil Paral wrote:
> > - bugs that break the rawhide buildroot. In practice these are
> > usually
> > noticed pretty quickly and the offending build is just untagged
> > until
> > it can be fixed, but there could be cases where the fix is more
> >
> - bugs that break the rawhide buildroot. In practice these are
> usually
> noticed pretty quickly and the offending build is just untagged
> until
> it can be fixed, but there could be cases where the fix is more
> complex and has a bug associated with it.
For those of us who are not ski
Greetings.
I'd like to propose we create a rawhide tracker bug.
Probibly name it: RawhideBlocker
(But I don't care what colour the bikeshed is)
This bug would be used for the following types of bugs against the
'rawhide' version:
- bugs that prevent the daily rawhide compose from completing.
