Mageia 7 has npm-6.14.10-184.108.40.206.10.mga7 from nodejs-10.23.1-10.mga7.src.rpm
Mageia 8 has npm-6.14.8-220.127.116.11.3.mga8 from nodejs-14.15.1-3.mga8.src.rpm
Both have Epoch 1.
This is blocking upgrades from Mageia 7 to 8 (cascade failure).
Raising the priority as we have a user whose system is broken until upgrading
can be finished.
Adding sysadmins to cc list.
Shouldn't the mga8 in the release override the lower number?
the mga8 bit has nothing to do with this.
its npm-6.14.10 > npm-6.14.8
looks like broken package versioning, or if the npm has actually been rolled down, it should have gotten an epoch
(In reply to Thomas Backlund from comment #3)
> the mga8 bit has nothing to do with this.
> its npm-6.14.10 > npm-6.14.8
> looks like broken package versioning, or if the npm has actually been rolled
> down, it should have gotten an epoch
epoch *bump* that is.
and mga7 < mga8 is only in effect if EVR is exactly the same on both packages
i will update nodejs on mga8, i will see if this is better for the npm version.
Btw mga7 update will have npm version 6.14.11
and if still version issues we will add an epoch
we won't need an epoch as new mageia 8 nodejs will have 6.14.11 too.
I think this bug should be considered fixed because Bug 28445 is?
Or are we waiting for some more?
I can confirm that the bug has been fixed
(In reply to Morgan Leijström from comment #9)
> I think this bug should be considered fixed because Bug 28445 is?
> Or are we waiting for some more?
(In reply to Michael Slíva from comment #10)
> I can confirm that the bug has been fixed
In Errata noting marked as fixed by mga8 update