[Bug 1814369] Re: update toolchain packages for bionic

[Łukasz Zemczak]

Hello Matthias, or anyone else affected,

Accepted gcc-8-cross into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/gcc-8-cross/18ubuntu0.2 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 and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. 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-8-cross (Ubuntu Bionic)
       Status: New => Fix Committed

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

Title:
  update toolchain packages for bionic

Status in eclipse-titan package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in eclipse-titan source package in Bionic:
  Fix Committed
Status in gcc-7 source package in Bionic:
  Fix Committed
Status in gcc-7-cross source package in Bionic:
  New
Status in gcc-7-cross-ports source package in Bionic:
  New
Status in gcc-8 source package in Bionic:
  Fix Committed
Status in gcc-8-cross source package in Bionic:
  Fix Committed
Status in gcc-8-cross-ports source package in Bionic:
  Fix Committed
Status in gcc-defaults source package in Bionic:
  New
Status in gcc-defaults-ports source package in Bionic:
  New
Status in eclipse-titan source package in Cosmic:
  New
Status in gcc-7 source package in Cosmic:
  Fix Committed
Status in gcc-7-cross source package in Cosmic:
  New
Status in gcc-7-cross-ports source package in Cosmic:
  New
Status in gcc-8 source package in Cosmic:
  New
Status in gcc-8-cross source package in Cosmic:
  New
Status in gcc-8-cross-ports source package in Cosmic:
  New
Status in gcc-defaults source package in Cosmic:
  New
Status in gcc-defaults-ports source package in Cosmic:
  New

Bug description:
  This is a follow-up to LP: #1769657. I'd like to update the toolchain
  packages in bionic, to state which we have in disco in Junuary 2019:

   - gcc-8, update to the gcc-8.3.0 release
   - gcc-7, updates to the gcc-7.4.0 release
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

  [Impact]
  Provide an upstream release for GCC 7, and update GCC 8 to the 8.3.0
  release

  [Regression Potential]
  There is regression potential, however with a test rebuild of the complete archive no regressions were found.

  [Test Case]
  No regressions in the GCC test suite, and no regressions in the test
  rebuild of the main component of the archive (all architectures)

  As a test, a complete archive rebuild was performed, and no
  regressions were found with this new package. The archive rebuild also
  contained updated versions of OpenJDK, OPenSSL, gcc-7, gcc-8,
  python3.6 and python3.7. The OpenJDK, OpenSSL, GCC and Python packages
  should not infer with each other.

  [Validation]
  Analyze the build logs for regressions.
  For the cross builds, just make sure that the packages build using
  the updated sources.

  Summary of the test rebuilds:
  http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
  http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html

  The first one is a reference build, the second one the test rebuild
  with the updated components.

  An analysis of the build failures was done in
  https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 (Sheet2).

  No regressions attributed to GCC are shown with the test rebuild for
  main, the universe component looks ok, except for packages relying on
  specific GCC versions (ggcov: LP: #1817554), packages needing no-
  change uploads (e.g. eclipse-titan).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eclipse-titan/+bug/1814369/+subscriptions