You are not logged in.
Today I ran into a problem when upgrading my system with
pacman -Syu
The error messages are basically the same reported by someone in https://bbs.archlinux.org/viewtopic.php?id=210539.
Instead of forcing the upgrade, I did two things:
1. Uninstalled virt-install and virt-manager (pacman -R virt-install virt-manager)
2. Renamed /usr/share/virt-manager to /usr/share/virt-manager.bak
Then I was able to run pacman -Syu without any issues. I think this is a better solution than forcing the upgrade because apparently /usr/share/virt-manager had a new file structure.
Old structure:
$ tree -L 1 virt-manager.bak
virt-manager.bak
└── virtinst
New structure:
$ tree -L 1 virt-manager
virt-manager
├── icons
├── ui
├── virtinst
└── virtManager
Any thoughts? I upgrade my system every few days, and I did my last upgrade on 8/28. I checked the ArchLinux page but there was no information about this potential issue.
Offline
Your error was about .pyc files?
Offline
Yes. Files like this:
$ find /usr/share/virt-manager.bak/virtinst/|head
/usr/share/virt-manager.bak/virtinst/
/usr/share/virt-manager.bak/virtinst/__pycache__
/usr/share/virt-manager.bak/virtinst/__pycache__/domcapabilities.cpython-313.pyc
/usr/share/virt-manager.bak/virtinst/__pycache__/buildconfig.cpython-313.pyc
/usr/share/virt-manager.bak/virtinst/__pycache__/xmlapi.cpython-313.pyc
/usr/share/virt-manager.bak/virtinst/__pycache__/generatename.cpython-313.pyc
/usr/share/virt-manager.bak/virtinst/__pycache__/snapshot.cpython-313.pyc
/usr/share/virt-manager.bak/virtinst/__pycache__/xmlbuilder.cpython-313.pyc
/usr/share/virt-manager.bak/virtinst/__pycache__/storage.cpython-313.pyc
/usr/share/virt-manager.bak/virtinst/__pycache__/virtinstall.cpython-313.pyc
Offline
Same error here.
I cannot confirm the structure change, though. My current structure of /usr/share/virt-manager, before removing the virt-install and virt-manager packages as you suggested, looks exactly like your "new structure". Maybe that's because you renamed the folder to .bak after uninstalling the packages.
I'm no expert but I believe that the __pycache__ folders have been packaged by mistake. They're not there in my previous packages.
My fix was to run this (obviously run as root) before pacman -Syu
find /usr/share/virt-manager/ -type d | grep __pycache__ | xargs rm -rf
EDITED to add: I read the post from 2016 linked in the OP and maybe the .pyc files were not packaged by mistake. Still they were not there in 5.0.1
Last edited by andreworg (2025-09-04 21:13:45)
Offline
I'm no expert but I believe that the __pycache__ folders have been packaged by mistake. They're not there in my previous packages.
Please see https://gitlab.archlinux.org/archlinux/ … -/issues/5
Offline
andreworg wrote:I'm no expert but I believe that the __pycache__ folders have been packaged by mistake. They're not there in my previous packages.
[...]
EDITED to add: I read the post from 2016 linked in the OP and maybe the .pyc files were not packaged by mistake. Still they were not there in 5.0.1Please see https://gitlab.archlinux.org/archlinux/ … -/issues/5
That is interesting. I did not know about the gitlab. (It looks quite fresh by the way.)
I'm not sure I got everything right, so I'll sum it up for a check.
The .pyc are intended to be packaged, they were not there in the previous version of the package due to some previous glitch and they were in the filesystem of those affected, like the OP and me, because we ran virt-manager as root (I can confirm that I did that at least once). So that's what generated the conflict.
Do I get it right? Thanks.
Offline
Do I get it right? Thanks.
That matches my understanding.
Offline