You are not logged in.

#1 2015-02-15 22:28:09

KRTac
Member
From: Croatia
Registered: 2008-07-01
Posts: 99

File that doesn't belong to any installed package causes conflicts

I get a file conflict error when upgrading:

error: failed to commit transaction (conflicting files)
nodejs: /usr/lib/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/ctype/.npmignore exists in filesystem
Errors occurred, no packages were upgraded.

Now, as far as I can tell, this module is required in npm, but it doesn't bellong to any package. The nodejs package includes these files with it so there's a conflict. The bigger problem here is that I can't figure out how it got to this. Maybe I accidentally updated npm?

Any advice on how to procede?

Offline

#2 2015-02-15 22:49:46

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,731
Website

Re: File that doesn't belong to any installed package causes conflicts

Backup the affected files and then move them away to allow the package to install.  If no problems, delete the backups.

Offline

Board footer

Powered by FluxBB