[Bug 1895137] Re: [MIR] rpi-eeprom

[Christian Ehrhardt ]

> > - Please consider updating to a newer version before you SRU things to
> >=Focal
>
> Is it best at this point to fix the existing 7.8 upload, or reject that
> and fix all this in a new 9.0 upload? Happy to do whichever is easier
> from the MIR/security team's perspective.

IMHO cancel what is there, get it right in Groovy or later and then
SRU the correct thing.
The usual reason is this, right now nothing is in Focal, so you can
(under constraints) backport anything.
But if you have 7.8+fixes there first and then plan to update to 9.0
this update would have to follow SRU rules.
Which means you'd need to retain any behavior of the former version
making it much harder for you.

TL;DR: "Get it right first, SRU once afterwards" usually is the right
approach

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

Title:
  [MIR] rpi-eeprom

Status in raspberrypi-userland package in Ubuntu:
  New
Status in rpi-eeprom package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
  The package is in proposed, pending a correction to Architecture to permit it to migrate to multiverse (LP: #1884748).

  [Rationale]
  The package is required for updating the boot EEPROM on the Raspberry Pi 4.

  [Security]
  I am not aware of any open CVEs against the tools in rpi-eeprom.

  [Quality assurance]
  The package is extensively used upstream on Raspbian, and is obviously actively maintained there. There is no meaningful test suite included in the package, but the contents of the package are regularly exercised in image testing (and boot EEPROM testing).

  [UI standards]
  Manual pages are included for both utilties included in the package (rpi-eeprom-config and rpi-eeprom-update), but localization is missing from both utilities at present. However, most users will never use these utilities directly. Rather, they are typically launched by a systemd service on boot which automatically applies new versions of the boot EEPROM.

  [Dependencies]
  The package depends on binutils, python3, and pciutils, all of which are already in main. It also depends on linux-firmware-raspi2 and libraspberrypi-bin which are the subject of other MIRs (LP: #1867813, LP: #1895133).

  [Standards compliance]
  The package installs its scripts under /usr/bin.

  [Maintenance]
  The package is maintained by the Ubuntu Foundations team.

  [Background information]
  As this is a dependency for keeping the boot EEPROM on the Raspberry Pi 4 up to date, the intention is to install this by default in all pi-related images going forward.

  
  ---

  
  [Availability]
  The package is already in universe.

  [Rationale]
  The package is depended upon by the new raspi-common seed, for inclusion in all pi related images. The reason for its inclusion in the seed is that the libraspberrypi-bin package provides the vcgencmd and dtoverlay utilities which are both required by rpi-eeprom (the subject of a separate MIR, LP: #1895137) for updating the boot EEPROM on the Raspberry Pi 4.

  The libraspberrypi0 package is a dependency of libraspberrypi-bin and
  both are built from the raspberrypi-userland source package.

  [Security]
  I am not aware of any open CVEs against the tools in libraspberrypi-bin or the libraries in libraspberrypi0.

  It may be worth noting that the -bin package installs a udev rule (in
  /lib/udev/10-local-rpi.rules) permitting members of the "video" group
  access to /dev/vchiq, which is required for all the VC related
  utilities (including vcgencmd, raspivid, and raspistill) to be
  operated without root privileges.

  [Quality assurance]
  The package is extensively used upstream on Raspbian, and is obviously actively maintained there. There is no meaningful test suite included in the package, but the contents of the package are regularly exercised in image testing (and boot EEPROM testing).

  [UI standards]
  I've added manual pages for all the utilities I'm able to, but localization is missing from all utilities at present. However, most users will never use these utilities directly (bar, perhaps, the raspivid and raspistill utilities for the camera module). Instead the most common scenario is that the utilities will be used (invisibly) by other scripts (e.g. rpi-eeprom-update) for maintenance purposes like manipulating the boot EEPROM.

  [Dependencies]
  As noted above, libraspberrypi-bin depends on libraspberrypi0. It also depends on device-tree-compiler and libc6, both of which are already in main. libraspberrypi0 in turn merely depends on libc6.

  [Standards compliance]
  The package installs its binaries under /usr/bin, and its libraries under /usr/lib. Upstream does not version their API, so the libraries are unversioned.

  [Maintenance]
  The package is maintained by the Ubuntu Foundations team.

  [Background information]
  As noted above, the package is a dependency of the recently added raspi-common seed (https://lists.ubuntu.com/archives/ubuntu-release/2020-September/005086.html). As it is a dependency for keeping the boot EEPROM on the Raspberry Pi 4 up to date, the intention is to install this by default in all pi-related images going forward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/raspberrypi-userland/+bug/1895137/+subscriptions