Comment 0 for bug 2050956

[Impact]

`google-guest-agent` is a package provided by Google for installation within guests that run on Google Compute Engine (GCE). It is part of a collection of tools and daemons that ensure that Ubuntu images published to GCE run properly on the platform.

There is a diff between Google's packaged debian distro [0] `debian/control` file and what's currently in the archive [1]. This was originally harmless but now has caused a customer issue where they were unable to login as they'd upgraded the `google-guest-agent` package but _not_ the `google-compute-engine-oslogin` package.

The `google-guest-agent` should have a dependency on `google-compute-engine-oslogin` the same as it does in the Google managed control file. There is also a missing `Conflicts` field and the `Vcs-` fields are out of date.

[Test Case]

When the new version of this package is uploaded to -proposed, the following will happen:

 * an image based on -proposed will be built for GCE and published
 * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation.
 * Each test image will be launched, and we will validate:
 ** the package version(s)
 ** that the correct ssh keys have been imported
 ** that the google specific services are running successfully

If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done.

[0]: https://github.com/GoogleCloudPlatform/guest-agent/tree/main/packaging/debian
[1]: https://git.launchpad.net/~cloud-images/cloud-images/+git/google-guest-agent/tree/debian/control?h=ubuntu/master