Arch Linux

atordo

Member

Registered: 2007-04-21

Posts: 147

[SOLVED] Errors upgrading namcap 3.2.4-1

I got the following errors trying to upgrade namcap:

error: failed to commit transaction (conflicting files)
namcap: /usr/lib/python3.2/site-packages/Namcap/__pycache__/__init__.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/__pycache__/depends.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/__pycache__/package.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/__pycache__/ruleclass.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/__pycache__/tags.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/__pycache__/util.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/__init__.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/anyelf.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/arrays.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/badbackups.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/carch.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/elffiles.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/emptydir.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/extravars.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/fhs.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/filenames.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/fileownership.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/glibfiles.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/gnomemime.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/hardlinks.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/hicoloricons.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/infodirectory.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/invalidstartdir.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/javafiles.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/kdeprograms.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/libtool.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/licensepkg.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/lotsofdocs.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/mimefiles.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/missingbackups.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/missingvars.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/perllocal.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/permissions.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/pkginfo.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/pkgnameindesc.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/rpath.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/scrollkeeper.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/sfurl.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/shebangdepends.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/sodepends.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/splitpkgbuild.cpython-32.pyc exists in filesystem
namcap: /usr/lib/python3.2/site-packages/Namcap/rules/__pycache__/symlink.cpython-32.pyc exists in filesystem
Errors occurred, no packages were upgraded.

Those files don't belong to any package (according to pacman -Qo). Is it safe to force the update?

Last edited by atordo (2012-05-14 16:58:00)

loafer

Member

From: the pub

Registered: 2009-04-14

Posts: 1,772

Re: [SOLVED] Errors upgrading namcap 3.2.4-1

I would be inclined to rename them rather than use force.  Then delete them if all goes well.

---

All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: [SOLVED] Errors upgrading namcap 3.2.4-1

You're fine to force the upgrade for namcap alone (do NOT use -Syu --force). In the future, don't run namcap as root.

Last edited by falconindy (2012-05-13 20:27:51)

---

blog | ±github

atordo

Member

Registered: 2007-04-21

Posts: 147

Re: [SOLVED] Errors upgrading namcap 3.2.4-1

Thanks both for the replies. Forcing the update worked, and as falconindy suggests, I'm afraid those files were generated by using namcap as root. So my bad for being a lazy ass and using root to build some custom packages, instead of just for installing.