- Arch-dev-public - lists.archlinux.org

GitLab behind Anubis
by Kristian Klausen 14 Dec '25

14 Dec '25

Hi all, To deflect yet another scraping attack against our GitLab instance, it has been hastily put behind Anubis. This may have broken stuff. Please reach out if notice anything that does not work, either by replying to this email or #archlinux-devops on IRC. Cheers, Kristian Klausen DevOps

1 0

Python 3.14 rebuild starting
by Jelle van der Waa 13 Dec '25

13 Dec '25

Hi all! Let's start the Python 3.14 rebuild as Christmas present for our users! This effectively means [staging] will be blocked for a longer period of time before everything is rebuild. I'll start after the hdf5 rebuild has been moved and will first bootstrap the build tooling (setuptools, flit, pytest, etc.). When that's done a todolist will be opened for all Python packages. Do note that there will be cycles which need to be broken up by building packages without tests first. Greetings, Jelle

1 0

Fwd: Looking for feedback on CONFIG_MODULE_HASHES for Linux
by Robin Candau 10 Dec '25

10 Dec '25

Hi everyone, As discussed during this year's Arch summit, Thomas is seeking help / support from projects that could benefit from his patch set which aims to enable reproducible kernel packages for Linux distributions (see the forwarded mail below). As far as I can tell, this is something we would be interested in. I think it would be nice if we could "officially" claim our interest as "Arch Linux" to hopefully provide some assistance to Thomas for his incoming discussion with upstream. Does any of the kernel packages maintainers on our side wants to jump in (or anyone else interested with some kernel knowledge, I guess)? -------- Forwarded Message -------- Subject: Looking for feedback on CONFIG_MODULE_HASHES for Linux Date: Thu, 13 Nov 2025 21:10:58 +0100 From: Thomas Weißschuh via rb-general <rb-general(a)lists.reproducible-builds.org> Reply-To: General discussions about reproducible builds <rb-general(a)lists.reproducible-builds.org> To: rb-general(a)lists.reproducible-builds.org CC: Thomas Weißschuh <thomas(a)t-8ch.de> Hi everyone, I am the author of the CONFIG_MODULE_HASHES patchset [0] for the Linux kernel which aims to enable reproducible kernel packages for Linux distributions. My goal is to reignite development and continue with the upstream process. To have a better base to argue with I'd like to get some confirmation that distributions have looked at the patches and do intent to adapt this scheme when it is available in the mainline kernel. That should help me get some leverage with the upstream maintainers. The current form of the patches can be found at [1], they are only slightly adapted from the previous submission to LKML. Remaining open topics before the next submission are proper IMA support and stripping of modules. Future changes may introduce more hash algorithms and performance improvements, but these should not be relvant for now. So if you are packaging Linux for your distribution, have looked at my patches and are eager to use them, please let me know. My plan is to talk with the upstream maintainers at the upcoming Linux Plumbers Conference on 11th of December. Thanks, Thomas [0] https://lore.kernel.org/lkml/20250429-module-hashes-v3-0-00e9258def9e@weiss… [1] https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git…

2 1

News draft: .NET packages may require manual intervention
by George Rawlinson 09 Dec '25

09 Dec '25

The following packages may require manual intervention due to the update 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: ```sh pacman -Syu aspnet-runtime-9.0 pacman -Rs aspnet-runtime ```

1 0

Archive repos snapshot changes
by Kristian Klausen 09 Nov '25

09 Nov '25

Hi all, We (DevOps) want to reduce [the I/O stress][1] on the archive server (archive.archlinux.org) by reducing the numbers of inodes (currently 55 millions). Most of these inodes (52,6 millions) originates from the daily snapshot (64k inodes) of the repositories. Going forward only the database files and the "sources" directory will be included in the snapshot (~120 inodes + ~2400 inodes for "sources") and all HTTP requests for package files will be redirected to the relevant package at https://archive.archlinux.org/packages/. E.g. https://archive.archlinux.org/repos/2025/11/02/core/os/x86_64/linux-6.17.6.… -> https://archive.archlinux.org/packages/l/linux/linux-6.17.6.arch1-1-x86_64.… Package files from existing snapshots will be removed at a later date. The "sources" directory will be removed at a later date, when a proper replacement is in place. If no concerns are raised before 2025-11-21 EOD, we will move forward with the changes. [1] All inodes must be traveresed for backup and hardlinking Cheers, Kristian Klausen DevOps

1 0

Dropping qt5-webengine
by Antonio Rojas 08 Nov '25

08 Nov '25

Hi, Qt5 is EOL since May. In particular, qt5-webengine's Chromium ships with unfixed vulnerabilities. Its code is bitrotting, which also makes it a costly package to maintain due to the frequent API changes in its dependencies (I had to give up on system ffpmeg and switch to its ancient bundled version, and currently doesn't build against ICU 78). I therefore think it's wise to drop it from our repos. Its remaining reverse dependencies are: csoundqt - can be built without it by disabling remote debugging support, MR at [1] fcitx-libpinyin - archived upstream for over a year globalprotect-openconnect - very out of date, a new version switching to wbkitgtk and rust is available in testing. kchmviewer - dead upstream (no activity in 4 years) qmc2 - dead upstream (no activity in 1.5 years) wiznote - dead upstream (no activity in 4 years) openshot - the only case of a (semi-)maintained application still unported to Qt6 - there was an attempt 3 years ago [2] aborted due to some drama and no signs of new efforts since then, porting is non-trivial. If there are no objections (that include an offer to pick up maintenance of the package), I will drop it and all its unported reverse dependencies in a few days. [1] https://gitlab.archlinux.org/archlinux/packaging/packages/csoundqt/-/merge_… [2] https://github.com/OpenShot/openshot-qt/pull/4836

