Arch Linux 32-bit Planet - Latest News

pacman -Suy results in "invalid or corrupted package" (%2024/%11/%28 %07:%Nov)Follow the procedure described in FS32#365 .

xz backdoor in Archlinux32 (%2024/%03/%31 %15:%Mar)The xz versions 5.6.0 and 5.6.1 should be considered harmful in Archlinux32,especially the last versions installed:xz-5.6.1-1.0-pentium4xz-5.6.1-1.0-i686xz-5.6.0-1.0-i486Make sure that the following versions or newer are installed:xz-5.6.1-2.0-pentium4xz-5.6.1-2.0-i686xz-5.6.1-3.0-i486

Shim packages required for 'icu' (%2023/%07/%28 %05:%Jul)If you see messages like::: installing icu (73.2-1.0) breaks dependency 'libicuuc.so=72-32' required by XXXXyou can work around this by forcefully uninstalling 'icu' (the 72 version) and installing 'icu'(the 73 version) and 'icu72' (the 72 shared libraries) in parallel:pacman -Rd --nodeps icu pacman -Syy icu icu72 pacman -SyyuSadly we have big issues rebuilding packages at the moment, so this situation might persist for a while..

New package signing keys (%2023/%06/%24 %07:%Jun)downloading required keys... :: Import PGP key E4D41569196B1160, "TasosSah &lt;arch32@tasossah.com&gt;"? [Y/n] :: File /var/cache/pacman/pkg/libxcrypt-4.4.35-1.0-pentium4.pkg.tar.zst is corrupted (invalid or corrupte Do you want to delete it? [Y/n] Use pacman -Syy archlinux32-keyring first before you do a full update with pacman -Syyu.

Git Migration (%2023/%05/%23 %14:%May)status update: The migration of the git sources is done and seems successful. However, now the build machines need to catch up and build all packages. As you might imagine, this will take some time.

upstream git migration (%2023/%05/%16 %13:%May)Upstream ArchLinux announced that they will migrate their git repositories.This will affect ArchLinux32, because we heavily rely on how the repositories are structured and how packages are updated.We are currently in the process of evaluating, which changes we need to do, and how long this may take.In any case, starting with the migration on 2023-05-19 morning, we will not be able to update packages anymore.We hope to resume operation within a few days, but please be patient if it takes longer.Auxillary tools, like asp32 will also break, but as upstream discontinues asp, we will likely move to a different tool, too.

In case of key problems (%2023/%04/%29 %05:%Apr)Because of expired keys starting this year there can still be installations out there which are not easy to updatesecurely.Try the following steps:pacman-key --refresh pacman -S archlinux32-keyringIf this doesn't help, try importing the signing keys from our keyservers (which you have to trust in this case) manually:pacman-key --init curl -Ss 'https://archlinux32.org/keys.php?k=5FDCA472AB93292BC678FD59255A76DB9A12601A' | gpg --homedir /etc/pacman.d/gnupg/ --import curl -Ss 'https://archlinux32.org/keys.php?k=16194A82231E9EF823562181C8E8F5A0AF9BA7E7' | gpg --homedir /etc/pacman.d/gnupg/ --import pacman-key --populate pacman-key --refresh pacman -S archlinux32-keyringMore details can be found https://wiki.archlinux.org/title/Pacman/Package_signing.

Dropping Haskell (%2023/%03/%31 %07:%Mar)After years of not being able to build a consistent set of Haskell libraries and more recently not being able to bootstrap the ghc compiler on 32-bit, Archlinux32 drops Haskell and all dependent packages. You can find a complete list of blacklisted packages and the rationals behind blacklisting on https://archlinux32.org/buildmaster/blacklist.php.

OpenSSL 3.0.7 (%2022/%11/%17 %08:%Nov)OpenSSL 3.0.7 is now the current version of OpenSSL. If you experience problems like:binary: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory binary: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directoryyou can temporarily install `openssl-1.1` to fix the issue like so:pacman -S openssl-1.1This is especially the case for everything comingfrom third party repos or the AUR.

systemd 251.2 breaks logins (%2022/%10/%30 %08:%Oct)If you see this message after upgrading and booting:Assertion 'close_nointr(fd) != -EBADF' failed at src/basic/fd-util.c:76, function safe_close(). Aborting.Just boot into single user mode and comment out the following sections in `/etc/pam,.d/system-login`:#-session optional pam_systemd.soand in /etc/pam.d/system-auth:#-auth [success=2 default=ignore] pam_systemd_home.so #-account [success=1 default=ignore] pam_systemd_home.so #-password [success=1 default=ignore] pam_systemd_home.so #-session optional pam_systemd_home.so

CA certificates file is empty (%2022/%05/%12 %09:%May)This affects pacman updates from HTTPS mirrors and basically any other SSL request.Update to the newest p11-kit package (0.24.1-1.0) and excute `update-ca-trust` as root(if your CA certificate file `/etc/ca-certificates/extracted/tls-ca-bundle.pem` is empty).

ISO 2022.02.01 available (%2022/%02/%01 %20:%Feb)A new ISO is available: archlinux32-2022.02.01-i686.iso.It has been updated to support text-to-speech, copy-to-ram, archinstall, new keyring, smaller size, etc.Archinstall has some issues currently:- zram-support is not available, just choose *No* when asked (otherwise installation of packages with pacstrap will fail)- installation of additional packages breaks, just say "Enter" if asked and install the packages afterwards with pacman in the chrooted post installation environment- choose a desktop which might a) work on your hardware b) which is not currently broken (Mate for instance is known to work)You can of course always use the more "traditional" installation procedure, if you prefer..

error while loading shared libraries: libicui18n.so.68 (%2022/%01/%07 %22:%Jan)If you see software failing with:error while loading shared libraries: libicui18n.so.69: cannot open shared object file: No such file or directoryThis means that the software (or a library) has not been rebuilt against newest icu (70).As a temporary workaround you can install the old libs with:pacman -S icu69The same applies for icu68 and icu67.If you have software that does this, please also raise a bug or bother the devs on irc so that in the future we can fix it properly.

nss 3.73 crashes firefox (%2022/%01/%07 %14:%Jan)Due to a non-working signing of libraries nss-3.73 has been built without signed shared libraries, causing firefoxto simply crash. This is fixed in nss-3.74-1.1 now.

Warning about upgrading to zstd 1.5.1 (%2022/%01/%07 %11:%Jan)If using zstd 1.5.1 you end up with an unbootable system (dbus doesn't start, all systemd subservices fail to start).This is fixed in zstd-1.5.1-2.1.