Mkinitcpio upgrade: "exists in filesystem" error

Question

When running pacman -Syu, I get the following errors:
error: failed to commit transaction (conflicting files)
mkinitcpio: /lib/initcpio/hooks/keymap exists in filesystem
mkinitcpio: /lib/initcpio/hooks/udev exists in filesystem
mkinitcpio: /lib/initcpio/install/keymap exists in filesystem
mkinitcpio: /lib/initcpio/install/udev exists in filesystem
mkinitcpio: /lib/initcpio/udev/load-modules.sh exists in filesystem
Errors occurred, no packages were upgraded.
error: pacman exited with an error (256)
I assume this has to do with the changes to mkinitcpio mentioned on the front page
I have earlier modified the HOOKS line in /etc/mkinitcpio.conf
HOOKS="base udev autodetect pata scsi sata keymap uresume filesystems"
So, what do I do? Force the upgrade?

Answer 1

I'm getting the same error on yaourt -Syu (also occurs when trying to upgrade mkinitcpio)
error: failed to commit transaction (conflicting files)
mkinitcpio: /lib/initcpio/hooks/keymap exists in filesystem
mkinitcpio: /lib/initcpio/hooks/udev exists in filesystem
mkinitcpio: /lib/initcpio/install/keymap exists in filesystem
mkinitcpio: /lib/initcpio/install/udev exists in filesystem
mkinitcpio: /lib/initcpio/udev/load-modules.sh exists in filesystem
Errors occurred, no packages were upgraded.
The upgrade is from mkinitcpio 0.5.30-1 to 0.6.2-1 and to mkinitcpio-busybox 1.15.3-5 (new package)
I'm running x86_64. I can update other packages without problems.
Edit: I forced the upgrade of mkinitcpio and rebuilt the kernel image. The new image doesn't work (it can't find /sbin/udevd, which does exist). If I remove klibc-*, the kernel won't build at all (Can't build hook udev).
Booting the new kernel image:
:: Loading Initramfs
:: Starting udev...
/init: line 24: /sbin/udevd: not found
done.
:: Running Hook [udev]
:: Loading udev... /init: line 11: /sbin/udevd: not found
/init: line 11: sbin/udevadm: not found
/init: line 11: sbin/udevadm: not found
done.
Waiting 10 seconds for device /dev/disk/by-uuid/(...)...
\nRoot device 'dev/disk/by-uuid/(...)' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/disk/by-uuid/(...)'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
/bin/sh: can't access tty; job control turned off
[ramfs /]# _
I can't do anything with the recovery console using my usb keyboard.
/sbin/udevd does exist.
Last edited by gopher292 (2010-02-18 00:30:37)