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
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
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
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.
Please test this extensively and post ...