Package: libelk0t64
Version: 3.99.8-5
Severity: serious
User: debian-qa@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libelk0

libelk0t64 has an undeclared file conflict. This may result in an unpack
error from dpkg.

The files
* /usr/lib/x86_64-linux-gnu/libelk-xlib.so.0
* /usr/lib/x86_64-linux-gnu/libelk-xlib.so.0.0.0
* /usr/lib/x86_64-linux-gnu/libelk-xt.so.0
* /usr/lib/x86_64-linux-gnu/libelk-xt.so.0.0.0
* /usr/lib/x86_64-linux-gnu/libelk.so.0
* /usr/lib/x86_64-linux-gnu/libelk.so.0.0.0
are contained in the packages
* libelk0/3.99.8-4.2+b1 as present in bookworm|bullseye|trixie|unstable
* libelk0t64/3.99.8-5 as present in 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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

affects -1 + libelk0

Bug #1065126 [libelk0t64] libelk0t64 has an undeclared file conflict
Added indication that 1065126 affects libelk0

--
1065126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065126
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Tue, 05 Mar 2024 15:34:10 +0000
with message-id <E1rhWny-004IMl-M2@fasolo.debian.org>
and subject line Bug#1065126: fixed in elk 3.99.8-6
has caused the Debian Bug report #1065126,
regarding libelk0t64 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 owner@bugs.debian.org
immediately.)


--
1065126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065126
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 29 Feb 2024 22:46:18 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-12.0 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,HAS_PACKAGE,SPF_HELO_NONE,SPF_NONE,
T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 25; hammy, 141; neutral, 36; spammy,
0. spammytokens: hammytokens:0.000-+--bookworm, 0.000-+--trixie,
0.000-+--H*F:U*helmut, 0.000-+--H*F:D*subdivi.de,
0.000-+--H*RU:sk:helmut@
Return-path: <helmut@subdivi.de>
Received: from isilmar-4.linta.de ([136.243.71.142]:58964)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
(Exim 4.94.2)
(envelope-from <helmut@subdi