Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#59679 - Can't upgrade npm due to conflicting files

Attached to Project: Community Packages
Opened by Jared Meit (jmeit) - Thursday, 16 August 2018, 16:04 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 16 August 2018, 16:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Running pacman to update my system is being blocked due to "conflicting files" for npm package. Conflicting files are node_modules and a list is attached. When the offending folder is renamed to avoid conflict, another folder in node_modules/ becomes the offending folder.

Additional info:
* package version: 6.4.0-1

Steps to reproduce:
Run `pacman -Syu` with a package update for npm 6.4.0-1.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 16 August 2018, 16:11 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See man#.22Failed_to_commit_transaction_.28c onflicting_files.29.22_error