Re: Bug#457177: keep yaird out of Testing
- To: firstname.lastname@example.org
- Cc: email@example.com
- Subject: Re: Bug#457177: keep yaird out of Testing
- From: Jonas Smedegaard <firstname.lastname@example.org>
- Date: Sun, 28 Dec 2008 14:37:17 +0100
- Message-id: <20081228133717.GH22453@jones.dk>
- Reply-to: email@example.com
- In-reply-to: <20071222125931.GA11193@mails.so.argh.org>
- References: <20071220101956.GB15344@stro.at> <20071221144402.GB2295@jones.dk> <20071221170316.GN1537@baikonur.stro.at> <20071221190457.GE2295@jones.dk> <20071221191121.GO1537@baikonur.stro.at> <20071221195421.GG2295@jones.dk> <20071222125931.GA11193@mails.so.argh.org>
-----BEGIN PGP SIGNED MESSAGE-----
On Sat, Dec 22, 2007 at 01:59:31PM +0100, Andreas Barth wrote:
>severity 457177 serious
[details on discussing individual issues separately snipped]
>Unfortunatly, I have to agree from a release team POV (i.e. speaking
>with my Release Manager hat on) with maks on the general status of the
>package, especially as maks spoke with his kernel arch maintainer hat
>on (so his remarks shouldn't be lightly waived away).
>One might discuss about the adequate severity of the individual bugs,
>but they together makes this package RC buggy. (Perhaps even some of
>the individual bugs make it - we can discuss that at the individual bug
>reports if wanted.) But there are some cases like "brutal hardcoding -
>breaks ony every new linux image either due to /proc, /sys or
>/boot/config hardcoded parsing see #443821 for the latest 2.6.23
>variation" which are *not* fixed by adjusting to the current kernel,
>but we expect some flexibility and robustness as long term strategy.
Do the release team still consider yaird too buggy for release with
Yaird is no more "brutal" in its hardcoded knowledge about Linux than
initramfs-tools, it just hardcodes different kinds of info. If you
disagree then please file a separate bugreport about what you believe is
"brutal" about yaird.
Bug #443821 was *not* not "adjusted to the curent kernel" as Andreas
interprets above. I welcome discussing that issue in detail - but not
here: Please discuss details at the related bugreport!
Yaird does *not* "break on every new linux image" - it has worked fine
for the last 4 upstream releases of Linux. If you disagree then please
discuss this issue at bug #457467.
True, yaird does not succeed in all cases. Neither do initramfs-tools.
Main difference is that yaird often realize problems at ramdisk *build*
time rather than runtime, so instead of rendering the whole system
unbootable it only causes the installation of the new kernel to fail.
So I ask again: Do the release team still consider yaird too buggy for
release with Lenny?
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----