[Bug 2025458] Autopkgtest regression report (libunwind/1.3.2-2build2.1)

Ubuntu SRU Bot 2025458 at bugs.launchpad.net
Sun Jul 2 22:28:13 UTC 2023


All autopkgtests for the newly accepted libunwind (1.3.2-2build2.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-aws-5.19/5.19.0-1028.29~22.04.1 (arm64)
linux-aws-6.2/6.2.0-1006.6~22.04.1 (arm64)
linux-azure-5.19/5.19.0-1027.30~22.04.2 (arm64)
linux-gke/5.15.0-1037.42 (arm64)
linux-lowlatency/5.15.0-76.83 (arm64)
linux-lowlatency-hwe-5.19/5.19.0-1028.29~22.04.1 (arm64)
linux-nvidia-tegra/5.15.0-1014.14 (arm64)
linux-xilinx-zynqmp/5.15.0-1022.26 (arm64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#libunwind

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/2025458

Title:
  SRU: rebuild libunwind with GCC 11.4

Status in libunwind package in Ubuntu:
  New
Status in libunwind source package in Jammy:
  Fix Committed

Bug description:
  Reported in LP: #1997161

  after updating GCC 11 in 22.04 LTS to 11.3, and now to 11.4, linking
  with the static libraries provided by libunwind-dev fails with:

  lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux-
  gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with
  LTO version 11.2 instead of the expected 11.3

  This happens, because gcc-11 bumped the LTO version in 11.3
  (11.3.0-1ubuntu1~22.04), plus the static libraries are not stripped in
  the packaging.

  Fixes could be to change the packaging, disable the LTO build for the
  package, or just rebuild with the new compiler.

  For 22.04 LTS, the least invasive action seems to be the no-change
  rebuild.

  To verify the packages: check that the package builds with the correct
  compiler version, and that the tests succeed during the build.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2025458/+subscriptions




More information about the Ubuntu-openstack-bugs mailing list