From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] avoiding urgent stabilizations
Date: Mon, 07 Feb 2011 18:35:59 +0100 [thread overview]
Message-ID: <1297100159.15824.21.camel@localhost.localdomain> (raw)
In-Reply-To: <4D502114.2060006@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
El lun, 07-02-2011 a las 18:43 +0200, Samuli Suominen escribió:
> On 02/07/2011 06:19 PM, "Paweł Hajdan, Jr." wrote:
> > From time to time there are stabilization bugs where the current stable
> > is broken. For example, https://bugs.gentoo.org/show_bug.cgi?id=353487
> >
> > However, in theory that should not happen, because presumably the
> > current stable has been tested in the past and considered not broken.
> >
>
> In this case, xdm has been broken for more than a year because it has
> been ignoring pambase by not using system-local-login.
>
> Only the problem came to light after ConsoleKit really started to
> require this functionality from pambase.
>
> Tricky...
>
> But it was still tested, unfortunately the test environment that was
> used leaked some environment variables that made XDM appear to work, so
> this was catched too late.
>
> Sorry.
>
> - Samuli
>
>
I think that maybe we could have an even higher "priority" field called,
for example, "Broken Stable" that should be *only* used for that cases
and that arch teams should try fix sooner. What do you think?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-07 17:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 16:19 [gentoo-dev] avoiding urgent stabilizations "Paweł Hajdan, Jr."
2011-02-07 16:43 ` Samuli Suominen
2011-02-07 17:35 ` Pacho Ramos [this message]
2011-02-07 17:45 ` Andreas K. Huettel
2011-02-07 20:50 ` Markos Chandras
2011-02-07 21:02 ` "Paweł Hajdan, Jr."
2011-02-08 3:36 ` [gentoo-dev] " Duncan
2011-02-21 0:26 ` Enrico Weigelt
2011-02-08 8:24 ` [gentoo-dev] " Markos Chandras
2011-02-08 8:38 ` "Paweł Hajdan, Jr."
2011-02-08 11:43 ` Roy Bamford
2011-02-08 12:03 ` Markos Chandras
2011-02-08 12:22 ` Fabian Groffen
2011-02-08 13:12 ` "Paweł Hajdan, Jr."
2011-02-21 0:37 ` Enrico Weigelt
2011-02-08 16:41 ` Donnie Berkholz
2011-02-08 17:37 ` Rich Freeman
2011-02-08 17:46 ` Andreas K. Huettel
2011-02-08 17:57 ` Fabian Groffen
2011-02-08 18:10 ` Andreas K. Huettel
2011-02-09 13:57 ` Rich Freeman
2011-02-09 14:01 ` [gentoo-dev] GSLA improvements (WAS: avoiding urgent stabilisations) Fabian Groffen
2011-02-09 14:08 ` [gentoo-dev] avoiding urgent stabilizations "Paweł Hajdan, Jr."
2011-02-09 15:26 ` Rich Freeman
2011-02-09 19:57 ` Donnie Berkholz
2011-02-09 21:01 ` Robin H. Johnson
2011-02-08 18:56 ` Donnie Berkholz
2011-02-21 0:34 ` Enrico Weigelt
2011-02-08 13:12 ` Roy Bamford
2011-02-08 14:24 ` Rich Freeman
2011-02-21 0:11 ` Enrico Weigelt
2011-02-25 10:25 ` Ed W
2011-02-25 11:08 ` Matthew Marlowe
2011-02-25 11:37 ` Ed W
2011-02-25 12:31 ` [gentoo-dev] Community Development of Gentoo Server Mgmt Tools for VMware Clusters/etc - Puppet modules, github collaboration, etc - Fork of Dev Topic: Avoiding Urgent Stabilizations Matthew Marlowe
2011-02-25 17:53 ` [gentoo-dev] avoiding urgent stabilizations Enrico Weigelt
2011-02-26 11:45 ` Ed W
2011-02-26 15:57 ` Enrico Weigelt
2011-02-27 10:43 ` Ed W
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1297100159.15824.21.camel@localhost.localdomain \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox