[Bug 2046250] Re: [needs-packaging] raspi-utils (replacement for raspberrypi-userland)

[Simon Chopin]

Pragyansh (or Dave), could you please clarify for me the copyright
situation? The documented copyright on debian/ is for Raspberry Pi Ltd,
but d/changelog only has your entry, and from the review Dave did I'm
guessing we have non-trivial contributions to the packaging?

-- 
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/2046250

Title:
  [needs-packaging] raspi-utils (replacement for raspberrypi-userland)

Status in raspberrypi-userland package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  URL: https://github.com/raspberrypi/utils
  License: GPL-2 or BSD-3-Clause
  Notes:

  The raspberrypi-userland package was deprecated upstream some time ago
  (prior to noble in fact), with the majority of the utilities
  (dtoverlay, dtmerge, vcgencmd, vclog, etc.) moving to the raspi-utils
  package. Recent versions of rpi-eeprom-update (which we need to pull
  in to fix other issues, e.g. LP: #2078806) now include functionality
  introduced since the move to raspi-utils.

  We should include raspi-utils in oracular with all the appropriate
  Breaks + Replaces bits to handle replacing the existing package.

  [ Test Plan ]

  * With EEPROM boot firmware from current Ubuntu:

  * Build the package in ppa:waveform/raspi-utils
  * Test the function of the package on supported models. Specifically, on Pi 5, Pi 4, CM4, and at least one of the 2/3/3+ generation
  * Especially: check vcgencmd, dtoverlay, dtparam still operate as expected as these are the major components used by other utilities

  * Update EEPROM boot firmware to current RaspiOS version and repeat
  above tests.

  [ Regression Potential ]

  Given the nature of some of the utilities (e.g. low-level mailbox
  communication in vcmailbox, device-tree overlay manipulation in
  dtoverlay and dtparam), there is a reasonable risk that we may break
  functionality by upgrading. However, these utilities tend to move in
  step with the RPi firmware, and if we are updating that firmware,
  these utilities should be updated too in order to minimize the risk of
  regression.

  Nonetheless, the test plan should be followed on a wide variety of
  models, and as much functionality should be tested as possible, with
  old and new firmware to spot potential regressions.

  [ Addendum ]

  Note to self: don't forget to update the seeds

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