Package: supermin
Version: 5.2.2-3
Severity: important
X-Debbugs-Cc: segfa...@riseup.net

After installing recent package updates, libguestfs fails to start guestfsd
inside a supermin appliance.

The error it fails with is:

    guestfsd: error while loading shared libraries: librpm.so.9: cannot open
shared object file: No such file or directory

The source of the problem seems to be that librpm9t64 is installed on my host.
That package does provide a librpm.so.9, but supermin doesn't copy it to the
appliance. The librpm9 package is also missing in the verbose output (printed
by -v -v) of supermin.

If I install librpm9 instead of librpm9t64, the librpm.so.9 is copied to the
appliance. When I do that, guestfsd fails with the next missing dependency,
libcurl.so.4, which is provided by libcurl4t64 on my host (so it seems to be
the same issue with the t64 version being ignored again).

I would have expected supermin to either use the libraries it finds on my host
or, if it notices that they are incompatible, that it fails with an error
instead of ignoring the dependencies.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.7-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages supermin depends on:
ii  apt                           2.7.13+b1
ii  cpio                          2.15+dfsg-1
ii  e2fsprogs                     1.47.0-2.3+b1
ii  libc6                         2.37-15.1
ii  libcom-err2t64 [libcom-err2]  1.47.0-2.3+b1
ii  libext2fs2t64 [libext2fs2]    1.47.0-2.3+b1

Versions of packages supermin recommends:
ii  linux-image-amd64  6.7.7-1

supermin suggests no packages.

-- no debconf information

Reply via email to