Bug 29833

Summary: NPM unable to update
Product: Mageia Reporter: Marc Krämer <mageia>
Component: RPM PackagesAssignee: Joseph Wang <joequant>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal    
Version: 8   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: nodejs-14.18.1-1.1.mga8.src.rpm CVE:
Status comment:

Description Marc Krämer 2021-12-31 11:12:59 CET
urpmi --auto-select 
To satisfy dependencies, the following package is going to be installed:
  Package                        Version      Release       Arch    
(medium "Core Updates")
  npm                            6.14.15      1.14.18.1.1.> x86_64  
27B of additional disk space will be used.
3.5MB of packages will be retrieved.
Proceed with the installation of one package? (Y/n) 


    https://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/8/x86_64/media/core/updates/npm-6.14.15-1.14.18.1.1.1.mga8.x86_64.rpm
installing npm-6.14.15-1.14.18.1.1.1.mga8.x86_64.rpm from /var/cache/urpmi/rpms
Preparing...                     #############################################
      1/1: npm                   #############################################
error: unpacking of archive failed on file /usr/lib/node_modules/npm/docs: cpio: File from package already exists as a directory in system
ERROR: 'unpack' failed for npm-1:6.14.15-1.14.18.1.1.1.mga8.x86_64
error: npm-1:6.14.15-1.14.18.1.1.1.mga8.x86_64: install failed
error: npm-1:6.14.15-1.14.17.6.1.mga8.x86_64: erase skipped


ll /usr/lib/node_modules/npm/docs
insgesamt 0
drwxr-xr-x 5 root root 24 Dez 18 15:47 content/
drwxr-xr-x 5 root root 24 Dez 18 15:47 output/


does the package conflict with updates done via npm update etc?
Comment 1 Lewis Smith 2021-12-31 20:12:03 CET
Was the command you did:
 # urpmi --auto-select npm
?

The only source I can find for /usr/lib/node_modules/npm/ is 'npm' itself (a huge number (>4500) of times). If you already have these, it suggests that you have previously installed npm.
Have you? Did you remove it at some point? If you did, that would suggest that the removal omitted this lot.

Clearly to allow a 'new' installation, you could remove entirely the tree
/usr/lib/node_modules/npm/ or even perhaps /usr/lib/node_modules/
but it would be preferable to first find out why your conflict arose.

CC: (none) => lewyssmith

Comment 2 Marc Krämer 2022-01-01 11:14:03 CET
I did urpmi --auto-select, since it is already installed (should have written update).
There are files in conflict (in my filesystem there is a folder) and the rpm contains a file (I assume a symlink).

I assume I have issued
npm upgrade
at some point. But anyway, this command is available and is used to update npm packages, and it also updates npm itself. Our rpm package should be compatible with these updates.

Summary: NPM unable to install => NPM unable to update

Comment 3 Lewis Smith 2022-01-03 20:19:27 CET
> I assume I have issued
> npm upgrade
> at some point. But anyway, this command is available and is used to update
> npm packages, and it also updates npm itself. Our rpm package should be
> compatible with these updates.
This is a very dicey situation, updating npm independently and then via urpmi. 

Assigning this to joequant for nodejs (which contains npm).

Assignee: bugsquad => joequant
CC: lewyssmith => (none)

Comment 4 Marc Krämer 2022-01-05 00:48:11 CET
removed the files and did the update, let's see if this comes again. closing for now.

Resolution: (none) => INVALID
Status: NEW => RESOLVED