On Wed, Jun 06, 2012 at 11:31:52PM +1000, Gaetan Bisson wrote:
[2012-06-03 16:58:24 +0200] Tom Gundersen:
# pacman -Syu --ignore filesystem && pacman -S filesystem --force
On a VM created today with systemd, enabling [testing] yields:
# pacman -S filesystem --force resolving dependencies... looking for inter-conflicts...
Targets (1): filesystem-2012.6-2
Total Installed Size: 0.30 MiB Net Upgrade Size: 0.23 MiB
Proceed with installation? [Y/n] y (1/1) checking package integrity [#####################################] 100% (1/1) loading package files [#####################################] 100% (1/1) checking available disk space [#####################################] 100% (1/1) upgrading filesystem [#####################################] 100% warning: directory permissions differ on sys/ filesystem: 755 package: 555 error: extract: not overwriting dir with file var/run error: problem occurred while upgrading filesystem error: could not commit transaction error: failed to commit transaction (transaction aborted) Errors occurred, no packages were upgraded.
But that's not all; then:
# pacman -Q filesystem filesystem 2012.6-2 # ls -la /var | grep run lrwxrwxrwx 1 root root 11 Jun 6 10:13 lock -> ../run/lock drwxr-xr-x 4 root root 72 Jun 6 11:47 run
So pacman did not touch /var/run but "validated" the upgrade anyhow. What am I doing wrong?
-- Gaetan
I think this happens when /var/run has files in it. pacman should probably be aborting here before it gets to sync_commit.