Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

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!
Tasklist

FS#46851 - [npm] Filesystem Conflict npm 3.3.9-1

Attached to Project: Community Packages
Opened by Arsalan (afzalarsalan) - Saturday, 24 October 2015, 02:49 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 24 October 2015, 03:12 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Recently went to upgrade my system and noticed that there seems to be a random file system conflict on the install of npm 3.3.9

npm: /usr/lib/node_modules/npm/node_modules/request/node_modules/qs/README.md exists in filesystem

Unclear whether its okay to just force this or whether this is a packaging error

This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 24 October 2015, 03:12 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Saturday, 24 October 2015, 03:02 GMT
Follow the instructions here: https://wiki.archlinux.org/index.php/Pacman#.22Failed_to_commit_transaction_.28conflicting_files.29.22_error
Comment by Arsalan (afzalarsalan) - Saturday, 24 October 2015, 03:07 GMT
Yup, this did the job. Looking back at it, this probably occurred due to updating npm with itself rather than the package manager.

Loading...