FS#6406 - upgrading autofs when packages are stored on an autofs fs breaks
Attached to Project:
Arch Linux
Opened by Rob Page (robrob) - Monday, 12 February 2007, 12:04 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 12 December 2008, 18:35 GMT
Opened by Rob Page (robrob) - Monday, 12 February 2007, 12:04 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 12 December 2008, 18:35 GMT
|
Details
I have my packages directory on a remote smbfs, which I
mount using autofs. I just tried to upgrade my autofs
package and (perhaps not too surprisingly) the upgrade
failed with "upgrading autofs... could not open package: No
such file or directory"
Rerunning, i get: [rob@rob-laptop ~]$ sudo pacman -Su Password: Targets: dbus-1.0.2-4 dbus-glib-0.72-2 gxine-0.5.11-1 kernel26-2.6.20-2 libx11-1.1.1-2 spidermonkey-1.60-1 Total Package Size: 23.6 MB Proceed with upgrade? [Y/n] :: Retrieving packages from current... warning: no /var/cache/pacman/pkg cache exists. creating... warning: couldn't create package cache, using /tmp instead Note, that autofs has now been dropped from the list of files needing to be installed. However if i try to reinstall/upgrade autofs I get: [root@rob-laptop mnt]# pacman -S autofs Targets: autofs-4.1.4-4 Total Package Size: 0.1 MB Proceed with upgrade? [Y/n] checking package integrity... done. loading package data... done. checking for file conflicts... error: the following file conflicts were found: autofs: /etc/autofs/auto.master: exists in filesystem autofs: /etc/conf.d/autofs: exists in filesystem errors occurred, no packages were upgraded. |
This task depends upon
Also, I understand, the new pacman checks for user changes to config files, so this shouldn't be a problem anymore.