bin:google_authorized_keys shipped by this package conflicts with the same binary shipped by src:google-compute-engine-oslogin
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
google-guest-agent (Ubuntu) |
Fix Released
|
Undecided
|
Utkarsh Gupta | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Impish |
Won't Fix
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
========
The two packages src:google-
dpkg: error processing archive /tmp/apt-
trying to overwrite '/usr/bin/
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
[Test Plan]
===========
$ lxc launch images:
$ lxc shell ktemp
$ apt update
$ apt install google-
$ apt install google-guest-agent
This should result in failure. Whilst these two should co-install together.
Another thing to note is the file list that's going to be provided:
Without fix:
/lib/systemd/
/lib/systemd/
/lib/systemd/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/share/
/usr/share/
With the fix:
/lib/systemd/
/lib/systemd/
/lib/systemd/
/usr/bin/
/usr/bin/
/usr/share/
/usr/share/
That is, the google_
[Where Problems Could Occur]
=======
Whilst this is totally broken in Kinetic and in the -proposed pocket of Jammy, Impish, and Focal, it can't get any worse than that. But an edge case might happen when the person has just installed google-guest-agent and started to use the binary from there, instead of using it from the original source (the oslogin package). But this hasn't been published in any stable releases so I don't see that happening, really. :)
Furthermore, since Impish is going to be EOL'd in two weeks, it's not worth fixing it there at all because it'll take us at least sometime to get this verified, et al, only to have Impish EOL'd so marking this as Won't Fix.