Bug#1062611: libiv-unidraw2t64 has an undeclared file conflict
El vie, 2 feb 2024 a las 6:57, Helmut Grohne () escribió: > > Package: libiv-unidraw2t64 > Version: 2.0.11d.a1-1.1~exp1 > Severity: serious > User: debian...@lists.debian.org > Usertags: fileconflict > Control: affects -1 + libiv2 libiv2t64 > X-Debbugs-Cc: Graham Inggs , vor...@debian.org > > libiv-unidraw2t64 has an undeclared file conflict. This may result in an > unpack error from dpkg. > > The files > * /usr/lib/x86_64-linux-gnu/libIV.so.2 > * /usr/lib/x86_64-linux-gnu/libIV.so.2.0.0 > are contained in the packages > * libiv-unidraw2t64/2.0.11d.a1-1.1~exp1 as present in experimental > * libiv2 >* 2.0.11d.a1-1+b4 as present in bookworm >* 2.0.11d.a1-1+b5 as present in trixie|unstable >* 2.0.4a1-2 as present in bullseye > * libiv2t64/2.0.11d.a1-1.1~exp1 as present in experimental Hi, Helmut. I wonder if this is still an issue. Some uploads happened in the meantime and seems that those files are currently shipped by a different package $ dpkg -S libIV.so.2 libiv2t64:amd64: /usr/lib/x86_64-linux-gnu/libIV.so.2.0.0 libiv2t64:amd64: /usr/lib/x86_64-linux-gnu/libIV.so.2 which apparently handles things well Package: libiv2t64 Replaces: libiv2 Provides: libiv2 (= 2.0.11d.a1-1.1) Breaks: libiv2 (<< 2.0.11d.a1-1.1)
Bug#1062611: libiv-unidraw2t64 has an undeclared file conflict
Package: libiv-unidraw2t64 Version: 2.0.11d.a1-1.1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libiv2 libiv2t64 X-Debbugs-Cc: Graham Inggs , vor...@debian.org libiv-unidraw2t64 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linux-gnu/libIV.so.2 * /usr/lib/x86_64-linux-gnu/libIV.so.2.0.0 are contained in the packages * libiv-unidraw2t64/2.0.11d.a1-1.1~exp1 as present in experimental * libiv2 * 2.0.11d.a1-1+b4 as present in bookworm * 2.0.11d.a1-1+b5 as present in trixie|unstable * 2.0.4a1-2 as present in bullseye * libiv2t64/2.0.11d.a1-1.1~exp1 as present in experimental 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 hel...@subdivi.de for assistance.