FS#61414 - [libidn2] version 2.1.0 breaks many packages

Attached to Project: Arch Linux
Opened by Brian BIdulock (bidulock) - Tuesday, 15 January 2019, 17:46 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 15 January 2019, 17:55 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No



libidn2 2.1.0 replaces /usr/lib/libidn2.so.0 with /usr/lib/libidn2.so.4

After a recent update, binaries remain linked against /usr/lib/libidn2.so.0

3 packages in core (gnupg, openvpn, pacman)
48 packages in extra
32 packages in community

Additional info:
* package version(s)
* config and/or log files etc.

Steps to reproduce:

perform ldd check on /usr/bin/* with check for libidn2.so.0
package list attached
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 15 January 2019, 17:55 GMT
Reason for closing:  Not a bug
Additional comments about closing:  repo packages have been rebuilt
Comment by Doug Newgard (Scimmia) - Tuesday, 15 January 2019, 17:54 GMT
None of the core packages you listed are linked to libidn2 at all. Forget ldd, use lddtree to see where the real problem is.
Comment by Santiago Torres (sangy) - Tuesday, 15 January 2019, 17:54 GMT
This seems mostly due to a partial upgrade, the latest version of these packages do link against libidn2.so.4. E.g., pacman:

santiago at ~ ✔ ldd /usr/bin/pacman
linux-vdso.so.1 (0x00007fffbdbf1000)
libnghttp2.so.14 => /usr/lib/libnghttp2.so.14 (0x00007f7deb612000)
libidn2.so.4 => /usr/lib/libidn2.so.4 (0x00007f7deb5f3000)