[Bug 2019465] Please test proposed package

Ɓukasz Zemczak 2019465 at bugs.launchpad.net
Thu Jul 13 13:45:33 UTC 2023


Hello Matthias, or anyone else affected,

Accepted gcc-10 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gcc-10/10.5.0-1ubuntu1~22.04 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gcc-10-cross (Ubuntu Jammy)
       Status: New => Fix Committed

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

Title:
  SRU: update gcc-10 to 10.5.0 and gcc-11 to 11.4.0

Status in gcc-10 package in Ubuntu:
  New
Status in gcc-10-cross package in Ubuntu:
  New
Status in gcc-10-cross-ports package in Ubuntu:
  New
Status in gcc-11 package in Ubuntu:
  New
Status in gcc-11-cross package in Ubuntu:
  New
Status in gcc-11-cross-mipsen package in Ubuntu:
  New
Status in gcc-11-cross-ports package in Ubuntu:
  New
Status in gcc-10 source package in Focal:
  Fix Committed
Status in gcc-10 source package in Jammy:
  Fix Committed
Status in gcc-10-cross source package in Jammy:
  Fix Committed
Status in gcc-10-cross-ports source package in Jammy:
  Fix Committed
Status in gcc-11 source package in Jammy:
  Fix Committed
Status in gcc-11-cross source package in Jammy:
  Fix Committed
Status in gcc-11-cross-ports source package in Jammy:
  Fix Committed
Status in gcc-10 source package in Kinetic:
  Fix Committed
Status in gcc-10-cross source package in Kinetic:
  Fix Committed
Status in gcc-10-cross-ports source package in Kinetic:
  Fix Committed
Status in gcc-11 source package in Kinetic:
  Fix Committed
Status in gcc-11-cross source package in Kinetic:
  Fix Committed
Status in gcc-11-cross-ports source package in Kinetic:
  Fix Committed
Status in gcc-10 source package in Lunar:
  Fix Committed
Status in gcc-10-cross source package in Lunar:
  Fix Committed
Status in gcc-10-cross-ports source package in Lunar:
  Fix Committed
Status in gcc-11 source package in Lunar:
  Fix Committed
Status in gcc-11-cross source package in Lunar:
  Fix Committed
Status in gcc-11-cross-mipsen source package in Lunar:
  Fix Committed
Status in gcc-11-cross-ports source package in Lunar:
  Fix Committed

Bug description:
  update gcc-11 to GCC 11.4.0
  update gcc-10 to GCC 10.5.0. Note that the GCC 10.5 release is expected in early July 2023. The test rebuilds mentioned below were done with a version taken from the gcc-10 branch.  GCC 10 is not used as a default compiler in all the targeted releases.

  There are no regressions in the gcc-10 and gcc-11 testsuites.

  Test rebuilds for main in lunar, kinetic and jammy were done. The
  analysis can be found in LP: #1995499.

  The packages were built in the ubuntu-toolchain-r/ppa PPA with only
  the security pocket enabled.

  The gcc-10 packages were done with the GCC 10.5.0 release candidate,
  and later updated to the final 10.5.0 release. The only change besides
  the version number is a bug fix in the D frontend.

  Test rebuilds for main in focal were done.
   
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230629-focal-focal.html
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230629-focal-gcc-focal.html

  There is one regression, dee on riscv64, timing out on the buildd in
  the testsuite. Newer uploads of the dee package have the testsuite
  disabled on riscv64, so apparently a known issue. We can backport that
  fix, if wanted.

  There are a few progressions: mir, python-openstacksdk, swift,
  udisks2, all riscv64 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2019465/+subscriptions




More information about the foundations-bugs mailing list