[Bug 1828171] Re: New toolchain updates need to be rebuilt against -security only
Colin Watson
cjwatson at canonical.com
Mon Jun 10 22:13:52 UTC 2019
I had to remove gcc-defaults-ports from cosmic-proposed:
https://launchpad.net/ubuntu/+source/gcc-defaults-ports/1.176ubuntu1.2
and https://launchpad.net/ubuntu/+source/gcc-defaults-
ports/1.178ubuntu1.2 have overlapping binary versions in different
builds, so these were unpublishable and were causing the publisher to
OOPS frequently. Could you please sort out a non-overlapping version
scheme here?
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1828171
Title:
New toolchain updates need to be rebuilt against -security only
Status in binutils package in Ubuntu:
New
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 ggcov package in Ubuntu:
New
Status in binutils source package in Bionic:
Fix Committed
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:
Fix Committed
Status in gcc-7-cross-ports source package in Bionic:
Fix Committed
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:
Fix Committed
Status in gcc-defaults-ports source package in Bionic:
Fix Committed
Status in ggcov source package in Bionic:
Fix Committed
Status in binutils source package in Cosmic:
Fix Committed
Status in eclipse-titan source package in Cosmic:
Fix Committed
Status in gcc-7 source package in Cosmic:
Fix Committed
Status in gcc-7-cross source package in Cosmic:
Fix Committed
Status in gcc-7-cross-ports source package in Cosmic:
Fix Committed
Status in gcc-8 source package in Cosmic:
Fix Committed
Status in gcc-8-cross source package in Cosmic:
Fix Committed
Status in gcc-8-cross-ports source package in Cosmic:
Fix Committed
Status in gcc-defaults source package in Cosmic:
Fix Committed
Status in gcc-defaults-ports source package in Cosmic:
Fix Committed
Status in ggcov source package in Cosmic:
Fix Committed
Bug description:
[Impact]
With LP: #1814369, the toolchain packages have been updated in both cosmic and bionic, but due to an error those packages were built in -proposed as any regular SRU. For toolchain updates there exists a policy that those should be always built against -security *only*, and then released to both -security and -updates.
Since this is not the case with the current toolchain update, we need
to no-change rebuild all of the previously released toolchain packages
in a -security enabled devirt PPA, sync them to -proposed with
binaries and then release into the archives.
[Regression Potential]
As these are toolchain packages, there is always some regression potential. These will be no-change rebuilds so in theory the risk should be low, but the current versions of the packages have not been built against -security only before. It is hard to say how any regressions could manifest themselves.
[Test Case]
Making sure there are no reported regressions in the GCC and binutils test suites. Hopefully this will be sufficient.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+subscriptions
More information about the foundations-bugs
mailing list