Tom Gundersen wrote:
As of `filesystem-2012.6-2` the folders `/var/run` and `/var/lock` will be
replaced by symlinks to `/run` and `/run/lock`, respectively.
On most systems this is already the case, as `initscripts` create the symlinks
on boot. However, these symlinks are not owned by any package, which is what we
are fixing with this upgrade.
If the symlinks are already in place on your system (which should be the case
for most people), then you can simply perform
`# pacman -Syu --ignore filesystem && pacman -S filesystem --force`
Otherwise, if `/var/run` or `/var/lock` are directories (e.g. if you are using
`systemd` and never booted with `initscripts`) you need to delete the
directories before performing the update. As these directories are used at
runtime, it is recommended to shutdown any background tasks before performing
`# rm -rf /var/run /var/lock && pacman -Syu && reboot`
Note: In general, it is strongly advised to avoid the `--force` switch as it is
not safe. However, in this particular case it is safe, and suggested to avoid
having to manually delete the `/var/run` or `/var/lock` symlinks.
Lastly, on upgrading `filesystem` users of kernels prior to `linux-3.4` will get
a warning about permissions on `/sys`. This is nothing to worry about, as of
`linux-3.4` the permissions will be `555`, and this upgrade reflects this in the
Gaetan Bisson wrote:
For the past six months, pacman's package verification features were turned off
by default while we were figuring out the details of our public-key
They have finally been enabled in pacman-4.0.3-2; when you upgrade, you will be
prompted to run:
pacman-key --populate archlinux
This sets up a local keyring for pacman, and populates it with the data needed
to authenticate official packages. This includes five master keys used to
authenticate Arch Linux packagers (developers and trusted users), so you do not
need to know who joins or leaves the team: you only have to verify those five
master keys once and for all. The populate command will prompt you to do so;
please do this cautiously by checking the fingerprints displayed against [those
published on our website].
Then, merge your `pacman.conf` with `pacman.conf.pacnew`, that is, enable
package verification through the SigLevel option, and you should be good to go.
For details on the development of pacman and archlinux-keyring, see the blog
posts of [Allan] and [Pierre].
Dave Reisner wrote:
systemd and udev have been merged upstream. We will still ship them in separate
packages. However, in order to keep things simple, udev will now be part of a
package called systemd-tools. This package contains several other standalone
tools which can be used without systemd. The astute reader will note that this
also means the entirety of systemd is available in the core repository.
Please replace udev with systemd-tools when prompted. If you upgrade the linux
package at the same time, you may see an error during initramfs creation that
the udev hook is not found. After the upgrade completes, please rerun
'mkinitcpio -p linux' to ensure that a bootable image is created for the newly