You are not logged in.
I'm unable to upgrade libvirt-python and virt-manager as of this morning:
[root@foobar ~]# pacman -Su
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Packages (2): libvirt-python-1.2.0-2 virt-manager-0.10.0-4
Total Installed Size: 9.28 MiB
Net Upgrade Size: 0.79 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring [######################] 100%
(2/2) checking package integrity [######################] 100%
(2/2) loading package files [######################] 100%
(2/2) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
libvirt-python: /usr/lib/python2.7/site-packages/libvirt.pyc exists in filesystem
Errors occurred, no packages were upgraded.
[root@iwr239124 ~]# pacman -Qo /usr/lib/python2.7/site-packages/libvirt.pyc
error: No package owns /usr/lib/python2.7/site-packages/libvirt.pycSo that file appears to be un-owned... would like to know how it got there (generated post-install?) but is it okay to just --force in this case?
Last edited by kmshanah (2013-12-05 23:02:34)
Offline
.pyc file are bytecode compiled python, they are often generated on first run and therefor untracked by pacman. They are trying to get these into the packages so that they are tracked and to speed up load times for those not run as root and .pyc files can't be generated.
I would suggest just removing the file then installing like normal.
Last edited by Scimmia (2013-12-05 23:01:28)
Offline
Great, thanks. Worked fine after just removing that one file.
Offline