[arch-general] system-config-printer: conflicting files
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello fellow Archers, I received the following error while upgrading system-config-printer:
error: failed to commit transaction (conflicting files) system-config-printer: /usr/share/system-config-printer/debug.pyc exists in filesystem Errors occurred, no packages were upgraded.
Apparently, at some point python automatically compiled debug.py into debug.pyc to increase long term performance. However, the new package has debug.pyc presupplied. The solution was to delete debug.pyc, then everything installs cleanly and works fine. Of course, this begs the question: Should a compiled python module be supplied in a package (debug.pyc), or should the local machine interpret/compile/do whatever it wants with a python script (debug.py)? - --Kyle -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTUH7GAAoJEN5rMzXPJBsQvwkP/jrjwgfai7jUTTFI980qQdaM nu6u/kms6Ys72uJIvxF3a0b94ZprbLe6bjshzCBW0fJuBHrZ+Deb1Xdt2i10b3pV O/JgZzYMsICVqF2MYdn+GZ9T/GYkLpzLWctwBCnHwQKABIw+T5Jk4CwdNLTnd4V5 pmxynMi/A3RzYFsxFQLcNK6a1sk/FhVmwDSAk5WB2feKjf/i614dH8Uf0aJxRcq+ LFg+eFndpEpMp77j0DnxcTwAR6RzdE19NCNf9rfBvctGpyE2nzdYE8bcof66mLoB yWR2jmRC2CYwOxU556I+Bg4TIGy4SQunqkc0hKEG+nQ6/xSOV72CF7ZCFBOKrLsW 8rGPHDNXFFbLeE6kcR+hnEYaKjLTLn+o+BwV9CJSB3l3aCXpoBCJ9kDiEPEfPR6h mZwP77BpBUMTfclTYL/F2mR0NDd4615CWxXd6wHXGCex+WrA4FTyGqGQgUvPa5Bu 9yB/oMyLthgGL9S5CN0N2VcRdPQB4X44DhUieOMqWAO+KVKmJGfohkCRRHy7UOCY JLh8dkA9JBnoeQ9wLFXn7ibSFxJAVfUeddnmsKOaRnVSGVjGuKYbb9IcFQ/xcfBa ghnTIOk6l15Rrzd9pxfoXSDz8eIeC9UWGQN13Q6waD1gOjZVPS2rgmM2vNpYzT5M iyOEOWaj6AVvni9eADE1 =tWUo -----END PGP SIGNATURE-----
On 2014-04-17 20:24, Kyle Terrien wrote:
Hello fellow Archers,
I received the following error while upgrading system-config-printer:
error: failed to commit transaction (conflicting files) system-config-printer: /usr/share/system-config-printer/debug.pyc exists in filesystem Errors occurred, no packages were upgraded.
Apparently, at some point python automatically compiled debug.py into debug.pyc to increase long term performance. However, the new package has debug.pyc presupplied.
The solution was to delete debug.pyc, then everything installs cleanly and works fine.
Of course, this begs the question: Should a compiled python module be supplied in a package (debug.pyc), or should the local machine interpret/compile/do whatever it wants with a python script (debug.py)?
- --Kyle
Yes, they should be included in the package. 1. The user running these scripts usually doesn't have write access to the dir they're in, so more often than not, the .pyc files don't get saved. This makes the load times for the script longer. 2. If it is run as root, a file gets created that pacman knows nothing about. It will leave crap behind when upgrading or removing.
participants (2)
-
Doug Newgard
-
Kyle Terrien