Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38601 - [python-dbus] fails to upgrade

Attached to Project: Arch Linux
Opened by Sebastián Peyrott (Pse) - Tuesday, 21 January 2014, 13:41 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Sunday, 26 January 2014, 17:28 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description: python-dbus fails to upgrade due to conflicting files:

Additional info:
* python-dbus-1.2.0-2 (upgrade from python-dbus-1.2.0-1).

error: failed to commit transaction (conflicting files)
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/__init__.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/_compat.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/_dbus.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/_expat_introspect_parser.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/_version.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/bus.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/connection.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/decorators.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/exceptions.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/lowlevel.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/proxies.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/service.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/__pycache__/types.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/mainloop/__pycache__/__init__.cpython-33.pyc exists in filesystem
python-dbus: /usr/lib/python3.3/site-packages/dbus/mainloop/__pycache__/glib.cpython-33.pyc exists in filesystem
Errors occurred, no packages were upgraded.

Steps to reproduce:
sudo pacman -Syu
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Sunday, 26 January 2014, 17:28 GMT
Reason for closing:  Not a bug
Comment by Sebastián Peyrott (Pse) - Tuesday, 21 January 2014, 13:45 GMT
Linked ticket (caused by):  FS#38592 
Comment by Jan de Groot (JGC) - Tuesday, 21 January 2014, 17:59 GMT
Just overwrite them. These files were not tracked in the old package.
Comment by Sebastián Peyrott (Pse) - Tuesday, 21 January 2014, 18:00 GMT
I realized as much. However I thought a proper solution would be to handle this in the package itself, or perhaps post an update notice in the home page, as is done with other required manual interventions.
Comment by Timothée Ravier (Siosm) - Wednesday, 22 January 2014, 18:11 GMT
I think a short news item would be great here.
Comment by Sam Stoelinga (samos123) - Thursday, 23 January 2014, 22:10 GMT
So we just delete all the .pyc files in conflict and then continue with update? Agree that a news item would be nice to have with instructions.
Comment by Sebastián Peyrott (Pse) - Thursday, 23 January 2014, 22:12 GMT
Sam, you can also do:

sudo pacman -S --force python-dbus

And then continue normally.
Comment by Sam Stoelinga (samos123) - Thursday, 23 January 2014, 22:22 GMT
Thanks that seems more easy lol, i deleted them manually and didn't have to force install that way.
Comment by Doug Newgard (Scimmia) - Sunday, 26 January 2014, 17:14 GMT
Handle it in the package? News item? You've got to be kidding.

This is straight forward and covered in the wiki. As an Arch user, you are expected to be able to handle it.
Comment by Sam Stoelinga (samos123) - Sunday, 26 January 2014, 17:24 GMT
@Goug Newgard: Why not handle it in the package if this would prevent the upgrade from breaking. Even if we know the user can do it or expect he can do it, doesn't mean we should let them do it.

And I thought nearly all updated that require user intevention would be posted as news item. Thought that was a general thing. It's the first place I look if some update won't apply after that Google.

(I'm just a noob been using the same Arch installation for 4-5 years now and updating every week, while sometimes breaking and fixing my system and I like it :D)

Loading...