With the release of mkinitcpio v38, several hooks previously provided by Arch packages have been
moved to the mkinitcpio upstream project. The hooks are: systemd, udev, encrypt,
sd-encrypt, lvm2 and mdadm_udev.
To ensure no breakage of users' setup occurs, temporary
conflicts have been introduced into the respective packages to prevent installing packages
that are no longer compatible.
The following packages needs to be upgraded together:
- mkinitcpio 38-3
- systemd 255.4-2
- lvm2 2.03.23-3
- mdadm 4.3-2
- cryptsetup 2.7.0-3
Please note that the mkinitcpio
flag --microcode
, and the microcode
option in the preset files, has been deprecated in favour of
a new microcode
hook. This also allows you to drop the microcode initrd
lines from your boot configuration as they are now packed together with the main initramfs image.
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.
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.
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 -Sy jdk-openjdk && pacman -Su
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.