1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1102701: libjs-markdown-it and node-markdown-it have an undeclared

    From Helmut Grohne@21:1/5 to All on Sat Apr 12 11:40:02 2025
    Package: libjs-markdown-it,node-markdown-it
    Severity: serious
    User: [email protected]
    Usertags: fileconflict

    The file /usr/share/javascript/markdown-it is contained in the packages
    * libjs-markdown-it/8.4.2-6 as present in bookworm|unstable
    * node-markdown-it/22.2.3+dfsg+~12.2.3-2 as present in bookworm|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.

    Please figure out which of these packages should properly own the
    affected file and reassign the bug as appropriate. When doing so, please
    add the other package to the set of affected packages using "Control:
    affects -1 + <packagename>" to avoid the filing of duplicates.

    The other package should stop installing the file. In case the file is
    being moved between packages, Breaks and Replaces should be declared. In
    this case, please refer to policy section 7.6 for details. Another
    useful resource is https://wiki.debian.org/PackageTransition.

    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 Wed Apr 16 13:30:01 2025
    This is a multi-part message in MIME format...

    Your message dated Wed, 16 Apr 2025 11:19:23 +0000
    with message-id <[email protected]>
    and subject line Bug#1095465: Removed package(s) from unstable
    has caused the Debian Bug report #1102701,
    regarding libjs-markdown-it and node-markdown-it have an undeclared file conflict on /usr/share/javascript/markdown-it
    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.)


    --
    1102701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102701
    Debian Bug Tracking System
    Contact [email protected] with problems

    Received: (at submit) by bugs.debian.org; 12 Apr 2025 09:34: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=-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, 13; hammy, 134; neutral, 41; 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: <[email protected]>
    Received: from isilmar-4.linta.de ([136.243.71.142]:39164)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__