Comment 20 for bug 672964

Hello Jean-Baptiste,

Jean-Baptiste Lallement [2010-11-22 11:23 -0000]:
> I'm unable to reproduce the original issue with the provided test case.
> The diversion is removed and update-initramfs is run in the postinst
> script, copying the right udevadm to the initramfs.

Ah, you mean that calling the udev postinst in step 3 updates the
initramfs _again_, and this time a correct one.

Right, so the check for the broken initramfs should be done before
calling the postinst. I updated the test case in the description
accordingly.

> But, if I run update-initramfs without removing the diversion first
> (running steps 1 & 2 or skipping enable_udevadm in postinst) then the
> current version in -updates generates a broken initramfs and the version
> in -proposed generates a correct initramfs.

That's the situation this update was meant to fix indeed. So I'll call
this a succesful verification.

> So this fix fixes an issue, but I am not sure that it fixes the issue
> reported here originally.

The original description and followups seem to indicate exactly that
problem. Unfortunately it is hard to provide a simple test case for
this, as the actual bug would only occur if multiple kernel ABIs are
involved during upgrade. I. e. the first udevadm trigger during the
update updates the initramfs for ABI 2.6.X (a broken one due to this
bug), and later on in the game a new kernel 2.6.Y gets installed, and
apparently the final udev configure then only updated the initramfs
for 2.6.Y, but not for .X any more.

Thanks,

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)