• Bug#1062352: libgsmme1t64 has an undeclared file conflict

    From Helmut Grohne@21:1/5 to All on Thu Feb 1 07:40:02 2024
    Package: libgsmme1t64
    Version: 1.10+20120414.gita5e5ae9a-2.1~exp1
    Severity: serious
    User: debian-qa@lists.debian.org
    Usertags: fileconflict
    Control: affects -1 + libgsmme1v5
    X-Debbugs-Cc: Graham Inggs <ginggs@debian.org>, vorlon@debian.org

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

    The files
    * /usr/lib/x86_64-linux-gnu/libgsmext.so.1
    * /usr/lib/x86_64-linux-gnu/libgsmext.so.1.0.4
    * /usr/lib/x86_64-linux-gnu/libgsmme.so.1
    * /usr/lib/x86_64-linux-gnu/libgsmme.so.1.0.4
    are contained in the packages
    * libgsmme1t64/1.10+20120414.gita5e5ae9a-2.1~exp1 as present in experimental
    * libgsmme1v5
    * 1.10+20120414.gita5e5ae9a-2+b1 as present in bookworm|trixie|unstable
    * 1.10+20120414.gita5e5ae9a-2~bpo11+1 as present in bullseye-backports

    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)
  • From Debian Bug Tracking System@21:1/5 to All on Tue Mar 5 15:10:01 2024
    This is a multi-part message in MIME format...

    Your message dated Tue, 5 Mar 2024 15:06:16 +0100
    with message-id <9683feb7-5761-62f2-9ee2-0bbe59add153@debian.org>
    and subject line Re: libgsmme1t64 has an undeclared file conflict
    has caused the Debian Bug report #1062352,
    regarding libgsmme1t64 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.)


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

    Received: (at submit) by bugs.debian.org; 1 Feb 2024 06:32:07 +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, 18; hammy, 150; neutral, 55; spammy,
    0. spammytokens: hammytokens:0.000-+--bookworm, 0.000-+--X-Debbugs-Cc,
    0.000-+--XDebbugsCc, 0.000-+--trixie, 0.000-+--exp1
    Return-path: <helmut@subdivi.de>
    Received: from isilmar-4.linta.de ([136.243.71.142]:39572)
    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@subdivi.de>)
    id 1rVQcJ-