[Yaird-devel] Bug#477054: Bug#477054: yaird: Generates invalid initrds which reference /lib/i686/mov/

[Jonas Smedegaard]

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

On Mon, Apr 21, 2008 at 01:14:06AM +0300, Andrei Popescu wrote:
>On Sun, Apr 20, 2008 at 11:08:40PM +0200, maximilian attems wrote:
>> On Sun, Apr 20, 2008 at 11:40:39PM +0300, Andrei Popescu wrote:
>> > On Sun, Apr 20, 2008 at 06:37:52PM +0100, Nick Burch wrote:
>> >  
>> > > The initrds were all generated using update-initramfs
>> > 
>> > ,----[ dpkg -S update-initramfs ]
>> > | initramfs-tools: /etc/initramfs-tools/update-initramfs.conf
>> > | initramfs-tools: /usr/sbin/update-initramfs
>> > | initramfs-tools: /usr/share/man/man5/update-initramfs.conf.5.gz
>> > | initramfs-tools: /usr/share/man/man8/update-initramfs.8.gz
>> > `----
>> > 
>> > I think your bug belongs to the initramfs-tools package, if you 
>> > don't mind I will reassign (that is if the BTS allows a 
>> > non-maintainer to do this).

I believe it is not "forbidden" for non-maintainers to reassign 
packages.  And you might be right in this case.

Not all package maintainers treat bugreports and bugreporters equally 
nice, however, so reassigning a bugreport raise the risk of not being 
treated nicely.

Also, the act of reassigning can itself be seen as provocation to some 
package maintainers.

Therefore I recommend to be extra cautious and only reasssing if certain 
that the bug can only be tied to the new package (neither tied to the 
old package nor to multiple bugs needing a fork of the bugreport).

So when you only _might_ be right, it was sane to not do it :-)


>> you snipped all the interesting part of that bug report! please 
>> reread start and subject before radomly reassigning!
>
>I have read those. And I also read the part about unpacking it and 
>looking at busybox. I may be wrong, but yaird AFAIK does not include 
>busybox in the initrd. Also I wasn't aware of the possibility to use 
>yaird with update-initramfs.

With yaird you _can_ include busybox in the ramdisk.  You are right that 
it is not the default behaviour, but the bugreporter mentioned busybox 
while _debugging_ the problem, not as part of the core problem itself.

It is not uncommon to get confused with the actual steps involved in 
handling initial ramdisks.  Indeed, update-initramfs is not used with 
yaird, but this only is an indication that initramfs-tools is installed 
on the system, not that it is the generator actually used on that system 
to generate ramdisks.

Even then, I do find it sane to consider initramfs-tools being involved 
in this bug.  But package maintainers of yaird and initramfs-tools do 
not treat bugreports and bugreporters equally, which migh confuse (or 
worse) our bugreporter.  So please let us treat this bug as 
yaird-related only, until certain that it is not!


Kind regards,

  - Jonas

- -- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  - Enden er nær: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIDHA9n7DbMsAkQLgRAmrgAJ4rJX5Fcn22EUoWfyaJ3MT6o8wVoACdEouZ
M/Ha/qUAGHgmR/Dpv83ysNw=
=eXD4
-----END PGP SIGNATURE-----