You've reached the website for Arch Linux 32, the community maintained continuation of 32-bit support for Arch Linux, a lightweight and flexible Linux® distribution that tries to Keep It Simple.
Currently we have official packages optimized for the i686 and pentium4 architectures. Also most(ly) non-graphical packages are available for i486, too. Have a look at the required cpu flags to decide which architecture is the right one for you. Most packages from Arch Linux's community-operated package repository are also compatible with Arch Linux 32.
Instructions for the transition from Arch Linux to Arch Linux 32 can be found here.
Installation media which boot on x86_64 and i686 can be found here.
Join us on #archlinux32 IRC channel on Freenode, check out our forums or subscribe to the mailing list to get your feet wet. Also glance through the Arch Wiki if you want to learn more about upstream Arch.
The astyle package prior to version 3.1-2 was missing a soname link. This has been fixed in 3.1-2, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If you get an error
astyle: /usr/lib/libastyle.so.3 exists in filesystem
when updating, use
pacman -Suy --overwrite usr/lib/libastyle.so.3
to perform the upgrade.
The tensorflow packages prior to version 1.14.0-5 were missing some soname links. This has been fixed in 1.14.0-5, so the upgrade will need to overwrite the untracked soname links created by ldconfig. If you get an errors like so
tensorflow: /usr/lib/libtensorflow.so.1 exists in filesystem
tensorflow: /usr/lib/libtensorflow_cc.so.1 exists in filesystem
tensorflow: /usr/lib/libtensorflow_framework.so.1 exists in filesystem
when updating, use
pacman -Suy --overwrite=usr/lib/libtensorflow.so.1,usr/lib/libtensorflow_cc.so.1,usr/lib/libtensorflow_framework.so.1
to perform the upgrade.
The libbloom package prior to version 1.6-2 was missing a soname link. This has been fixed in 1.6-2, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If you get an error
libbloom: /usr/lib/libbloom.so.1 exists in filesystem
when updating, use
pacman -Suy --overwrite usr/lib/libbloom.so.1
to perform the upgrade.
The update to mariadb 10.4.6-1 and later changes configuration layout as recommended by upstream.
The main configuration file moved from /etc/mysql/my.cnf (and its include directory /etc/mysql/my.cnf.d/) to /etc/my.cnf (and /etc/my.cnf.d/). Make sure to move your configuration.
Instantiated services (like mariadb@foo.service) are no longer configured in separate files (like /etc/mysql/myfoo.cnf). Instead move your configuration to configuration blocks with group suffix in main configuration file, one for each service. A block should look something like this:
[mysqld.foo]
datadir = /var/lib/mysql-foo
socket = /run/mysqld/mysqld-foo.sock
...
Like every mariadb feature update this requires the data directory to be updated. With the new configuration in place run:
systemctl restart mariadb.service && mariadb-upgrade -u root -p
| glibc 2.29-4.43 | i486 |
| wireguard-lts 0.0.20190905-1.0 | i686 |
| vulkan-headers 1:1.1.121-1.0 | pentium4 |
| wireguard-lts 0.0.20190905-1.0 | i486 |
| wireguard-lts 0.0.20190905-1.0 | pentium4 |
| linux-zen 5.2.11.zen1-1.2 | pentium4 |
| linux-zen-docs 5.2.11.zen1-1.2 | pentium4 |
| linux-zen 5.2.11.zen1-1.2 | i686 |
| linux-zen-docs 5.2.11.zen1-1.2 | i686 |
| python-openstackclient 3.19.0-1.1 | i486 |
| python-openstackclient 3.19.0-1.1 | i686 |
| python-openstackclient 3.19.0-1.1 | pentium4 |
| vhba-module 20190831-3.0 | pentium4 |
| wireguard-arch 0.0.20190905-3.0 | pentium4 |
| vhba-module-dkms 20190831-3.0 | pentium4 |