debcrafters-packages team mailing list archive

[Simon Chopin <2123886@xxxxxxxxxxxxxxxxxx>]

Hi,

I'm sorry to have to tell you this, but you'll have to rework your
questing patch since questing has been released and resolute is now the
new development series.

For resolute, I'd check whether the issue would be fixed by a merge from
Debian, as their upstream version is higher.

Please resubscribe ubuntu-sponsors once you feel this is ready for
another round of reviews.

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2123886

Title:
  Add missing ARM-cores to support Vera-based systems

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Noble:
  In Progress
Status in util-linux source package in Plucky:
  In Progress
Status in util-linux source package in Questing:
  In Progress

Bug description:
  [Impact]

  When running "lscpu" on a Vera-based system, it doesn't report a model
  name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Noble's
  (and previous) versions.

  https://github.com/util-linux/util-
  linux/commit/908777470d403ec30c525472ba0d3701c9c5a223

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Olympus

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems.

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2123886/+subscriptions