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:

  Preparing to unpack .../python3-gdbm_3.10.0~b1-3_amd64.deb ...
  Unpacking python3-gdbm:amd64 (3.10.0~b1-3) ...
  dpkg: error processing archive /var/cache/apt/archives/python3-gdbm_3.10.0~b1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so', which is also in package libpython3.10-stdlib:amd64 3.10.0-5
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-gdbm_3.10.0~b1-3_amd64.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/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so

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.

Please note: This is a conflict between libpython3.10-stdlib/sid and
python3-gdbm/experimental.


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

Hi,

You reported a conflict between a package in unstable
(libpython3-stdlib) and a package in experimental
(python3-gdbm/3.10.0~b1-3).
Surely the bug should be reported against the package in experimental,
if at all, shouldn’t it?

Anyway, at least right now, there is no conflict between the packages
in unstable.

Cheers,