-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Otavio Salvador wrote: | | Well, IMHO, uploads so near of a stable release have to be only to RC | bugs since a so important package like initrd-tools can brake a lot of | things and a lot of users. This is the probably reason of your patches | keep out of this release. |
Sarge is near release for how many months? 6? Sorry, but unless there is no comitted release date, this is no excuse for not applying even the most simple patches. Please take a look at other important packages: They are updated every second week (e.g. util-linux, glibc, udev, etc), as expected. initrd-tools on unstable wasn't changed for more than 4 months, even though a lot of patches and new bug reports have been filed during this time.
For initrd-tools some really severe bugs are marked as "normal" instead, e.g. the not existing migration path from kernel 2.4.x to 2.6.y, if your root disk is sata (#256714). Or not being able to do an interactive file system check at boot time, because the keyboard driver modules are not loaded (#264839). Or the badly broken mapping of scsi module names (#285430, #266239). Etc.
| Sure your patches are important but the maintainer can't trust your | patches about all possible implications and in that case it's not | suitable for uploads near of stable release.
See above. Sarge is not close to stable, if there is no release date set.
| IMHO, the maintainer, | should take all patches (or all more important) and include on another | upload target to experimental distribution while we have a more | trustable release for sid and sarge.
I completely agree to this.
Regards
Harri -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB1rABUTlbRTxpHjcRAk8IAJ0Sw7My3iG7dKUGNCfumvmK+2Ha5gCeKTXd E72w3n/y3/kSCYA5GGQD3DY= =DY3W -----END PGP SIGNATURE-----
