- Arch-announce - lists.archlinux.org

�� ?
by arch-announce＠archlinux.org 24 Oct '19

24 Oct '19

Вас интересуют базы данных?

1 0

[arch-announce] Required update to recent libarchive
by Arch Linux: Recent news updates: Christian Hesse 16 Oct '19

16 Oct '19

The compression algorithm `zstd` brings faster compression and decompression, while maintaining a compression ratio comparable with `xz`. This will speed up package installation with `pacman`, without further drawbacks. The imminent release of **pacman 5.2** brings build tools with support for compressing packages with `zstd`. To install these packages you need `libarchive` with support for `zstd`, which entered the repositories in September 2018. In order for `zstd` compressed packages to be distributed, we require all users to have updated to at least **libarchive 3.3.3-1**. You have had a year, so we expect you already did update. Hurry up if you have not. If you use custom scripts make sure these do not rely on hardcoded file extensions. The `zstd` package file extension will be `.pkg.tar.zst`. URL: https://www.archlinux.org/news/required-update-to-recent-libarchive/

1 0

[arch-announce] `base` group replaced by mandatory `base` package - manual intervention required
by Arch Linux: Recent news updates: Robin Broda 06 Oct '19

06 Oct '19

The `base` group has been replaced by a metapackage of the same name, we advise users to install this package (`pacman -Syu base`), as it is effectively mandatory from now on. Users requesting support are expected to be running a system with the base package. URL: https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-packag…

1 0

[arch-announce] astyle>=3.1-2 update requires manual intervention
by Arch Linux: Recent news updates: Antonio Rojas 26 Aug '19

26 Aug '19

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. URL: https://www.archlinux.org/news/astyle31-2-update-requires-manual-interventi…

1 0

[arch-announce] tensorflow>=1.14.0-5 update requires manual intervention
by Arch Linux: Recent news updates: Konstantin Gizdov 20 Aug '19

20 Aug '19

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. URL: https://www.archlinux.org/news/tensorflow1140-5-update-requires-manual-inte…

1 0

[arch-announce] libbloom>=1.6-2 update requires manual intervention
by Arch Linux: Recent news updates: Felix Yan 11 Jul '19

11 Jul '19

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. URL: https://www.archlinux.org/news/libbloom16-2-update-requires-manual-interven…

1 0

[arch-announce] mariadb 10.4.x update requires manual intervention
by Arch Linux: Recent news updates: Christian Hesse 27 Jun '19

27 Jun '19

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(a)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 URL: https://www.archlinux.org/news/mariadb-104x-update-requires-manual-interven…

1 0

[arch-announce] libutf8proc>=2.1.1-3 update requires manual intervention
by Arch Linux: Recent news updates: Antonio Rojas 14 Jul '18

14 Jul '18

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. URL: https://www.archlinux.org/news/libutf8proc211-3-update-requires-manual-inte…

1 0

[arch-announce] js52 52.7.3-2 upgrade requires intervention
by Arch Linux: Recent news updates: Jan Steffens 04 May '18

04 May '18

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. URL: https://www.archlinux.org/news/js52-5273-2-upgrade-requires-intervention/

1 0

[arch-announce] glibc 2.27-2 and pam 1.3.0-2 may require manual intervention
by Arch Linux: Recent news updates: Bartłomiej Piotrowski 20 Apr '18

20 Apr '18

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 `libnss_nis` package. There is no replacement for NIS+ in the official repositories. `pam 1.3.0-2` no longer ships pam_unix2 module and `pam_unix_*.so` compatibility symlinks. Before upgrading, review PAM configuration files in the `/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 any modifications. URL: https://www.archlinux.org/news/glibc-227-2-and-pam-130-2-may-require-manual…

1 0