3 3

GitLab unavailable at the moment
by Jelle van der Waa 05 Nov '25

05 Nov '25

Hi All, GitLab is experiencing some high load due to unknown reasons, devops is investigating. Expect issues when updating packages so maybe postpone them if you can. Greetings, Jelle

2 1

News Draft: waydroid >= 1.5.4-3 update may require manual intervention
by George Hu 05 Nov '25

05 Nov '25

The `waydroid` package prior to version `1.5.4-2` (including `aur/waydroid`) creates byte-compiled Python 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 overwrite 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 remove the conflicting files by running the following command before upgrading: ```sh find /usr/lib/waydroid/tools/ -type d -name __pycache__ -exec sudo rm -rf '{}' + ``` -- Best Regards, George Hu / Integral

4 5

mkinitcpio v40, packaging changes and kernel-install
by Morten Linderud 04 Nov '25

04 Nov '25

Yo, I'm dropping the new `mkinitcpio` v40 release into [core-testing] right after this email. Generally the changes are not super interesting, but we got a new build system with meson for this release. This has given us the option to enable and disable the default hooks for `mkinitcpio` during building. As a result I have made two packaging decisions! # Disabled fallback image creation for new installs. Generally they are not super useful and people that need them can enable them if they would like too. This is only affects new installs as we can't change the hook files on existing installs. # Switched over to `systemd` hooks by default. This is generally a change I think we should have done a long time ago. The systemd side of our initramfs is getting a lot of changes thanks to systemd moving the needle forward, however our busybox hooks are not getting any of these improvements and have generally stalled for years. I have swapped things over on our side, and will continue to maintain the busybox hooks upstream. Further release notes can be found here: https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/releases/v40 # kernel-install Beyond this next on my todo is to see if we can move us wholesale away from the custom libalpm hooks we currently have to using `kernel-install`. This is going to make things much easier for us and users to swap between initrd and uki generators. It would also allow us to simplify our kernel installation and boot creation as we can probably automatically generate configs with hooks. I plan on writing a rough outline of my idea to arch-dev-public before doing a RFC, mostly because I haven't completely decided on how we would like to do this smoothly and people might have better ideas then me. -- Morten Linderud PGP: 9C02FF419FECBE16

1 0

News draft: dovecot >= 2.4 requires manual intervention
by Thore Bödecker 29 Oct '25

29 Oct '25

Hi folks, the upstream dovecot 2.4 branch comes with handful of breaking changes, mostly concerning configuration semantics and syntax. For this, upstream provides a migration guide [1]. We've kept dovecot 2.4.1 in [testing] for quite some time and it received a decent number of signoffs. There was already a bit of chatter on arch-general regarding the availability of a dovecot 2.4 package in [extra]. While slightly unintentional, I've built and pushed todays upstream release version 2.4.2 to [extra]. However, there is a feature disparity: the 2.4 branch no longer supports replication. My own setup relies on that particular feature and I've grown quite fond of it, so I'm a bit sad to see it going away. As per upstreams EOL announcement [2], the 2.3 branch is supposedly going to receive critical secrity fixes, which I considered "maintained enough" to warrant packaging it separately until upstream fully drops it. The following packages are now available in [extra]: - dovecot23 - pigeonhole23 - dovecot23-fts-elastic - dovecot23-fts-xapian Where applicable, they are configured with the necessary conflicts/provides. The most recent dovecot-2.4.2-3 build also contains the following dovecot.install notice: > ==> Dovecot 2.4 is incompatible with older configurations and requires manual intervention. > ==> Refer to 'https://doc.dovecot.org/latest/installation/upgrade/2.3-to-2.4.html' for upgrading instructions. > ==> Alternatively, there is a dovecot23 (and pigeonhole23) package available. Given the fact that any dovecot 2.4 binary *will not* start with a <= 2.3 configuration file, it seems reasonable for us to publish an announcement to make users aware of this situation while also informing them about the alternate 2.3 packages we provide. News draft below. ----8<---- # dovecot >= 2.4 requires manual intervention 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](https://doc.dovecot.org/latest/installation/upgrade/2.3-to-2.4.html) 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 packages available in [extra]: - dovecot23 - pigeonhole23 - dovecot23-fts-elastic - dovecot23-fts-xapian The dovecot 2.3 release branch is going to [receive critical security fixes](https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/threa… from upstream until stated otherwise. ---->8---- [1] https://doc.dovecot.org/latest/installation/upgrade/2.3-to-2.4.html [2] https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/3P45L… Cheers -- Thore "foxxx0" Bödecker GPG ID: 0xEB763B4E9DB887A6 GPG FP: 051E AD6A 6155 389D 69DA 02E5 EB76 3B4E 9DB8 87A6

1 0