- Arch-announce - lists.archlinux.org

[arch-announce] zabbix >= 7.4.1-2 may requires manual intervention
by Arch Linux: Recent news updates: Robin Candau 04 Aug '25

04 Aug '25

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](https://www.zabbix.com/documentation/current/en/manual/installati… 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 main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: - `PSK` files used for encrypted communication - Custom scripts for metrics collections or report generations - `sudoers` rules for metrics requiring elevated privileges to be collected - ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may [remove the obsolete user accounts from your system](https://wiki.archlinux.org/title/Users_and_groups#Other_examples_of…. URL: https://archlinux.org/news/zabbix-741-2-may-requires-manual-intervention/

1 0

[arch-announce] linux-firmware >= 20250613.12fe085f-5 upgrade requires manual intervention
by Arch Linux: Recent news updates: Jan Alexander Steffens 21 Jun '25

21 Jun '25

With `20250613.12fe085f-5`, we split our firmware into several vendor-focused packages. `linux-firmware` is now an empty package depending on our default set of firmware. Unfortunately, this coincided with upstream reorganizing the symlink layout of the NVIDIA firmware, resulting in a situation that Pacman cannot handle. When attempting to upgrade from `20250508.788aadc8-2` or earlier, you will see the following errors: linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystem To progress with the system upgrade, first remove `linux-firmware`, then reinstall it as part of the upgrade: # pacman -Rdd linux-firmware # pacman -Syu linux-firmware URL: https://archlinux.org/news/linux-firmware-2025061312fe085f-5-upgrade-requir…

1 0

[arch-announce] Plasma 6.4.0 will need manual intervention if you are on X11
by Arch Linux: Recent news updates: Tomaz Canabrava 20 Jun '25

20 Jun '25

On Plasma 6.4 the wayland session will be the only one installed when the users does not manually specify kwin-x11. With the recent split of kwin into kwin-wayland and kwin-x11, users running the old X11 session needs to manually install plasma-x11-session, or they will not be able to login. Currently pacman is not able to figure out your personal setup, and it wouldn't be ok to install plasma-x11-session and kwin-x11 for every one using Plasma. ### tldr: Install plasma-x11-session if you are still using x11 URL: https://archlinux.org/news/plasma-640-will-need-manual-intervention-if-you-…

1 0

[arch-announce] Transition to the new WoW64 wine and wine-staging
by Arch Linux: Recent news updates: Peter Jung 16 Jun '25

16 Jun '25

We are transitioning the wine and wine-staging package to a pure [wow64](https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0#wow64) build. This change removes the dependency on the multilib repository for wine and wine-staging. The main reason for this is to align with upstream Wine development, which simplifies packaging and the dependency chain. Potential Issues: * OpenGL Performance: A known limitation of the new WoW64 mode is reduced performance for 32-bit applications that use OpenGL directly * Breaking Changes: Existing 32-bit prefixes needs to be recreated If you are facing issues with 32 bit prefixes, please recreate these and reinstall the application. URL: https://archlinux.org/news/transition-to-the-new-wow64-wine-and-wine-stagin…

1 0

[arch-announce] Valkey to replace Redis in the [extra] Repository
by Arch Linux: Recent news updates: Andrew Crerar 17 Apr '25

17 Apr '25

Valkey, a high-performance key/value datastore, will be replacing redis in the [extra] repository. This change is due to Redis modifying its license from BSD-3-Clause to RSALv2 and SSPLv1 on March 20th, 2024[0]. Arch Linux Package Maintainers intend to support the availability of the redis package for roughly 14 days from the day of this post, to enable a smooth transition to valkey. After the 14 day transition period has ended, the redis package will be moved to the AUR. Also, from this point forward, the redis package will not receive any additional updates and should be considered deprecated until it is removed. Users are recommended to begin transitioning their use of Redis to Valkey as soon as possible to avoid possible complications after the 14 day transition window closes. [0] https://github.com/redis/redis/commit/0b34396924eca4edc524469886dc5be6c77ec… URL: https://archlinux.org/news/valkey-to-replace-redis-in-the-extra-repository/

1 0

[arch-announce] Cleaning up old repositories
by Arch Linux: Recent news updates: Sven-Hendrik Haase 16 Feb '25

16 Feb '25

Around two years ago, we've merged the `[community]` repository into `[extra]` as part of the [git migration](https://archlinux.org/news/git-migration-completed/). In order to not break user setups, we kept these repositories around in an unused and empty state. We're going to clean up these old repositories on **2025-03-01**. On systems where `/etc/pacman.conf` still references the old `[community]` repository, `pacman -Sy` will return an error on trying to sync repository metadata. The following deprecated repositories will be removed: `[community]`, `[community-testing]`, `[testing]`, `[testing-debug]`, `[staging]`, `[staging-debug]`. Please make sure to remove all use of the aforementioned repositories from your `/etc/pacman.conf` (for which a `.pacnew` was shipped with `pacman>=6.0.2-7`)! URL: https://archlinux.org/news/cleaning-up-old-repositories/

1 0

[arch-announce] Glibc 2.41 corrupting Discord installation
by Arch Linux: Recent news updates: Frederik Schwan 03 Feb '25

03 Feb '25

We plan to move `glibc` and its friends to stable later today, Feb 3. After installing the update, the Discord client will show a red warning that the installation is corrupt. This issue has been fixed in the Discord canary build. If you rely on audio connectivity, please use the canary build, login via browser or the flatpak version until the fix hits the stable Discord release. There have been no reports that (written) chat connectivity is affected. URL: https://archlinux.org/news/glibc-241-corrupting-discord-installation/

1 0

[arch-announce] Critical rsync security release 3.4.0
by Arch Linux: Recent news updates: Robin Candau 16 Jan '25

16 Jan '25

We'd like to raise awareness about the rsync security release version `3.4.0-1` as described in our advisory [ASA-202501-1](https://security.archlinux.org/ASA-202501-1). An attacker only requires anonymous read access to a vulnerable rsync server, such as a public mirror, to execute arbitrary code on the machine the server is running on. Additionally, attackers can take control of an affected server and read/write arbitrary files of any connected client. Sensitive data can be extracted, such as OpenPGP and SSH keys, and malicious code can be executed by overwriting files such as `~/.bashrc` or `~/.popt`. We highly advise anyone who runs an rsync daemon or client prior to version `3.4.0-1` to upgrade and reboot their systems immediately. As Arch Linux mirrors are mostly synchronized using rsync, we highly advise any mirror administrator to act immediately, even though the hosted package files themselves are cryptographically signed. All infrastructure servers and mirrors maintained by Arch Linux have already been updated. URL: https://archlinux.org/news/critical-rsync-security-release-340/

1 0

[arch-announce] Providing a license for package sources
by Arch Linux: Recent news updates: Rafael Epplée 19 Nov '24

19 Nov '24

Arch Linux hasn't had a license for any package sources (such as PKGBUILD files) in the past, which is potentially problematic. Providing a license will preempt that uncertainty. In [RFC 40](https://rfc.archlinux.page/0040-license-package-sources/) we agreed to change all package sources to be licensed under the very liberal [0BSD](https://spdx.org/licenses/0BSD.html) license. **This change will not limit what you can do with package sources**. Check out [the RFC](https://rfc.archlinux.page/0040-license-package-sources/) for more on the rationale and prior discussion. Before we make this change, we will provide contributors with a way to voice any objections they might have. Starting on 2024-11-19, over the course of a week, contributors will receive a single notification email listing all their contributions. - If you receive an email and agree to this change, there is no action required from your side. - If you do not agree, please reply to the email and we'll find a solution together. If you contributed to Arch Linux packages before but didn't receive an email, please contact us at package-sources-licensing(a)archlinux.org. URL: https://archlinux.org/news/providing-a-license-for-package-sources/

1 0

[arch-announce] Manual intervention for pacman 7.0.0 and local repositories required
by Arch Linux: Recent news updates: Morten Linderud 14 Sep '24

14 Sep '24

With the release of [version 7.0.0][0] pacman has added support for downloading packages as a separate user with dropped privileges. For users with local repos however this might imply that the download user does not have access to the files in question, which can be fixed by assigning the files and folder to the `alpm` group and ensuring the executable bit (`+x`) is set on the folders in question. $ chown :alpm -R /path/to/local/repo Remember to [merge the .pacnew][1] files to apply the new default. Pacman also introduced [a change][2] to improve checksum stability for git repos that utilize `.gitattributes` files. This might require a one-time checksum change for `PKGBUILD`s that use git sources. [0]: https://gitlab.archlinux.org/pacman/pacman/-/blob/master/NEWS?ref_type=heads [1]: https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave [2]: https://gitlab.archlinux.org/pacman/pacman/-/commit/9548d6cc765b1a8dcf933e8… URL: https://archlinux.org/news/manual-intervention-for-pacman-700-and-local-rep…

1 0