** Description changed:

+ [Note to SRU members]
+ 
+ Attention! This is a toolchain update, it requires to be released into both 
-updates and -security at the same time. Also, it requires some special 
handling so it's best to leave it in the hands of the accepting SRU team member.
+ For instance, currently the gcc-9 parts of the SRU are basically 
verification-failed until the situation is cleared. So those should *not* be 
released without prior consultation.
+ 
+ Thank you!
+ 
+ [Overview]
+ 
  as done before in LP: #1879481 with GCC 9.3.0 and GCC 10.2.0, updating
  again to GCC 9.4.0 and GCC 10.3.0 in 20.04 LTS, 20.10 and 21.04.  GCC
  10.3.0 is already in 21.04 (hirsute), so no need to update that compiler
  there as well.
  
   - gcc-10, update to the gcc-10.3.0 release
   - gcc-9, update to the gcc-9.4.0 release
   - corresponding gcc-cross packages
  
  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages
  built with only the security pocket enabled.
  
  [Impact]
  Provide an upstream release for GCC 10.3, and an upstream release for GCC 9.4.
  gcc-9 is the default compiler for focal, gcc-10 the default compiler for 
groovy.
  
  [Regression Potential]
  There is regression potential, however with a test rebuild of the main 
portion of the archive for both focal and groovy, we make sure that we don't 
see any regressions in package builds.
  
  [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).  No test 
rebuild is done for hirsute, as gcc-9 is not the default compiler anymore.
  
  Also check that the rebuilt kernel boots on all architectures.
  
  TODO: 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 gcc-9, gcc-10, python3.8, and python3
  -stdlib-extensions. The GCC and Python packages should not infer with
  each other.
  
  [Validation]
  Analyze the GCC build logs for regressions.
  For the cross builds, just make sure that the packages build using
  the updated sources.
  
  Summary of the test rebuilds:
  
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210602-focal-focal.html
  
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210602-focal-gcc-focal.html
  
  
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210601-groovy-groovy.html
  
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210601-groovy-gcc-groovy.html
  
- 
- The first one in each paragraph is a reference build, the second one the test 
rebuild with the updated components.
+ The first one in each paragraph is a reference build, the second one the
+ test rebuild with the updated components.
  
  There are no additional regressions except for sssd in focal, which is
  unrelated to the GCC update, and only exposed by Python 3.8.10 which was
  fixed by a separate SRU. Note that the riscv64 builds are purely
  informational, and are not checked for any regressions.

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

Title:
  SRU: update gcc-9 and gcc-10 packages for focal, groovy and hirsute

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to