Re: Broken Debian's testing migration (grave bug in module-init-tools)
- Date: Mon, 12 Apr 2010 12:07:08 +0200
- From: Sven Joachim <svenjoac@xxxxxx>
- Subject: Re: Broken Debian's testing migration (grave bug in module-init-tools)
X-Mailing-List: <debian-user@xxxxxxxxxxxxxxxx> archive/latest/573916
Resent-Date: Mon, 12 Apr 2010 10:07:27 +0000 (UTC)
On 2010-04-12 11:19 +0200, Vincent L
> There's something broken in the design of Debian's migration to testing.
> A grave bug in the testing version of module-init-tools (3.12~pre2-1)
> was fixed several weeks ago, and the package was uploaded with
> module-init-tools (3.12~pre2-2) unstable; urgency=high
> * Fixed an init scripts dependency loop introduced in -1. (Closes: #574535)
> -- Marco d'Itri <md@xxxxxxxx> Mon, 22 Mar 2010 12:21:18 +0100
> but it hasn't migrated to testing yet!
> The reason is a build failure on HPPA:
> Isn't it unacceptable that a problem on some platform blocks a fix
> for a grave bug?
This may not be acceptable for testing users, but the rules are pretty
clear: all release architectures must be in sync in testing. This often
holds up important fixes for months.
The conclusion I had drawn from this long ago: don't use testing, it is
only meant to be a staging area for preparing the next release and not
as a distribution actually to be used by people, except during freezes
Use stable or unstable instead, or a mixed testing/unstable system where
you upgrade packages that are broken in testing from unstable.
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx