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

Package: liblcms2-dev
Version: 2.9-3
Severity: important

Dear Maintainer,

After running 'apt-get dist-upgrade' today, I now have the following
behavior:


# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer
required:
  libbison-dev libskarnet2.7 python-pyasn1
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  liblcms2-dev:i386
The following packages will be upgraded:
  liblcms2-dev:i386
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
177 not fully installed or removed.
Need to get 0 B/9,103 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n]
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 456287 files and directories currently installed.)
Preparing to unpack .../liblcms2-dev_2.9-3+b1_i386.deb ...
Unpacking liblcms2-dev:i386 (2.9-3+b1) over (2.9-3) ...
dpkg: error processing archive
/var/cache/apt/archives/liblcms2-dev_2.9-3+b1_i386.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/liblcms2-dev/src.zip',
which is different from other instances of package liblcms2-dev:i386
Errors were encountered while processing:
 /var/cache/apt/archives/liblcms2-dev_2.9-3+b1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


Removing liblcms2-dev lets the dist-upgrade pending packages finish
installing, but attempting to reinstall afterwards produces the same
error.

For comparison, liblcms2-dev:amd64 upgraded (to the matching version)
just fine.

I'm not sure what "other instances of liblcms2-dev:i386" means, since as
far as I can tell, there is by definition only one instance of the i386
variant of that package with that version on the current machine.

My best guess is that this is a confusing way of saying that the file is
different in liblcms2-dev:amd64, but that doesn't seem entirely clear.
(If that *is* correct, a better way of conveying that would be to say
"opther instances of package liblcms2-dev", with no arch suffix. That's
probably a detail for dpkg, however.)

If there's anything I can do to help track this down, please let me
know. I'm comparatively swamped with work at this point, but I may be
able to spare some time in the mornings.


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'stable'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages liblcms2-dev:i386 depends on:
iu  liblcms2-2  2.9-3+b1

liblcms2-dev:i386 recommends no packages.

liblcms2-dev:i386 suggests no packages.

- -- no debconf information

Reply via email to