Your message dated Mon, 4 Mar 2024 08:02:23 +0100
with message-id <[email protected]>
and subject line Re: Bug#1062611: libiv-unidraw2t64 has an undeclared file
conflict
has caused the Debian Bug report #1062611,
regarding libiv-unidraw2t64 has an undeclared file conflict
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 [email protected]
immediately.)
--
1062611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062611
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libiv-unidraw2t64
Version: 2.0.11d.a1-1.1~exp1
Severity: serious
User: [email protected]
Usertags: fileconflict
Control: affects -1 + libiv2 libiv2t64
X-Debbugs-Cc: Graham Inggs <[email protected]>, [email protected]
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
[email protected] for assistance.
--- End Message ---
--- Begin Message ---
Version: 2.0.11d.a1-1.1
On Mon, Mar 04, 2024 at 12:39:21AM +0100, Agustin Martin wrote:
> 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
Thank you for reaching out.
> $ 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)
I double checked with what dumat thinks about this and it does not see
any issue anymore and thnks libiv2t64 has version 2.0.11d.a1-1.1. I
guess that Lukas fixed the bug in his upload without adding it to the
changelog.
Helmut
--- End Message ---
