Don't provide transitional package for python3-google-compute-engine, add Breaks: in google-guest-agent instead
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gce-compute-image-packages (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
google-guest-agent (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* gce-compute-
* The fix is not providing the empty python3-
[Test Case]
* Set up a system with the unfixed version of the packages, including python3-
* Upgrade to the new set of packages:
apt-get upgrade
* Observe that the google-guest-agent is kept back
* Upgrade google-guest-agent manually:
apt install google-guest-agent
* This should succeed, removing python3-
[Where problems could occur]
* The packages may become uninstallable upon upgrade or dist-upgrade. Testing was performed to avoid such regressions.
* Since the aim of this fix is preventing accidental upgrades should a security update of the affected packages be released the fix will prevent automatic application of this updated. In such case the the transitional package can be reintroduced and the Breaks: can be converted to a versioned Breaks: on the non-transitional package versions.
description: | updated |
description: | updated |
description: | updated |
description: | updated |
I've never heard of the 'empty python3- google- compute- engine transitional package'; for upstream packaging, we use "Conflicts: python3- google- compute- engine" and this will cause the top level package (called google- compute- engine upstream, I think called gce-compute- image-packages in Ubuntu) to be skipped in upgrades, and an administrator would have to issue dist-upgrade to enable the automatic removal of the conflicting package.