Ubuntu
gcc-defaults package

Versioning mess upon upgrade from bionic to cosmic

Bug #1800746 reported by Joseph Yasi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gcc-defaults (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Since the binary packages have different versions from the source package for the gcc-defaults package, but generate the deb revision based on the source package, some binary packages did not upgrade when upgrading from bionic to cosmic.

In my case, these two packages were the bionic versions:
gdc:amd64 4:8.2.0-1ubuntu2.1
libgphobos-dev:amd64 8.2.0-1ubuntu2.1

cosmic has
gdc:amd64 4:8.2.0-1ubuntu1
libgphobos-dev:amd64 8.2.0-1ubuntu1

gccgo* also has the same problem.

Revision history for this message
Matthias Klose (doko) wrote :

I haven't seen this before. Is this still an issue?

Changed in gcc-defaults (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Yasi (joe-yasi) wrote :

I haven't had this issue in any other upgrades (disco, eoan, focal, groovy) since then. It was a specific version numbering issue between bionic and cosmic, and cosmic is long out of support.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gcc-defaults (Ubuntu) because there has been no activity for 60 days.]

Changed in gcc-defaults (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.