Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#45819 - [qemu] Think glusterfs needs to be a depends
Attached to Project:
Arch Linux
Opened by James Harvey (jamespharvey20) - Wednesday, 29 July 2015, 00:07 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 03 August 2015, 22:09 GMT
Opened by James Harvey (jamespharvey20) - Wednesday, 29 July 2015, 00:07 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 03 August 2015, 22:09 GMT
|
DetailsPKGBUILD build() calls configure with --enable-glusterfs
Pretty sure this makes the package glusterfs a depends. Without it, if I try creating a virtual machine, I get: "internal error: process exited while connecting to monitor: Failed to open module: libgfapi.so.0: cannot open shared object file: No such file or directory". That is while not using anything glusterfs related, attempting to use pure LVM storage. It's still expecting to be able to load the shared library. Also, tried building this in a clean chroot to check namcap output to see if any others might need to be a depends rather than makedepends or optdepends, but I'm running into: ===== ERROR: User requested feature spice configure was not able to find it. Install spice-server(>=0.12.0) and spice-protocol(>=0.12.3) devel ===== spice and spice-protocol are installed in the cleanchroot. /usr/lib/pkgconfig/spice-server.pc exists. Even exporting PKG_CONFIG_PATH=/usr/lib/pkgconfig doesn't get configure running for me. |
Closed by Sébastien Luttringer (seblu)
Monday, 03 August 2015, 22:09 GMT
Reason for closing: Fixed
Additional comments about closing: qemu 2.3.0-7
Monday, 03 August 2015, 22:09 GMT
Reason for closing: Fixed
Additional comments about closing: qemu 2.3.0-7
Failed to open module: libgfapi.so.0: cannot open shared object file: No such file or directory
that does not prevent the VM to run, but it's still annoying.
Installing the glusterfs package removes the issue.
/usr/lib/qemu/block-gluster.so:
libgfapi.so.0 => not found
/usr/lib/qemu/block-rbd.so:
librbd.so.1 => not found
librados.so.2 => not found
It adds more complexity for the packager but avoids having to pull a huge pile of unnecessary dependencies for most users.
Failed to open module: libiscsi.so.4: cannot open shared object file: No such file or directory
Failed to open module: librbd.so.1: cannot open shared object file: No such file or directory
Failed to open module: libgfapi.so.0: cannot open shared object file: No such file or directory
Even that message is useless, is there any issue around there?
19:19:27 < pm215> the module should be in a package which depends on the various external libraries it links against
...
19:20:39 < pm215> ok, so qemu is correct, and whatever is failing to install librbd.so is the thing that needs fixing
Debian has a qemu-block-extra package for curl, iscsi, rbd and ssh: https://packages.debian.org/sid/qemu-block-extra
Maybe that is an approach to follow? It could be further split into a qemu-block-{curl,iscsi,rbd,ssh} package, hmm.
(29/29) upgrading qemu
New optional dependencies for qemu
qemu-block-gluster: glusterfs block support
qemu-block-iscsi: iSCSI block support
qemu-block-rbd: RDB block support
samba: SMB/CIFS server support [installed]
Seems to work otherwise (package dependencies exist, did not verify its contents though).