FS#42835 - [pinentry] links libg{t,d}k-x11-2.0.so.0, libpango-1.0.so.0
Attached to Project:
Arch Linux
Opened by Zack Buhman (buhman) - Wednesday, 19 November 2014, 03:01 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 13 May 2015, 20:55 GMT
Opened by Zack Buhman (buhman) - Wednesday, 19 November 2014, 03:01 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 13 May 2015, 20:55 GMT
|
Details
Description:
# ldd /usr/bin/pinentry linux-vdso.so.1 (0x00007fff667fe000) libcap.so.2 => /usr/lib/libcap.so.2 (0x00007f4e5230f000) libgtk-x11-2.0.so.0 => not found libgdk-x11-2.0.so.0 => not found libpango-1.0.so.0 => not found libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f4e520be000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f4e51db0000) libncursesw.so.5 => /usr/lib/libncursesw.so.5 (0x00007f4e51b4b000) libc.so.6 => /usr/lib/libc.so.6 (0x00007f4e517a8000) libattr.so.1 => /usr/lib/libattr.so.1 (0x00007f4e515a3000) libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f4e51334000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f4e51118000) libffi.so.6 => /usr/lib/libffi.so.6 (0x00007f4e50f0f000) /lib64/ld-linux-x86-64.so.2 (0x00007f4e52513000) Looks like either a dirty build, or missing depends. Thanks. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 13 May 2015, 20:55 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#28883
Wednesday, 13 May 2015, 20:55 GMT
Reason for closing: Duplicate
Additional comments about closing:
0) have testing enabled
1) pacstrap /mnt base
2) arch-chroot /mnt pinentry
2. Please don't use ldd, since it's recursive. objdump or readelf are better options.
3. gtk2 is already an optional dependency. The "pinentry" symlink is just pointing to pinentry-gtk-2 instead of pinentry-ncurses. This looks to be the case in 0.8.4-1, the current version in core as well. So yes, either the deps should be changed or the symlink should be changed.
$ chroot /mnt pacman -Q pinentry
pinentry 0.9.0-1
$ chroot /mnt objdump -p /usr/bin/pinentry
[objdump.txt]
> This looks to be the case in 0.8.4-1
Indeed. This also affects [core]/0.8.4, I just never noticed this until
FS#42762.