April

Arch Linux in April 2023 # project management # We’ve create a GitLab Board [0\] to track all tasks related to project management and project leadership. This Board allows us to visualize the exact state of tasks using different lanes and labels, making it easier to keep track of ongoing progress. Additionally, tasks will receive comments and lane updates to reflect the latest developments. This is another step towards providing increased transparency, structure, and visibility for our staff and users alike.

https://monthly-reports.archlinux.page/2023/04/

#planetarch

Git migration announcement

This Friday morning (2023-05-19) the Git packaging migration will start until Sunday (2023-05-21). The Arch Linux packaging team will not be able to update packages in any of the repositories during this period.

Notification when the migration starts, and when it is completed, will be published on the [arch-dev-public] mailing list.

How does this impact Arch Linux users?

The [testing] repository will be split into [core-testing] and [extra-testing], the [staging] repository will be split into [core-staging] and [extra-staging]. The [community] repository will be merged into [extra] and will therefore be empty after the migration.

All affected repositories will be provided as empty repositories for a transition period after the migration. For regular users, this means that everything works as before.

Note: After the migration is done, users that have the testing repositories enabled need to include the new repositories ([core-testing] and [extra-testing] instead of [testing]) in their pacman.conf before updating their system.

Other changes:

* SVN access is discontinued and will dissappear.
* The svn2git mirror will no longer be updated.
* asp, which relies on the svn2git mirror, will stop working. It is replaced by pkgctl repo clone.

How does this impact Arch Linux tier 1 mirrors?

During the migration rsync and HTTP access will be shut down. We will send an email notification to arch-mirrors once everything has been finished.

How does this impact Arch Linux packagers?

Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.

https://archlinux.org/news/git-migration-announcement/

#news

Git migration completed

We are proud to announce that the migration to Git packaging succeeded! 🥳

Thanks to everyone who has helped during the migration!

Package sources are now available on GitLab. Note that the bugtracker is still flyspray and that merge requests are not accepted as of now. We intend to open the issue tracker and merge requests on the Gitlab package repos in the near future.

Mirrors are syncing again, but it may take a bit of time until your mirror of choice has caught up.

## For users

Update your system and merge the pacman pacnew /etc/pacman.conf.pacnew file. This is required as we have moved the [community] repository into [extra].

$ pacman -Syu "pacman>=6.0.2-7"

For users of the now deprecated asp tool, you will need to switch to pkgctl:

$ pacman -Syu "devtools>=1:1.0.0-1"
$ pkgctl repo clone linux

For some more detailed instructions on how to obtain PKGBUILDs see the corresponding wiki article.

## For packagers

Before starting, first uninstall devtools-git-poc and remove any repos from your filesystem that you cloned during the git proof-of-concept testing.

Make sure you have both, an updated devtools and pacman on your system:

$ pacman -Syu "devtools>=1:1.0.0-1" "pacman>=6.0.2-7"

Additionally clean up old chroots in /var/lib/archbuild/

$ rm -rf /var/lib/archbuild/
# or optionally, use the --clean option for pkgctl build *ONCE*
$ pkgctl build --clean

For instruction on how to use pkgctl, please take a look at the "How to be a packager" wiki article and also consult the man page of each subcommand for further information:

$ man pkgctl-build
$ man pkgctl-repo-clone

https://archlinux.org/news/git-migration-completed/

#news

OpenBLAS >= 0.3.23-2 update requires manual intervention

The openblas package prior to version 0.3.23-2 doesn't ship optimized LAPACK routine and CBLAS/LAPACKE interfaces for compatibility. This decision has been reverted now, and the ability to choose a different default system BLAS/LAPACK implementation while keeping openblas installed is now provided to allow future co-installation of BLIS, ATLAS, etc.

The default BLAS implementation will be used for most packages like NumPy or R. Please install "blas-openblas" and "blas64-openblas" to make OpenBLAS the default BLAS implementation, just like the old behavior.

Unfortunately you will get errors on updating if you currently have OpenBLAS installed as the default BLAS implementation:

error: failed to prepare transaction (could not satisfy dependencies) :: installing openblas (0.3.23-2) breaks dependency 'blas' required by cblas :: installing openblas (0.3.23-2) breaks dependency 'blas' required by lapack

Please append your preferred default BLAS implementation to the regular -Syu command line to get around it. For example:

pacman -Syu blas-openblas

or

pacman -Syu blas

https://archlinux.org/news/openblas-0323-2-update-requires-manual-intervention/

#news

TeX Live package reorganization

Starting from version 2023.66594-9, TeX Live packages have been reorganized to mirror upstream collections. Even though the new texlive-basic replaces the old texlive-core, many of the texlive-core contents (including language specific files) are now split between different packages. To find out which Arch package contains a specific CTAN package, you can use the tlmgr utility, eg.

$ tlmgr info euler | grep collection
collection:  collection-latexrecommended

