Arch Linux

zgvaum

Member

Registered: 2016-03-24

Posts: 2

[solved] [virt-install] Conflicting files with virt-manager

Running

pacman -Syu

today, I get:

error: failed to commit transaction (conflicting files)
virt-install: /usr/share/virt-manager/virtcli/__init__.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtcli/cliconfig.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/__init__.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/capabilities.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/cli.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/clock.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/cloner.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/connection.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/cpu.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/device.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/deviceaudio.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicechar.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicecontroller.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicedisk.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicefilesystem.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicegraphics.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicehostdev.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/deviceinput.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/deviceinterface.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicememballoon.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicepanic.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/deviceredirdev.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicerng.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicesmartcard.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicetpm.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicevideo.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/devicewatchdog.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/diskbackend.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/distroinstaller.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainblkiotune.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainfeatures.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainmemorybacking.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainmemorytune.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainnumatune.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domainresource.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/domcapabilities.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/guest.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/idmap.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/installer.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/interface.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/network.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/nodedev.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/osdict.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/osxml.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/pm.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/pollhelpers.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/progress.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/seclabel.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/snapshot.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/storage.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/support.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/uri.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/urlfetcher.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/util.pyc exists in filesystem
virt-install: /usr/share/virt-manager/virtinst/xmlbuilder.pyc exists in filesystem
Errors occurred, no packages were upgraded.

Versions:

community/virt-install    1.3.2-3      1.3.2-4        3.29 MiB
community/virt-manager    1.3.2-3      1.3.2-4        0.01 MiB

Looks like 1.3.2-4 was just uploaded today.  Is the package genuinely broken and I should file a bug or is something amiss with my system?

Last edited by zgvaum (2016-03-24 18:58:03)

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: [solved] [virt-install] Conflicting files with virt-manager

https://projects.archlinux.org/svntogit … 43f930a02f

The package used to not install compiled/optimized pyc/pyo files, until the last update.
So when running it yourself, it byte-compiled the pyc files and saved them -- but they weren't tracked by pacman. Now the new package is doing the right thing and installing them...

This would be a case where it is appropriate to use the `--force` flag with pacman.

EDITED for clarity: Of course, I mean forcing that specific package (`pacman -Sy && pacman -S --force virt-install && pacman -Su`). Please don't force an entire system upgrade when it is completely unnecessary and introduces the potential for disaster. See below.

Last edited by eschwartz (2016-03-31 13:52:11)

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

sja1440

Member

From: Milano, Italy

Registered: 2015-01-03

Posts: 7

Re: [solved] [virt-install] Conflicting files with virt-manager

Thank you Eschwartz.

Your comment helped me understand and overcome the problem.

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: [solved] [virt-install] Conflicting files with virt-manager

Excellent.

Since your problem is solved, please edit your first post to include the word [solved] in the title. Whoops, you're not the OP.

Last edited by eschwartz (2016-03-24 18:55:39)

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

zgvaum

Member

Registered: 2016-03-24

Posts: 2

Re: [solved] [virt-install] Conflicting files with virt-manager

Eschwartz, thank you for the help.  Makes sense.  Shouldn't this be a package bug, though?  I (perhaps naively) assume that being unable to upgrade a package using the normal method (i.e. without --force) is a bug.

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,197

Re: [solved] [virt-install] Conflicting files with virt-manager

Nope. Those files were untracked, meaning something else put them there. Pacman won't overwrite them by default. This is expected with untracked files.

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: [solved] [virt-install] Conflicting files with virt-manager

Nope. Those files were untracked, meaning something else put them there. Pacman won't overwrite them by default. This is expected with untracked files.

I think what zgvaum is saying is, the package should've always provided those files -- and is at fault for putting people in such a position.
At  least the average userspace app doesn't normally have root permissions to write pyc files there...

So perhaps it would've been nice to have it upgraded in such a way as to not confuse people.
(Maybe include the pre-remove scriptlet first, and later add the pyc files to the package itself.)

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

nose

Member

Registered: 2014-09-22

Posts: 5

Re: [solved] [virt-install] Conflicting files with virt-manager

Thank you, i used:

pacman -Syu --force

as suggested and every works now!

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,197

Re: [solved] [virt-install] Conflicting files with virt-manager

Thank you, i used:

pacman -Syu --force

as suggested and every works now!

No, never, ever use --force on an entire upgrade. Use it on just the package that needs it.

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: [solved] [virt-install] Conflicting files with virt-manager

Thank you, i used:

pacman -Syu --force

as suggested and every works now!

As Scimmia said, that is NOT what I suggested!

`--force` is a powerful capability that gives you the control over your system necessary to do dangerous things -- or break your system.
Use it sparingly, and only for what needs it.

You wouldn't run every command as root, just because some things need root permissions, would you? Likewise, don't force every package, just because one package needs it.

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

totalkrill

Member

Registered: 2013-09-01

Posts: 15

Re: [solved] [virt-install] Conflicting files with virt-manager

Hey!

I had the same problem, looked and saw that the '--force' flag was recommended, and thus also ran "pacman -Syu --force"

While the packages was updating I read the responses and realised what horrors i could have unleashed upon my system. Althougt the --force flag solved it, I would appreciate an edit somewhere so that the recommended solution of just upgrading the specific package would somehow be presented first, to save such hasty persons as myself from possible horrors.

Thanks!

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: [solved] [virt-install] Conflicting files with virt-manager

Done, and sorry -- I should've thought of that myself!

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: [solved] [virt-install] Conflicting files with virt-manager

You wouldn't run every command as root, just because some things need root permissions, would you?

Too bad there's no way to implement that practice with scripts, given that in many cases root permissions are only needed for a few of the commands.</gratuitiouslyOT>

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: [solved] [virt-install] Conflicting files with virt-manager

Script those commands with sudo?

If it really needs to run without user interaction you can *probably* figure something not too terribly inconvenient out with `sudo -u nonrootuser`.
Or use an initial verification plus a sudoloop in the background.

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: [solved] [virt-install] Conflicting files with virt-manager

'Embedding' sudo is what I did in my early scripts. But apparently that's considered bad practice, good practice being to call the script with sudo. A sudoloop is the best solution I came across, which isn't saying much IMO.

Anyway, enough OT. I probably should have just posted this in grr thread.

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner