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

  • Bug#1101969: node-blueprintjs-core overwrites node-blueprintjs-colors

    From Helmut Grohne@21:1/5 to All on Thu Apr 3 10:10:01 2025
    Package: node-blueprintjs-core
    Version: 4.17.8~git20230417213433.6dab069+ds1-3
    Severity: serious
    User: debian-qa@lists.debian.org
    Usertags: fileconflict
    Control: affects -1 + node-blueprintjs-colors

    Both node-blueprintjs-core from trixie and sid and
    node-blueprintjs-colors version 5.0.0~alpha.0+ds-2 as present in
    bookworm, trixie and sid install the following files:
    - /usr/share/doc/node-blueprintjs-colors/README.md
    - /usr/share/doc/node-blueprintjs-colors/copyright
    - /usr/share/nodejs/@blueprintjs/colors/lib/colors.d.ts
    - /usr/share/nodejs/@blueprintjs/colors/lib/colors.js
    - /usr/share/nodejs/@blueprintjs/colors/lib/index.d.ts
    - /usr/share/nodejs/@blueprintjs/colors/lib/index.js
    - /usr/share/nodejs/@blueprintjs/colors/lib/legacyColors.d.ts
    - /usr/share/nodejs/@blueprintjs/colors/lib/legacyColors.js
    - /usr/share/nodejs/@blueprintjs/colors/package.json
    - /usr/share/nodejs/@blueprintjs/colors/src/_colors.scss
    - /usr/share/nodejs/@blueprintjs/colors/src/colors.ts
    - /usr/share/nodejs/@blueprintjs/colors/src/index.ts
    - /usr/share/nodejs/@blueprintjs/colors/src/legacyColors.ts
    - /usr/share/nodejs/@blueprintjs/colors/src/tsconfig.json

    Attempting to coinstall these packages results in an unpack error from
    dpkg. I am reporting this bug with node-blueprintjs-core, because node-blueprintjs-colors was the proper owner in bookworm.

    It's not clear to me what the desired state here is. A reasonable interpretation could be that node-blueprintjs-core accidentally vendored node-blueprintjs-colors and should really depend on it and another is
    that node-blueprintjs-core bundles node-blueprintjs-colors such that
    Debian would have fewer binary packages. Can you figure out how this is
    meant and reassign (and change affects) as appropriate?

    Helmut

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Thu Apr 3 10:10:01 2025
    Processing control commands:

    affects -1 + node-blueprintjs-colors
    Bug #1101969 [node-blueprintjs-core] node-blueprintjs-core overwrites node-blueprintjs-colors
    Added indication that 1101969 affects node-blueprintjs-colors

    --
    1101969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101969
    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 Sun Apr 6 18:30:01 2025
    Processing control commands:

    reassign -1 node-blueprintjs-colors
    Bug #1101969 [node-blueprintjs-core] node-blueprintjs-core overwrites node-blueprintjs-colors
    Bug reassigned from package 'node-blueprintjs-core' to 'node-blueprintjs-colors'.
    No longer marked as found in versions node-blueprintjs/4.17.8~git20230417213433.6dab069+ds1-3.
    Ignoring request to alter fixed versions of bug #1101969 to the same values previously set
    affects -1 node-blueprintjs-core
    Bug #1101969 [node-blueprintjs-colors] node-blueprintjs-core overwrites node-blueprintjs-colors
    Added indication that 1101969 affects node-blueprintjs-core

    --
    1101969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101969
    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 Fri Apr 11 16:00:01 2025
    This is a multi-part message in MIME format...

    Your message dated Fri, 11 Apr 2025 13:50:07 +0000
    with message-id <E1u3Elj-003yxb-LT@fasolo.debian.org>
    and subject line Bug#1102398: Removed package(s) from unstable
    has caused the Debian Bug report #1101969,
    regarding node-blueprintjs-core overwrites node-blueprintjs-colors
    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.)


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

    Received: (at submit) by bugs.debian.org; 3 Apr 2025 08:03:27 +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, 37; hammy, 143; neutral, 39; 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]:60534)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__A