which means the euler CTAN package is contained in texlive-latexrecommended. You may also use pacman -F to query for specific files.

A new metapackage texlive-meta is available to install all subpackages (except for language specific ones), and the new texlive-doc package provides the full documentation for offline use.

https://archlinux.org/news/tex-live-package-reorganization/

#news

budgie-desktop >= 10.7.2-6 update requires manual intervention

When upgrading from budgie-desktop 10.7.2-5 to 10.7.2-6, the package mutter43 must be replaced with magpie-wm, which currently depends on mutter. As mutter43 conflicts with mutter, manual intervention is required to complete the upgrade.

First remove mutter43, then immediately perform the upgrade. Do not relog or reboot between these steps.

pacman -Rdd mutter43

pacman -Syu

https://archlinux.org/news/budgie-desktop-1072-6-update-requires-manual-intervention/

#news

ansible-core >= 2.15.3-1 update may require manual intervention

As of ansible-core 2.15.3, upstream moved documentation and examples to a separate dedicated repository (see the related changelogs).
This means that, starting from version 2.15.3 the ansible-core package will stop shipping documentation and a default configuration example under /etc/ansible/ansible.cfg.

Regarding the documentation, it is available online: https://docs.ansible.com/
As for the configuration file, as explained in the wiki, a base config can be generated with the following command:

ansible-config init --disabled > ansible.cfg

After updating from ansible-core <= 2.15.2-1 to >= 2.15.3-1, everyone using a custom global Ansible configuration file stored under /etc/ansible/ansible.cfg will have their configuration saved as a pacsave file.
To restore it, run the following command:

mv /etc/ansible/ansible.cfg.pacsave /etc/ansible/ansible.cfg

https://archlinux.org/news/ansible-core-2153-1-update-may-require-manual-intervention/

#news

Changes to default password hashing algorithm and umask settings

With shadow >= 4.14.0, Arch Linux's default password hashing algorithm changed from SHA512 to yescrypt [1].

Furthermore, the umask [2] settings are now configured in /etc/login.defs instead of /etc/profile.

This should not require any manual intervention.

Reasons for Yescrypt

The password-based key derivation function (KDF) and password hashing scheme yescrypt has been chosen due to its adoption (readily available in libxcrypt, which is used by pam [3]) and its stronger resilience towards password cracking attempts over SHA512.

Although the winner of the Password Hashing Competition [4] has been argon2, this even more resilient algorithm is not yet available in libxcrypt [5][6].

Configuring yescrypt

The YESCRYPT_COST_FACTOR setting in /etc/login.defs is currently without effect, until pam implements reading its value [7]. If a YESCRYPT_COST_FACTOR higher (or lower) than the default (5) is needed, it can be set using the rounds option of the pam_unix [8] module (i.e. in /etc/pam.d/system-auth).

General list of changes

▪️yescrypt is used as default password hashing algorithm, instead of SHA512
▪️pam honors the chosen ENCRYPT_METHOD in /etc/login.defs and does not override the chosen method anymore
▪️changes in the filesystem (>= 2023.09.18) and pambase (>= 20230918) packages ensure, that umask is set centrally in /etc/login.defs instead of /etc/profile

https://archlinux.org/news/changes-to-default-password-hashing-algorithm-and-umask-settings/

#news

Store ssh keys inside the TPM: ssh-tpm-agent

After writing age-plugin-tpm a friend of mine at the hackerspace was super excited to finally have easy file encryption with TPM sealed keys, all without having to rely on gnupg. “This is great!” he said. “I wish I could have my SSH keys sealed in a TPM just as easily”. We should have left it at that. I shouldn’t have replied with a random assortment of facts like “I know google/go-tpm now”, or “but Go has a ssh-agent protocol implementation” followed-up with “Filippo has already implemented yubikey-agent, it can’t be that hard”.

https://linderud.dev/blog/store-ssh-keys-inside-the-tpm-ssh-tpm-agent/

#planetarch

September

Arch Linux in September 2023 # Staff # We would like to welcome Fabian Bornschein (fabiscafe) as part of the Arch Linux Package Maintainer team. Bug weekend # During the 1st to 3rd of September, we conducted a bug weekend with the aim of resolving old bugs and implementing proposed solutions. This effort not only reduced the backlog but also contributed to streamlining the upcoming bug tracker migration, resulting in the resolution of approximately 200 bugs.

https://monthly-reports.archlinux.page/2023/09/

#planetarch

Fully Automated Releases for Rust Projects

Here is how you can publish a Rust project with a single click of a button and automate everything.

https://blog.orhun.dev/automated-rust-releases/

#planetarch

Incoming changes in JDK / JRE 21 packages may require manual intervention

We are introducing a change in JDK/JRE packages of our distro. This is triggered from the way a JRE is build in modern versions of Java (>9). We are introducing this change in Java 21. To sum it up instead of having JDK and JRE packages coexist in the same system we will be making them conflict. The JDK variant package includes the runtime environment to execute Java applications so if one needs compilation and runtime of Java they need only the JDK package in the future. If, on the other hand, they need just runtime of Java then JRE (or jre-headless) will work. This will (potentially) require a manual user action during upgrade:

▪️ If you have both JDK and JRE installed you can manually install the JDK with pacman -Syu jdk-openjdk and this removes the JRE related packages.
▪️ If you have both JRE and JRE-headless you will need to choose one of them and install it manually since they would conflict each other now.
▪️ If you only have one of the JDK/JRE/JRE-headless pacman should resolve dependencies normally and no action is needed.

At the moment this is only valid for the upcoming JDK 21 release.

https://archlinux.org/news/incoming-changes-in-jdk-jre-21-packages-may-require-manual-intervention/

#news

Grants for Operating Systems

Over the past years I have written (unsuccessful) funding applications for free software projects, associated with the Arch Linux Operating System. This article is about my experiences with applying for numerous funds and my advice for people trying to get their work funded. TL;DR: Writing funding applications is extremely tedious and the selection process mostly intransparent and discouraging. Depending on what you apply for and who you apply with, you may never get funding due to other, additional factors. Read more… (8 min remaining to read)

https://sleepmap.de/2023/grants-for-operating-systems/

#planetarch

Operating System Bias in Next Generation Internet and NLnet

In Grants for Operating Systems I discussed my journey through the grant application writing business since beginning of last year. To keep things light and somewhat focused, I left out a topic, that I would like to write about in more detail in the following sections. It's about selection bias in grants provided by Next Generation Internet (NGI), that can be applied for directly or through NLnet. Read more… (11 min remaining to read)

https://sleepmap.de/2023/operating-system-bias-in-next-generation-internet-and-nlnet/

#planetarch

Bugtracker migration to GitLab completed

We are happy to announce that the migration of the bugtracker to GitLab is done! 🥳

Thanks to everyone who has helped during the migration!

This means the issue tracker and merge requests on the GitLab package repos are now enabled.

The old bugtracker will subsequently be closed down. For archiving reasons there will be a static copy so that links (for example the randomly picked Task #56716) are still stable, migrated bugs have a closing comment pointing to the new URL on GitLab.

Packaging bugs are now opened on the repo hosting the corresponding packaging sources, the "Add a new Bug" button on the package page on archlinux.org will automatically direct you to the correct place to open the issue. The workflow afterwards is mostly the same, first our Bug Wranglers will have a look at the issues and triage them, and then they will be handed over to the respective Package Maintainers to fix. A list of all issues can be found here.

If you do not have an account for GitLab already (which authenticates against our SSO service), please write us a mail with your desired username to accountsupport@archlinux.org as advised in the banner.

https://archlinux.org/news/bugtracker-migration-to-gitlab-completed/

#news

November

Arch Linux in November 2023 # Arch Summit 2023 # The Arch Summit took place in Hamburg, Germany, on November 4th and 5th, bringing together Arch Linux staff and invited guests. The summit provided an opportunity for the staff to connect, socialize, and delve into discussions regarding various aspects of our distro. A range of topics were explored including but not limited to infrastructure and mirror management, rebuilders for packages, signing enclave, mkinitcpio, packaging tooling improvements, and community building.

https://monthly-reports.archlinux.page/2023/11/

#planetarch

Reflecting on my 2023

I figured I’d write a post about this last year, maybe to crystalize thoughts I’ve been having, and to help figure some things out for the times ahead.

https://rubin55.org/blog/reflecting-on-my-2023/

#planetarch

Stream to chromecast with resolved, vlc and bash

Chromecast is one of those devices I just generally use a lot. They are small practical and enables me to stream video or music to my TV from multiple devices. But it also requires you to have a supported browser or video player. This is obviously a bit boring. There has been multiple command line chromecast streamers through the years. But their ffmpeg usage has been shoddy at best with no hardware decoding support and usually quite bad implementations.

https://linderud.dev/blog/stream-to-chromecast-with-resolved-vlc-and-bash/

#planetarch

Plans and ideas for 2024

A follow-up to my reflections on 2023, my plans and ideas for 2024.

https://rubin55.org/blog/plans-and-ideas-for-2024/

#planetarch

Making dbus-broker our default D-Bus daemon

We are making dbus-broker our default implementation of D-Bus, for improved performance, reliability and integration with systemd.

For the foreseeable future we will still support the use of dbus-daemon, the previous implementation. Pacman will ask you whether to install dbus-broker-units or dbus-daemon-units. We recommend picking the default.

For a more detailed rationale, please see our RFC 25.

https://archlinux.org/news/making-dbus-broker-our-default-d-bus-daemon/

#news

Why stdout is faster than stderr?

I recently realized stdout is much faster than stderr for Rust. Here are my findings after diving deep into this rabbit hole.

https://blog.orhun.dev/stdout-vs-stderr/

#planetarch