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
