** Description changed:

  When upgrading a live USB stick, we use a diverted version of update-
  initramfs installed by casper which arranges for /casper/vmlinuz and
  /casper/initrd.lz at the top level of the CD to be updated.
  Unfortunately this script does not quite operate correctly; it assumes
  that there will be vmlinuz and initrd.gz links in the root directory,
  when in fact they are often (although not exclusively) in /boot.  It
  needs to try both.
  
- DEVELOPMENT BRANCH: This has been addressed in casper 1.237 in maverick:
+ Stable update justification:
  
-   * Make the USB update-initramfs shim cope with vmlinuz and initrd.img
-     being in /boot rather than / (LP: #591207).
+ Impact: USB stick upgrades fail with obscure errors when upgrading the
+ kernel.  This results in very large numbers of duplicate bug reports.
  
- PATCH: http://bazaar.launchpad.net/~ubuntu-
- branches/ubuntu/lucid/casper/lucid/revision/813
+ Development branch: Fixed in casper 1.237/1.253/1.254 by making the
+ writable-USB-stick update-initramfs shim handle vmlinuz and initrd.img
+ being in /boot rather than /, making it more robust against the bits
+ it's copying not existing for various reasons, and making it be a
+ separate executable which can be upgraded in ways that don't involve
+ regenerating the USB stick.
  
- TEST CASE: Build a live USB stick of 10.04 (no need to install it
- anywhere), and upgrade it to the current bits in lucid-updates (should
- fail) and then from scratch to lucid-proposed (should succeed).  There
- are some other problems with this workflow so you may run into other
- failures; for the purposes of this bug, the important thing is that
- /casper/vmlinuz and /casper/initrd.img at the top level of the USB stick
- should be updated with copies of the new /boot/vmlinuz and
- /boot/initrd.img.
+ Patch:
+  
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/casper/lucid/revision/818?compare_revid=812
+  
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/casper/maverick/revision/843?compare_revid=841
  
- REGRESSION POTENTIAL: This diverted script can hardly get worse, given
- that it generally isn't working at all right now.
+ TEST CASE: Create an Ubuntu USB stick, making sure that you do *not*
+ drag the "Stored in reserved extra space" slider all the way to the
+ right in usb-creator (see bug 562312), and upgrade the kernel to the
+ current version in lucid-proposed or maverick-proposed as applicable.
+ 10.04.1 and 10.10 as released should fail.  A lucid daily build dating
+ from after this SRU is accepted should succeed (we're unlikely to do
+ more daily builds of maverick), although this only applies if you find a
+ daily build which contains this fixed version of casper but doesn't have
+ the newest version of the kernel in the archive, so don't worry if you
+ can't test this case.  Also, if you start from 10.04.1 or 10.10 as
+ released, upgrade the casper package to the current version in lucid-
+ proposed or maverick-proposed after this SRU is accepted, and then run
+ 'sudo update-initramfs -u', that should succeed.
+ 
+ Regression potential: I don't think update-initramfs will fail in any
+ more situations due to this change.  Possible sources of regression are
+ problems upgrading the casper package, and testers should also make sure
+ that the upgraded image actually still boots correctly into the new
+ kernel version following this change.
+ 
+ Please note the similar bug 557023, which we're fixing along with this
+ bug, and the related bug 591202 in grub2, which you may run into along
+ the way.

** Changed in: casper (Ubuntu Maverick)
       Status: New => Confirmed

** Changed in: casper (Ubuntu Maverick)
   Importance: Undecided => High

** Changed in: casper (Ubuntu Maverick)
     Assignee: (unassigned) => Colin Watson (cjwatson)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/591207

Title:
  Casper's USB update-initramfs shim should look for initrd.img in /boot

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to