Starting with package version 42-1, the mkinitcpio systemd hook now includes systemd-pcrosseparator.service (as intended by systemd v261).
This affects the measurements of PCR values 0-7, 9 and 12-14.
If you configured the systemd hook and unlock LUKS partitions, that depend on these values, you need to re-enroll the TPM2 in use.
For guidance, please refer to systemd-cryptenroll(1), or the ArchWiki article on systemd-cryptenroll, when using pinned values.
Refer to systemd-pcrlock(8), when relying on custom policies and a disabled systemd-pcrlock-make-policy.service.
If you get:
error: failed to prepare transaction (could not satisfy dependencies)
:: installing nettle (4.0-1.0) breaks dependency 'libnettle.so=8-32' required by wget
Remove wget first:
Then update normally
Then you can add wget again (now depending on nettle3):
Also you might have to have nettle and nettle3 installed in parallel.
Previously, we installed its contents in a way that made pacman not
aware of the files (using VBoxManage extpack install ... from an
install script). To mitigate issues during upgrade, you can use one of
the following methods:
- Uninstall
virtualbox-ext-vnc before upgrading the system, then
installing it again.
- Run
VBoxManage extpack uninstall 'VNC' as root before upgrading the
system.
- Instruct
pacman once to overwrite the existing files:
pacman -Syu --overwrite '/usr/lib/virtualbox/ExtensionPacks/VNC/*'
We are currently experiencing a high volume of malicious package adoptions and updates in the Arch User Repository.
We are actively working to track down existing malicious commits and attempting to prevent additional malicious commits from being pushed.
While this is happening, and while we work to create a more permanent solution, users may see issues with the following:
- Creating new accounts on the AUR
- Pushing package updates
- Adopting or creating new packages
We continue to encourage all users of AUR packages to review all PKGBUILD and install script changes when updating, especially during this time.
If you notice suspicious commits to a package that you use, please reach out to Arch staff via the aur-general mailing list with more information.