- Arch-announce - lists.archlinux.org

[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

[arch-announce] zita-resampler 1.6.0-1 -> 2 update requires manual intervention
by Arch Linux: Recent news updates: Antonio Rojas 22 Feb '18

22 Feb '18

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. URL: https://www.archlinux.org/news/zita-resampler-160-1-2-update-requires-manua…

1 0

[arch-announce] The end of i686 support
by Arch Linux: Recent news updates: Bartłomiej Piotrowski 08 Nov '17

08 Nov '17

Following 9 months of [deprecation period][1], 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. For users unable to upgrade their hardware to x86_64, an alternative is a community maintained fork named [Arch Linux 32][2]. See their website for details on migrating existing installations. [1]: https://www.archlinux.org/news/phasing-out-i686-support/ [2]: https://archlinux32.org/ URL: https://www.archlinux.org/news/the-end-of-i686-support/

1 0

[arch-announce] Perl library path change
by Arch Linux: Recent news updates: Florian Pritz 02 Sep '17

02 Sep '17

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 to 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. URL: https://www.archlinux.org/news/perl-library-path-change/

1 0