[Bug 1805668] Re: Building armhf and arm64 Raspberry Pi 3 images

[Launchpad Bug Tracker]

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

---------------
livecd-rootfs (2.525.12) bionic; urgency=medium

  * Key netplan delegation to NetworkManager on presence of
    /usr/sbin/NetworkManager, not on /usr/lib/NetworkManager which may have
    hooks from other packages (i.e., wpasupplicant).

  [ Cody Shepherd ]
  * Include snaps in image manifests (LP: #1805497)
  * Change call to add grub efi packages using new create_manifests()
    function.

 -- Steve Langasek <steve.langasek at ubuntu.com>  Mon, 10 Dec 2018
12:46:46 -0800

** Changed in: livecd-rootfs (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

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

Title:
  Building armhf and arm64 Raspberry Pi 3 images

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in raspi3-firmware package in Ubuntu:
  Fix Released
Status in u-boot package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Fix Released
Status in raspi3-firmware source package in Bionic:
  Fix Committed
Status in u-boot source package in Bionic:
  Fix Committed
Status in livecd-rootfs source package in Cosmic:
  Won't Fix
Status in raspi3-firmware source package in Cosmic:
  Confirmed
Status in u-boot source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  One of our long-term goals is to support the same set of platforms for both classical Ubuntu and ubuntu-core. We currently provide official images for the Raspberry Pi 3 for both the core16 and core18 bases but do not provide the same for Ubuntu classic.
  Since it's a 'feature' we're essentially lacking since long, we want to have the new device also supported in our current LTS (bionic).

  [Fix]

  For the classic raspi3 support we will be using the ubuntu-image classic image building tool which is specifically designed for creating preinstalled images. The support for that has already been SRUed in the latest ubuntu-image.
  For the full image build support to be complete, the following list of changes need to be backported (SRUed) into the respective stable series:

   * livecd-rootfs - all the changes regarding classic image build, gadget tree selection and raspi3 rootfs generation.
   * u-boot - bionic will need to be updated to at least 2018.03+dfsg1-2ubuntu2.
   * raspi3-firmware (bionic only) - needs to be updated to at least the version we have in cosmic. Without this change, the console is flooded with firmware error messages every 2 seconds.
   (vorlon) this should be updated specifically to the version of raspi3-firmware that we are using in the gadget snap - currently 1.20180919 - and not to another.

  [Test Case]

   * Run a bionic livefs build of raspi3+armhf with proposed enabled (IMAGEFORMAT=ubuntu-image and PROJECT=ubuntu-cpc), make sure the build succeeds and that the resulting image boots on a raspi3.
   * Run a bionic livefs build of raspi3+arm64 with proposed enabled (IMAGEFORMAT=ubuntu-image and PROJECT=ubuntu-cpc), make sure the build succeeds and that the resulting image boots on a raspi3.
   * Make sure that none of the other bionic daily images fail to build

  [Regression Potential]

  There is some potential that an invalid backport of livecd-rootfs
  functionality could result in the inability to create new ubuntu-core
  images or any of the other existing flavors. But in case of such a
  regression we would see it instantly after the package lands in
  bionic-proposed as we are building daily images with -proposed
  enabled. As for the other packages, there probably is some regression
  potential, but since the versions are backports from disco/cosmic, the
  risk is probably very small.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1805668/+subscriptions