Bug#1085252: libgexiv2-2:amd64: libgexiv2.so.2.14.3 still links to libexiv2.so.27, but only libexiv2.so.28 is present

Marcos Dione mdione at grulic.org.ar
Thu Oct 17 10:29:38 BST 2024


Package: libgexiv2-2
Version: 0.14.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

    Last Sunday I updated my Debian Sid setup, which installed
libexiv2-28:amd64 and removed libexiv2-27:amd64 and upgraded
libgexiv2-2:amd64 from 0.14.3-1 to 0.14.3-1+b1:

[INSTALL] libexiv2-28:amd64 0.28.3+dfsg-2
[INSTALL] libexiv2-data:amd64 0.28.3+dfsg-2
[REMOVE (PURGE)] libexiv2-27:amd64 0.27.6-1+b1
[UPGRADE] libgexiv2-2:amd64 0.14.3-1 -> 0.14.3-1+b1

    The problem is that the latter is still linked to libexiv2-27:amd64, as seen below:

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.10.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgexiv2-2:amd64 depends on:
ii  libc6            2.40-3
pn  libexiv2-27      <none>
ii  libgcc-s1        14.2.0-6
ii  libglib2.0-0t64  2.82.1-1
ii  libstdc++6       14.2.0-6

libgexiv2-2:amd64 recommends no packages.

libgexiv2-2:amd64 suggests no packages.

-- no debconf information

$ ldd /lib/x86_64-linux-gnu/libgexiv2.so.2
        linux-vdso.so.1 (0x00007f3536cf9000)
        libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f3536c34000)
        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f3536ae6000)
        libexiv2.so.27 => not found
        libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007f35368f1000)
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f3536600000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f353651a000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f35368c2000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3536324000)
        libffi.so.8 => /lib/x86_64-linux-gnu/libffi.so.8 (0x00007f35368b5000)
        libatomic.so.1 => /lib/x86_64-linux-gnu/libatomic.so.1 (0x00007f35368ab000)
        libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007f3536289000)
        libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007f35368a2000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f3536883000)
        libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x00007f3536214000)
        libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f35361e4000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f3536cfb000)
        libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007f3536185000)

    Maybe this needs a recompilation?

    Cheers,

        -- Marcos Dione.



More information about the pkg-gnome-maintainers mailing list