Your message dated Fri, 11 Apr 2025 13:50:07 +0000
with message-id <e1u3elj-003yxb...@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 ow...@bugs.debian.org
immediately.)
--
1101969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-blueprintjs-core
Version: 4.17.8~git20230417213433.6dab069+ds1-3
Severity: serious
User: debian...@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
--- End Message ---
--- Begin Message ---
Version: 5.0.0~alpha.0+ds-2+rm
Dear submitter,
as the package node-blueprintjs-colors has just been removed from the Debian
archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1102398
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
