[Bug 1980725] [NEW] bin:google_authorized_keys shipped by this package conflicts with the same binary shipped by src:google-compute-engine-oslogin

[Utkarsh Gupta]

Public bug reported:

[Impact]
========

The two packages src:google-compute-engine-oslogin and src:google-guest-
agent cannot be co-installed together because they ship the same binary
so dpkg throws the following error out:

dpkg: error processing archive /tmp/apt-dpkg-install-USEDmn/2-google-guest-agent_20220622.00-0ubuntu1_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/google_authorized_keys', which is also in package google-compute-engine-oslogin 20210907.00-0ubuntu2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

[Test Plan]
===========

$ lxc launch images:ubuntu/kinetic ktemp
$ lxc shell ktemp
$ apt update
$ apt install google-compute-engine-oslogin
$ 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/system/google-guest-agent.service
/lib/systemd/system/google-shutdown-scripts.service
/lib/systemd/system/google-startup-scripts.service
/usr/bin/google_authorized_keys
/usr/bin/google_guest_agent
/usr/bin/google_metadata_script_runner
/usr/share/doc/google-guest-agent/changelog.Debian.gz
/usr/share/doc/google-guest-agent/copyright

With the fix:

/lib/systemd/system/google-guest-agent.service
/lib/systemd/system/google-shutdown-scripts.service
/lib/systemd/system/google-startup-scripts.service
/usr/bin/google_guest_agent
/usr/bin/google_metadata_script_runner
/usr/share/doc/google-guest-agent/changelog.Debian.gz
/usr/share/doc/google-guest-agent/copyright

That is, the google_authorized_keys shouldn't be shipped.

[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. :)

** Affects: google-guest-agent (Ubuntu)
     Importance: Undecided
     Assignee: Utkarsh Gupta (utkarsh)
         Status: New

** Affects: google-guest-agent (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: google-guest-agent (Ubuntu Impish)
     Importance: Undecided
         Status: Won't Fix

** Affects: google-guest-agent (Ubuntu Jammy)
     Importance: Undecided
         Status: New


** Tags: regression-proposed

** Changed in: google-guest-agent (Ubuntu)
     Assignee: (unassigned) => Utkarsh Gupta (utkarsh)

** Tags added: regression-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to google-guest-agent in Ubuntu.
https://bugs.launchpad.net/bugs/1980725

Title:
  bin:google_authorized_keys shipped by this package conflicts with the
  same binary shipped by src:google-compute-engine-oslogin

Status in google-guest-agent package in Ubuntu:
  New
Status in google-guest-agent source package in Focal:
  New
Status in google-guest-agent source package in Impish:
  Won't Fix
Status in google-guest-agent source package in Jammy:
  New

Bug description:
  [Impact]
  ========

  The two packages src:google-compute-engine-oslogin and src:google-
  guest-agent cannot be co-installed together because they ship the same
  binary so dpkg throws the following error out:

  dpkg: error processing archive /tmp/apt-dpkg-install-USEDmn/2-google-guest-agent_20220622.00-0ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/google_authorized_keys', which is also in package google-compute-engine-oslogin 20210907.00-0ubuntu2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  [Test Plan]
  ===========

  $ lxc launch images:ubuntu/kinetic ktemp
  $ lxc shell ktemp
  $ apt update
  $ apt install google-compute-engine-oslogin
  $ 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/system/google-guest-agent.service
  /lib/systemd/system/google-shutdown-scripts.service
  /lib/systemd/system/google-startup-scripts.service
  /usr/bin/google_authorized_keys
  /usr/bin/google_guest_agent
  /usr/bin/google_metadata_script_runner
  /usr/share/doc/google-guest-agent/changelog.Debian.gz
  /usr/share/doc/google-guest-agent/copyright

  With the fix:

  /lib/systemd/system/google-guest-agent.service
  /lib/systemd/system/google-shutdown-scripts.service
  /lib/systemd/system/google-startup-scripts.service
  /usr/bin/google_guest_agent
  /usr/bin/google_metadata_script_runner
  /usr/share/doc/google-guest-agent/changelog.Debian.gz
  /usr/share/doc/google-guest-agent/copyright

  That is, the google_authorized_keys shouldn't be shipped.

  [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. :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1980725/+subscriptions