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
pacman.
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.
The asp tool, available in [extra], provides similar functionality to
abs. 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.
While the extra/abs package has been already dropped, the rsync
endpoint ...
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 ...
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 ...
