[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1004071: marked as done (google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner)

Your message dated Thu, 10 Feb 2022 09:03:57 +0000
with message-id <E1nI5Mr-000IVt-4Z@fasolo.debian.org>
and subject line Bug#1004071: fixed in google-guest-agent 20211116.00-3
has caused the Debian Bug report #1004071,
regarding google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1004071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004071
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: google-guest-agent,python3-google-compute-engine
Severity: serious
User: treinen@debian.org
Usertags: edos-file-overwrite
Control: found -1 20211116.00-1
Control: found -1 20190916-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package python3-google-compute-engine.
  Preparing to unpack .../5-python3-google-compute-engine_20190916-1_all.deb ...
  Unpacking python3-google-compute-engine (20190916-1) ...
  dpkg: error processing archive /tmp/apt-dpkg-install-8A9en2/5-python3-google-compute-engine_20190916-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/google_metadata_script_runner', which is also in package google-guest-agent 20211116.00-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-8A9en2/5-python3-google-compute-engine_20190916-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/google_metadata_script_runner

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html

Attachment: google-guest-agent=20211116.00-1_python3-google-compute-engine=20190916-1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message --- 
Source: google-guest-agent
Source-Version: 20211116.00-3
Done: Dominik George <natureshadow@debian.org>

We believe that the bug you reported is fixed in the latest version of
google-guest-agent, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1004071@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominik George <natureshadow@debian.org> (supplier of updated google-guest-agent package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 10 Feb 2022 09:44:05 +0100
Source: google-guest-agent
Architecture: source
Version: 20211116.00-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud Team <debian-cloud@lists.debian.org>
Changed-By: Dominik George <natureshadow@debian.org>
Closes: 1004071
Changes:
 google-guest-agent (20211116.00-3) unstable; urgency=medium
 .
   * Replace+Conflict+Provide python3-google-compute-engine (Closes: #1004071)
Checksums-Sha1:
 3476ac52d5419c20491f568881807f90dbcf0208 1903 google-guest-agent_20211116.00-3.dsc
 de64ae74cdaa5634fea881a263e71f5e250bb548 2760 google-guest-agent_20211116.00-3.debian.tar.xz
 f46bc751dd052f6fe0be9ba7b8cc207aa3347c94 8374 google-guest-agent_20211116.00-3_amd64.buildinfo
Checksums-Sha256:
 84a01d094527b65e883beb756234e687d82a15491d05885b2175fccc158bd702 1903 google-guest-agent_20211116.00-3.dsc
 2c8e1282e77f5239c94bd88291d4ff30584b4f77081893e9d29fbe1461fab3e0 2760 google-guest-agent_20211116.00-3.debian.tar.xz
 e604d541ec1ca609de252ff6194c7def428b5e1863b50b6796f954156a00521d 8374 google-guest-agent_20211116.00-3_amd64.buildinfo
Files:
 72c50befe764679d4192933ac67407b4 1903 golang optional google-guest-agent_20211116.00-3.dsc
 b11a47a9ae59303ab3bc7d2442a29494 2760 golang optional google-guest-agent_20211116.00-3.debian.tar.xz
 14604c9583437989ad95fe0efbf9d6b7 8374 golang optional google-guest-agent_20211116.00-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iKcEARYKAE8WIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCYgTRXjEaaHR0cHM6Ly93
d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjAAoJEArlVOVG
DhvdkfMBAPzgAMv0pLsjG1tXWufuKv27hE+l/eJrphrLznpD9FqrAP4z19JAaMpo
p7HpMdnyOPLQW4uYwreLmyzUhsQx3p+NBw==
=pQV1
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: