FS#40450 - [twisted] Error upgrading

Attached to Project: Arch Linux
Opened by héctor (hacosta) - Monday, 19 May 2014, 15:33 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 19 May 2014, 23:11 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:
When attempting to run pacman -Syu I get the following:

error: failed to commit transaction (conflicting files)
python2-twisted: /usr/lib/python2.7/site-packages/twisted/plugins/dropin.cache exists in filesystem
Errors occurred, no packages were upgraded.

Additional info:
[1]hacosta@enchilada ~$ p -Qo /usr/lib/python2.7/site-packages/twisted/plugins/dropin.cache
error: No package owns /usr/lib/python2.7/site-packages/twisted/plugins/dropin.cache

* package version(s)
hacosta@enchilada ~$ p -Qiq twisted
Name : twisted
Version : 13.2.0-1

hacosta@enchilada ~$ p -Si python2-twisted
Repository : testing
Name : python2-twisted
Version : 14.0.0-1


To the best of my knowledge, i haven't modified the root filesystem withot pacman

* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Monday, 19 May 2014, 23:11 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Monday, 19 May 2014, 15:55 GMT
Please see https://wiki.archlinux.org/index.php/Pacman#I_get_an_error_when_updating:_.22file_exists_in_filesystem.22.21
Comment by héctor (hacosta) - Monday, 19 May 2014, 16:01 GMT
I know how to solve this.. But why is it not a bug?
Comment by Doug Newgard (Scimmia) - Monday, 19 May 2014, 16:35 GMT
Because this happens from time to time. The user is expected to be able to deal with it.
Comment by Jens Adam (byte) - Monday, 19 May 2014, 20:52 GMT
No, it's the usual news-worthy 'package-got-renamed-without-enough-testing' bug.

See here: https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/twisted&id=3ffbd07b0c808d9a703f8f6efaffbb2a76d15639
And here is where the file originated: https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/twisted&id=f8c21e7bb145860f31e22ab25b6e22ed411d5b55

Could have been averted with a new pkgrel of the old version that deletes the file in .install.
Comment by Doug Newgard (Scimmia) - Monday, 19 May 2014, 21:10 GMT
No, this has nothing to do with the rename at all. It has to do with the cache file being included as part of the package now instead of being generated later. This has happened many times with python packages and it is not news-worthy.

Your first link is correct, it specifically says there will be manual intervention required. Your second link is meaningless, it is not where the file originated at all.

An intermediate package wouldn't have helped, either, unless the maintainer put off updated to this version until every user had upgraded to the intermediate package. Not an option.

Loading...