[Yaird-devel] Bug#457177: Bug#457177: keep yaird out of Testing

[Jonas Smedegaard]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

package yaird
clone 457177 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
retitle -1 yaird: overheating: critical acpi modules not in ramdisks
retitle -2 yaird: cmdline ignores critical boot arguments
retitle -3 yaird: lack of support for some Debian archs
retitle -4 UUID, Label - apparently only works for some fs
retitle -5 yaird: missing firmware: no way to initiate some SCSI drivers
retitle -6 yaird: no cryptsetup support
retitle -7 yaird: no dmraid support
retitle -8 yaird: no usplash support
retitle -9 yaird: breaks on evey new kernel due to hardcoded parsing
retitle -10 yaird: dead upstream
thanks

On Thu, Dec 20, 2007 at 11:19:56AM +0100, maximilian attems wrote:
>yaird has a bunch of failures that make it not fit for a release:
>* overheating - none of the acpi modules lands on initramfs
>  for some boxes it is *really* critical to load them earliest
>* cmdline - ignores any of the boot passed arguments
>  even critical ones like root, rootfs or rootdelay
>* missing debian arch support - for example s390 
>* UUID, Label - apparently only works for some fs
>* missing firmware - several scsi drivers need firmware inside initramfs
>  no loader on initramfs nor any mechanism to add it
>* missing cryptsetup support see #336599
>* no dmraid support
>* no usplash support
>* 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
>* dead upstream - 24 debian revsion
>
>
>speaking as debian kernel arch maintainer none of aboves topic
>saw an improvement since etch release,
>thus i'm asking to keep yaird out of testing.

I find it relevant to discuss bugs in yaird. Also wether or not yaird is 
"fit for release" based on the accumulation of bugs. But it makes best 
sense to me keeping those discussions separate.

I asked you to please refer to bugreports regarding the issues raised 
here, but sadly you only found it important to claim importance, not 
help clarify the sanity of that imortance.

I have now forked bugreports for each of the issues raised here (and 
will afterwards merge with existing bugreports as relevant, to make 
other bugreporters and -participants aware of this metabug). Please let 
us discuss the details of each individual bug as such, and at this 
bugreport only discuss the "metabug" that is caused by them all judged 
together.


Kind regards,

  - jonas

- -- 
Jonas Smedegaard   <jonas at jones.dk>   http://www.jones.dk/~jonas/
IT-guide dr. Jones    <dr at jones.dk>   http://dr.jones.dk/    +45 40843136
Debian GNU/Linux    <js at debian.org>   http://www.debian.org/
GnuPG(1024D/C02440B8): 9A98 C6EB C098 9ED0 3085  ECA9 9FB0 DB32 C024 40B8
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHbTC1n7DbMsAkQLgRAusAAKCW1Yvljz5e0GJGIuHthZXa9QvJmwCfcbgk
1Ds76kz0FEFv3inaieckuYo=
=MTkz
-----END PGP SIGNATURE-----