Bug 28481

Summary:	npm has higher release on Mageia 7 than on Mageia 8 causing upgrade problems.
Product:	Mageia	Reporter:	Dave Hodgins <davidwhodgins>
Component:	RPM Packages	Assignee:	Joseph Wang <joequant>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	High	CC:	doktor5000, fri, mageia, michael, ouaurelien, sysadmin-bugs
Version:	8	Keywords:	IN_ERRATA8
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	nodejs-14.15.1-3.mga8	CVE:
Status comment:
Bug Depends on:	28445
Bug Blocks:	28393

Description Dave Hodgins 2021-02-28 01:03:08 CET

Mageia 7 has npm-6.14.10-1.10.23.1.10.mga7 from nodejs-10.23.1-10.mga7.src.rpm
Mageia 8 has npm-6.14.8-1.14.15.1.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).

Comment 1 Dave Hodgins 2021-02-28 01:27:41 CET

Raising the priority as we have a user whose system is broken until upgrading
can be finished.
https://forums.mageia.org/en/viewtopic.php?f=8&t=13945&p=81682#p81682

Priority: Normal => High

Florian Hubold 2021-02-28 01:33:55 CET

CC: (none) => doktor5000

Comment 2 Dave Hodgins 2021-02-28 01:54:22 CET

Adding sysadmins to cc list.

Shouldn't the mga8 in the release override the lower number?

CC: (none) => sysadmin-bugs

Comment 3 Thomas Backlund 2021-02-28 02:24:42 CET

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

Comment 4 Thomas Backlund 2021-02-28 02:27:58 CET

(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

Michael Slíva 2021-02-28 04:31:13 CET

CC: (none) => sliva

Manuel Hiebel 2021-02-28 12:25:16 CET

Blocks: (none) => 28393

Morgan Leijström 2021-02-28 13:28:45 CET

CC: (none) => fri

Comment 5 Nicolas Lécureuil 2021-02-28 13:38:19 CET

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

CC: (none) => mageia

Comment 6 Nicolas Lécureuil 2021-02-28 13:41:21 CET

and if still version issues we will add an epoch

Comment 7 Nicolas Lécureuil 2021-02-28 16:52:23 CET

we won't need an epoch as new mageia 8 nodejs will have 6.14.11 too.

Manuel Hiebel 2021-02-28 19:34:26 CET

Depends on: (none) => 28445

Comment 8 Morgan Leijström 2021-03-01 00:29:59 CET

https://wiki.mageia.org/en/Mageia_8_Errata#Various_upgrade_issues

Keywords: (none) => IN_ERRATA8

Comment 9 Morgan Leijström 2021-03-01 15:57:54 CET

I think this bug should be considered fixed because Bug 28445 is?
Or are we waiting for some more?

Comment 10 Michael Slíva 2021-03-01 15:58:48 CET

I can confirm that the bug has been fixed

Comment 11 Aurelien Oudelet 2021-03-01 16:02:24 CET

(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

Closing

Resolution: (none) => FIXED
Status: NEW => RESOLVED
CC: (none) => ouaurelien

Comment 12 Morgan Leijström 2021-03-01 16:04:18 CET

Thanks
In Errata noting marked as fixed by mga8 update