FS#24904 - pacman does not handle the file -> directory case with conflicts
Attached to Project:
Pacman
Opened by Ionut Biru (wonder) - Monday, 27 June 2011, 08:48 GMT
Last edited by Allan McRae (Allan) - Tuesday, 19 July 2011, 05:25 GMT
Opened by Ionut Biru (wonder) - Monday, 27 June 2011, 08:48 GMT
Last edited by Allan McRae (Allan) - Tuesday, 19 July 2011, 05:25 GMT
|
Details
Summary and Info:
:: Replace zope-interface with extra/python2-zope-interface? [Y/n] y resolving dependencies... looking for inter-conflicts... Remove (1): zope-interface-3.6.3-1 Total Removed Size: 0.97 MB Targets (8): dbus-glib-0.94-2 fb-client-0.8.1-1 neon-0.29.6-2 perl-xml-parser-2.41-1 pyalpm-0.4.3-1 readline-6.2.001-2 shadow-4.1.4.3-2 python2-zope-interface-3.6.3-1 Total Download Size: 0.00 MB Total Installed Size: 8.70 MB Proceed with installation? [Y/n] (8/8) checking package integrity [################################################################] 100% (8/8) checking for file conflicts [################################################################] 100% error: failed to commit transaction (conflicting files) python2-zope-interface: /usr/lib/python2.7/site-packages/zope.interface-3.6.3-py2.7.egg-info/ exists in filesystem Errors occurred, no packages were upgraded. In zope-interface package /usr/lib/python2.7/site-packages/zope.interface-3.6.3-py2.7.egg-info is a file and in python2-zope-interface /usr/lib/python2.7/site-packages/zope.interface-3.6.3-py2.7.egg-info/ is a directory debug log attached |
This task depends upon
Closed by Allan McRae (Allan)
Tuesday, 19 July 2011, 05:25 GMT
Reason for closing: Fixed
Additional comments about closing: http://projects.archlinux.org/pacman.git /commit/?h=maint&id=e378170c
Tuesday, 19 July 2011, 05:25 GMT
Reason for closing: Fixed
Additional comments about closing: http://projects.archlinux.org/pacman.git /commit/?h=maint&id=e378170c
FS#13932i tried locally with conflicts=(zope-interface) to try at least to have a clean update but it didn't take it in consideration.
I don't anticipate the fix getting out too quickly however as this is quite the edge case if we didn't even have test coverage for it yet.