The openblas package prior to version 0.3.23-2 doesn't ship optimized
LAPACK routine and CBLAS/LAPACKE interfaces for compatibility. This
decision has been reverted now, and the ability to choose a different
default system BLAS/LAPACK implementation while keeping openblas
installed is now provided to allow future co-installation of BLIS,
ATLAS, etc.
The default BLAS implementation will be used for most packages like
NumPy or R. Please install "blas-openblas" and "blas64-openblas" to make
OpenBLAS the default BLAS implementation, just like the old behavior.
Unfortunately you will get errors on updating if you currently have
OpenBLAS installed as the default BLAS implementation:
error: failed to prepare transaction (could not satisfy dependencies)
:: installing openblas (0.3.23-2) breaks dependency 'blas' required by cblas
:: installing openblas (0.3.23-2) breaks dependency 'blas' required by
lapack
Please append your preferred default BLAS implementation to the regular
-Syu command line to get around it. For example:
pacman -Syu blas-openblas
or
pacman -Syu blas
We are proud to announce that the migration to Git packaging succeeded! 🥳
Thanks to everyone who has helped during the migration!
Package sources are now available on GitLab. Note that the bugtracker is still flyspray and that merge requests are not accepted as of now.
We intend to open the issue tracker and merge requests on the Gitlab package repos in the near future.
Mirrors are syncing again, but it may take a bit of time until your mirror of choice has caught up.
For users
Update your system and merge the pacman pacnew /etc/pacman.conf.pacnew file. This is …
This Friday morning (2023-05-19) the Git packaging migration will start until Sunday (2023-05-21). The Arch Linux packaging team will not be able to update packages in any of the repositories during this period.
Notification when the migration starts, and when it is completed, will be published on the [arch-dev-public] mailing list.
How does this impact Arch Linux users?
The [testing] repository will be split into [core-testing] and [extra-testing], the [staging] repository will be split into [core-staging] and [extra-staging]. The [community] repository will be merged into [extra] and will therefore be empty after the migration.
All affected repositories will …
On February 2nd, the base-devel package group has been replaced by a meta package of the same name.
If you installed the base-devel package group prior to this date, explicitly re-install it to get the new base-devel package installed on the system:
pacman -Syu base-devel
The php packages have been updated to the latest version 8.2. In
addition to this, a new set of php-legacy packages have been
introduced. These will follow the oldest but still actively supported
PHP branch. This enables users to install the latest version but also
introduces the option to use third party applications that might rely
on an older version. Both branches will be kept up to date following
our rolling release model. php and php-legacy can be installed at the
same time as the latter uses a -legacy suffix for its binaries and
configuration files.
In addition to this, …
