Bug#1061939: libtag-c-dev and libtag-dev have an undeclared file conflict
Package: libtag-c-dev,libtag-dev
Version: 2.0-1~exp2
Severity: serious
User: debian-qa@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libtag1-dev libtagc0-dev
libtag-c-dev and libtag-dev have an undeclared file conflict. This may
result in an unpack error from dpkg.
The files
* /usr/lib/x86_64-linux-gnu/libtag_c.so
* /usr/lib/x86_64-linux-gnu/pkgconfig/taglib_c.pc
are contained in the packages
* libtag-c-dev/2.0-1~exp2 as present in experimental
* libtagc0-dev
* 1.11.1+dfsg.1-3 as present in bullseye
* 1.13-2 as present in bookworm
* 1.13.1-1 as present in trixie|unstable
The files
* /usr/bin/taglib-config
* /usr/lib/x86_64-linux-gnu/libtag.so
* /usr/lib/x86_64-linux-gnu/pkgconfig/taglib.pc
are contained in the packages
* libtag-dev/2.0-1~exp2 as present in experimental
* libtag1-dev
* 1.11.1+dfsg.1-3 as present in bullseye
* 1.13-2 as present in bookworm
* 1.13.1-1 as present in trixie|unstable
These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.
Kind regards
The Debian Usr Merge Analysis Tool
This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
helmut@subdivi.de for assistance.
Reply to: