From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PmV14-0001D9-S2 for garchives@archives.gentoo.org; Mon, 07 Feb 2011 17:36:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 08FB2E0A9B; Mon, 7 Feb 2011 17:36:37 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 55640E0A92 for ; Mon, 7 Feb 2011 17:36:04 +0000 (UTC) Received: from [192.168.1.201] (23.151.222.87.dynamic.jazztel.es [87.222.151.23]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id 176AB1B40BE for ; Mon, 7 Feb 2011 17:36:02 +0000 (UTC) Subject: Re: [gentoo-dev] avoiding urgent stabilizations From: Pacho Ramos To: gentoo-dev@lists.gentoo.org In-Reply-To: <4D502114.2060006@gentoo.org> References: <4D501BA4.6040802@gentoo.org> <4D502114.2060006@gentoo.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-jzziiO4sPlyki4VNYclg" Date: Mon, 07 Feb 2011 18:35:59 +0100 Message-ID: <1297100159.15824.21.camel@localhost.localdomain> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Archives-Salt: X-Archives-Hash: 467045bf3983935a810f70aaf8056a17 --=-jzziiO4sPlyki4VNYclg Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El lun, 07-02-2011 a las 18:43 +0200, Samuli Suominen escribi=C3=B3: > On 02/07/2011 06:19 PM, "Pawe=C5=82 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=3D35348= 7 > >=20 > > However, in theory that should not happen, because presumably the > > current stable has been tested in the past and considered not broken. > >=20 >=20 > In this case, xdm has been broken for more than a year because it has > been ignoring pambase by not using system-local-login. >=20 > Only the problem came to light after ConsoleKit really started to > require this functionality from pambase. >=20 > Tricky... >=20 > 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. >=20 > Sorry. >=20 > - Samuli >=20 >=20 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? --=-jzziiO4sPlyki4VNYclg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAk1QLX8ACgkQCaWpQKGI+9RlUACfYeiq+zhId21MAzB18zfyEAeh 2X4An2OtYR/I3azA0yV+teyOF9egg4jK =V2/j -----END PGP SIGNATURE----- --=-jzziiO4sPlyki4VNYclg--