Control: reassign -1 node-rollup-plugin-terser
Le 20/03/2026 à 08:06, Paul Gevers a écrit :
Hi Yadd,
On 3/20/26 07:23, Yadd wrote:
Some packages have one of:
Breaks: node-rollup-plugin-terser (<< 7.0.2+~5.0.1-3~)
Breaks: node-rollup-plugin-terser (<< 7.0.2-6~)
And dpkg has no problem to compare those versions:
$ rmadison node-rollup-plugin-terser
node-rollup-plugin-terser | 7.0.2-5 | oldoldstable |
source, all
node-rollup-plugin-terser | 7.0.2+~5.0.1-8 | oldstable |
source, all
node-rollup-plugin-terser | 7.0.2+~5.0.1-8 | stable |
source, all
node-rollup-plugin-terser | 7.0.2+~5.0.1-9 | testing |
source, all
node-rollup-plugin-terser | 7.0.2+~cs8.6.4-1 | buildd-unstable |
source, all
node-rollup-plugin-terser | 7.0.2+~cs8.6.4-1 | unstable |
source, all
$ dpkg --compare-versions 7.0.2+~cs8.6.4-1 gt 7.0.2+~5.0.1-9 &&
echo OK
OK
$ dpkg --compare-versions 7.0.2+~cs8.6.4-1 gt 7.0.2-6 && echo OK
OK
Did you see
https://piuparts.debian.org/sid/fail/node-rollup-plugin-
terser_7.0.2+~cs8.6.4-1.log
autopkgtest just uses apt to install packages, so I don't believe this
is a bug in autopkgtest.
Paul
I found the issue (I can fix it in node-rollup-plugin-terser for now):
there is an automatic "Provides" because node-rollup-plugin-terser
provide rollup-plugin-terser and @rollup/plugin-terser.
We never had this issue before because in all replacements of old
rollup-plugin-foo by @rollup/plugin-foo (with temporary double package)
we had always @rollup/plugin-foo version > rollup-plugin-foo version
But here for the first time, @rollup/plugin-terser version is lower.
So there are 2 issues:
- dh-sequence-nodejs shouldn't double-provide
- resolver should take the higher version
Thanks for your time!
