The following packages may require manual intervention due to the upgrade from 9.0 to 10.0:
- aspnet-runtime
- aspnet-targeting-pack
- dotnet-runtime
- dotnet-sdk
- dotnet-source-built-artifacts
- dotnet-targeting-pack
pacman may display the following error failed to prepare transaction (could not satisfy dependencies) for the affected packages.
If you are affected by this and require the 9.0 packages, the following commands will update e.g. aspnet-runtime to aspnet-runtime-9.0:
pacman -Syu aspnet-runtime-9.0
pacman -Rs aspnet-runtime
The waydroid package prior to version 1.5.4-2 (including aur/waydroid) creates Python byte-code files (.pyc) at runtime which were untracked by pacman. This issue has been fixed in 1.5.4-3, where byte-compiling these files is now done during the packaging process.
As a result, the upgrade may conflict with the unowned files created in previous versions. If you encounter errors like the following during the update:
error: failed to commit transaction (conflicting files)
waydroid: /usr/lib/waydroid/tools/__pycache__/__init__.cpython-313.pyc exists in filesystem
waydroid: /usr/lib/waydroid/tools/actions/__pycache__/__init__.cpython-313.pyc exists in filesystem
waydroid: /usr/lib/waydroid/tools/actions/__pycache__/app_manager.cpython-313.pyc exists in filesystem
You can safely overwrite …
The dovecot 2.4 release branch has made breaking changes which result in it being incompatible with any <= 2.3 configuration file.
Thus, the dovecot service will no longer be able to start until the configuration file was migrated, requiring manual intervention.
For guidance on the 2.3-to-2.4 migration, please refer to the following upstream documentation:
Upgrading Dovecot CE from 2.3 to 2.4
Furthermore, the dovecot 2.4 branch no longer supports their replication feature, it was removed.
For users relying on the replication feature or who are unable to perform the 2.4 migration right now, we provide alternative …
We want to provide an update on the recent service outages affecting our infrastructure. The Arch Linux Project is currently experiencing an ongoing denial of service attack that primarily impacts our main webpage, the Arch User Repository (AUR), and the Forums.
We are aware of the problems that this creates for our end users and will continue to actively work with our hosting provider to mitigate the attack. We are also evaluating DDoS protection providers while carefully considering factors including cost, security, and ethical standards.
To improve the communication around this issue we will provide regular updates on …
Starting with 7.4.1-2, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared zabbix user account (as originally intended by upstream and done by other distributions):
- zabbix-server
- zabbix-proxy
- zabbix-agent (also used by the
zabbix-agent2 package)
- zabbix-web-service
This shared zabbix user account is provided by the newly introduced zabbix-common split package, which is now a dependency for all relevant zabbix-* packages.
The switch to the new user account is handled automatically for the corresponding …
