• Bug#1102736: libnet1-doc has an undeclared file conflict on /usr/share/

    From Helmut Grohne@21:1/5 to All on Sat Apr 12 13:50:02 2025
    Package: libnet1-doc
    Version: 1.3+dfsg-1
    Severity: serious
    User: debian-qa@lists.debian.org
    Usertags: fileconflict
    Control: affects -1 + libnet1

    libnet1-doc has an undeclared file conflict. This may result in an
    unpack error from dpkg.

    The file /usr/share/doc/libnet1/CONTRIB is contained in the packages
    * libnet1/1.1.6+dfsg-3.2 as present in bookworm
    * libnet1-doc/1.3+dfsg-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 file.

    Kind regards

    Helmut

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sat Apr 12 13:50:02 2025
    Processing control commands:

    affects -1 + libnet1
    Bug #1102736 [libnet1-doc] libnet1-doc has an undeclared file conflict on /usr/share/doc/libnet1/CONTRIB
    Added indication that 1102736 affects libnet1

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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sat May 3 11:00:01 2025
    This is a multi-part message in MIME format...

    Your message dated Sat, 03 May 2025 08:49:48 +0000
    with message-id <E1uB8ZA-009u97-PH@fasolo.debian.org>
    and subject line Bug#1102736: fixed in libnet 1.3+dfsg-2
    has caused the Debian Bug report #1102736,
    regarding libnet1-doc has an undeclared file conflict on /usr/share/doc/libnet1/CONTRIB
    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.)


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

    Received: (at submit) by bugs.debian.org; 12 Apr 2025 11:38:49 +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=-25.2 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_CONTROL_AFFECTS,BODY_INCLUDES_PACKAGE,DKIM_SIGNED,
    DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HAS_PACKAGE,SPF_HELO_NONE,
    SPF_NONE autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 12; hammy, 103; neutral, 30; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--bookworm,
    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]:33408)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__