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/my.cnf.d/). Make sure to move your configuration.
Instantiated services (like
firstname.lastname@example.org) 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
The libutf8proc package prior to version 2.1.1-3 had an incorrect soname link. This has been fixed in 2.1.1-3, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If you get an error
libutf8proc: /usr/lib/libutf8proc.so.2 exists in filesystem
when updating, use
pacman -Suy --overwrite usr/lib/libutf8proc.so.2
to perform the upgrade.
Due to the SONAME of
/usr/lib/libmozjs-52.so not matching its file name, ldconfig created an untracked file
/usr/lib/libmozjs-52.so.0. This is now fixed and both files are present in the package.
To pass the upgrade, remove
/usr/lib/libmozjs-52.so.0 prior to upgrading.
The new version of glibc removes support for NIS and NIS+. The default
/etc/nsswitch.conf file provided by
filesystem package already
reflects this change. Please make sure to merge pacnew file if it exists
prior to upgrade.
NIS functionality can still be enabled by installing
package. There is no replacement for NIS+ in the official repositories.
pam 1.3.0-2 no longer ships pam_unix2 module and
compatibility symlinks. Before upgrading, review PAM configuration files
/etc/pam.d directory and replace removed modules with
pam_unix.so. Users of pam_unix2 should also reset their passwords
after such change. Defaults provided by
pambase package do not need
The zita-resampler 1.6.0-1 package was missing a library symlink that has been readded in 1.6.0-2. If you installed 1.6.0-1, ldconfig would have created this symlink at install time, and it will conflict with the one included in 1.6.0-2. In that case, remove /usr/lib/libzita-resampler.so.1 manually before updating.
Following 9 months of deprecation period, support for the i686 architecture effectively ends today. By the end of November, i686 packages will be removed from our mirrors and later from the packages archive. The [multilib] repository is not affected.
For users unable to upgrade their hardware to x86_64, an alternative is a community maintained fork named Arch Linux 32. See their website for details on migrating existing installations.
The perl package now uses a versioned path for compiled modules. This means that modules built for a non-matching perl version will not be loaded any more and must be rebuilt.
A pacman hook warns about affected modules during the upgrade by showing output like this:
WARNING: '/usr/lib/perl5/vendor_perl' contains data from at least 143 packages which will NOT be used by the installed perl interpreter. -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/vendor_perl'
You must rebuild all affected packages against the new perl package before you can use them again. The change also affects modules installed directly via CPAN. Rebuilding will also be necessary again with future major perl updates like 5.28 and 5.30.
Please note that rebuilding was already required for major updates prior to this change, however now perl will no longer try to load the modules and then fail in strange ways.
If the build system of some software does not detect the change automatically,
you can use
perl -V:vendorarch in your PKGBUILD to query perl for the
correct path. There is also
sitearch for software that is not packaged with
Due to high maintenance cost of scripts related to the Arch Build
System, we have decided to deprecate the
abs tool and thus rsync
as a way of obtaining PKGBUILDs.
asp tool, available in [extra], provides similar functionality to
asp export pkgname can be used as direct alternative; more
information about its usage can be found in the documentation.
Additionally Subversion sparse checkouts, as described here, can
be used to achieve a similar effect. For fetching all PKGBUILDs, the
best way is cloning the svntogit mirrors.
extra/abs package has been already dropped, the rsync
endpoint (rsync://rsync.archlinux.org/abs) will be disabled by the end
of the month.
The upgrade to ca-certificates-utils 20170307-1 requires manual intervention because a symlink which used to be generated post-install has been moved into the package proper.
As deleting the symlink may leave you unable to download packages, perform this upgrade in three steps:
# pacman -Syuw # download packages # rm /etc/ssl/certs/ca-certificates.crt # remove conflicting file # pacman -Su # perform upgrade
mesa-17.0.0-3 can now be installed side-by-side with
nvidia-378.13 driver without any libgl/libglx hacks, and with the help of Fedora and upstream xorg-server patches.
First step was to remove the libglx symlinks with xorg-server-1.19.1-3 and associated mesa/nvidia drivers through the removal of various libgl packages. It was a tough moment because it was breaking optimus system,
xorg-server configuration needs manual updating.
The second step is now here, with an updated 10-nvidia-drm-outputclass.conf file that should help to have an "out-of-the-box" working
xorg-server experience with optimus system.
Due to the decreasing popularity of i686 among the developers and the community, we have decided to phase out the support of this architecture.
The decision means that February ISO will be the last that allows to install 32 bit Arch Linux. The next 9 months are deprecation period, during which i686 will be still receiving upgraded packages. Starting from November 2017, packaging and repository tools will no longer require that from maintainers, effectively making i686 unsupported.
However, as there is still some interest in keeping i686 alive, we would like to encourage the community to make it happen with our guidance. The arch-ports mailing list and #archlinux-ports IRC channel on Freenode will be used for further coordination.
The [multilib] repository will not be affected by this change.