Add support for lts-wily kernel flavours in trusty

Hello Adam, or anyone else affected,

Accepted debian-installer into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian-installer/20101020ubuntu318.33 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Adam, or anyone else affected,

Accepted livecd-rootfs into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.208.9 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

The server side changes have been made to generate ISOs with the new kernels.

Tested amd64 image successfully using roughly what is in 'notes.txt' at
 https://gist.github.com/smoser/1057704

The provided preseed does unattended install and sets 'ubuntu' user with 'ubuntu' password.

Kernels used:
 $ md5sum kernel initrd
 6725de97b08c3a79ef367d8a8d45b925 kernel
 66ccbff804a89bca2ff23dd7c62e0b04 initrd
 $ ls -l kernel initrd
 $ ls -l kernel initrd
 -rw-rw-r-- 1 ubuntu ubuntu 22544400 Dec 9 20:49 initrd
 -rw-rw-r-- 1 ubuntu ubuntu 6708504 Dec 9 20:49 kernel

Install done with:
 qemu-system-x86_64 -enable-kvm -m 1024 -curses -device virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive if=virtio,file=disk.img,cache=unsafe -no-reboot -kernel kernel -initrd initrd -append "apt-setup/proposed=true nomodeset fb=false priority=critical locale=en_US url=http://10.245.168.15:9900/preseed"

After booting, system shows:
 $ lsb_release -sc
 trusty
 $ uname -r
 4.2.0-22-generic
 $ dpkg -S /boot/vmlinu?-$(uname -r)
 linux-image-4.2.0-22-generic: /boot/vmlinuz-4.2.0-22-generic

Same process for i386 images currently at -proposed.
 $ md5sum kernel initrd
 21e31eaae6a3fb26b9ad26ca472db3ee kernel
 c161d6fc793cc8c34cd593e5ab34615a initrd
 $ ls -l kernel initrd
 -rw-rw-r-- 1 ubuntu ubuntu 20707800 Dec 9 20:48 initrd
 -rw-rw-r-- 1 ubuntu ubuntu 6420992 Dec 9 20:48 kernel

Install done with:
  qemu-system-i386 -enable-kvm -m 1024 -curses -device virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive if=virtio,file=disk.img,cache=unsafe -no-reboot -kernel kernel -initrd initrd -append "apt-setup/proposed=true nomodeset fb=false priority=critical locale=en_US url=http://10.245.168.15:9900/preseed"

Booted system, logged in then:
 $ lsb_release -sc
 trusty
 $ uname -r
 4.2.0-22-generic
 $ dpkg -S /boot/vmlinu?-$(uname -r)
 linux-image-4.2.0-22-generic: /boot/vmlinuz-4.2.0-22-generic
 $ uname -m
 i686

Because I had access to a ppc64el system (wily) that I could fairly
easily test this on, I went ahead and verified ppc64el with the following.

## get qemu/kvm setup
$ sudo apt-get update
$ sudo apt-get install qemu-system-ppc64
$ sudo chmod 666 /dev/kvm # i know, but rather than dealing with log out or sg
$ sudo ppc64_cpu --smt=off
$ sudo modprobe kvm_hv

$ burl="http://ports.ubuntu.com/dists/trusty-proposed/main/installer-ppc64el/current/images/wily-netboot/ubuntu-installer/"

$ wget "$burl/ppc64el/vmlinux" -O kernel
$ wget "$burl/ppc64el/initrd.gz" -O initrd

$ md5sum kernel initrd
685aafad26b086740a752de521d6e08a kernel
de554fab88e5422223212d3c2434f939 initrd

$ ls -l kernel initrd
-rw-rw-r-- 1 ubuntu ubuntu 21925967 Dec 9 20:50 initrd
-rw-rw-r-- 1 ubuntu ubuntu 22323480 Dec 9 20:50 kernel

$ qemu-img create -f qcow2 disk.img 4G

$ PRESEED_URL=http://some.url
$ qemu-system-ppc64 -echr 0x05 -enable-kvm -m 1024 -nographic \
   -device virtio-net-pci,netdev=net00 -netdev type=user,id=net00 \
   -drive if=virtio,file=disk.img,cache=unsafe \
   -no-reboot -kernel kernel -initrd initrd \
   -append "apt-setup/proposed=true nomodeset fb=false priority=critical console=hvc0 locale=en_US url=$PRESEED_URL"

## now boot system
$ mv disk.img disk.img.pristine
$ chmod ugo-w disk.img.pristine
$ qemu-img create -f qcow2 -b disk.img.pristine disk.img
$ qemu-system-ppc64 -echr 0x05 -enable-kvm -m 1024 -nographic \
   -device virtio-net-pci,netdev=net00 -netdev type=user,id=net00 \
   -drive if=virtio,file=disk.img,cache=unsafe

## Then boot the system, removing the '-kernel and -initrd'
## verify that I'm running the right kernel

ubuntu@ubuntu:~$ uname -r
4.2.0-23-generic
ubuntu@ubuntu:~$ lsb_release -sc
trusty
ubuntu@ubuntu:~$ dpkg -S /boot/vmlinu?-$(uname -r)
linux-image-4.2.0-23-generic: /boot/vmlinux-4.2.0-23-generic

For brevity, I've now tested netboot kernel/initramfs installation via preseed on each of i386, x86_64 and ppc64el.
The preseed I used is attached here.

This bug was fixed in the package debian-installer - 20101020ubuntu318.33

---------------
debian-installer (20101020ubuntu318.33) trusty; urgency=medium

  * Add lts-wily variants for all targets except for e500, for which
    support was dropped with the utopic kernel and up (LP: #1524366)
  * Add lts-xenial variants for all targets but e500, commented out.

 -- Adam Conrad <email address hidden> Wed, 09 Dec 2015 07:35:12 -0700

This bug was fixed in the package livecd-rootfs - 2.208.9

---------------
livecd-rootfs (2.208.9) trusty; urgency=medium

  * Switch from lts-vivid to lts-wily HWE kernels (LP: #1524366)

 -- Adam Conrad <email address hidden> Wed, 09 Dec 2015 10:47:37 -0700

The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.