libguestfs looks for README.fixed https://github.com/libguestfs/libguestfs/blob/8e0ae6560e6629f6e435147557f8e0e42ec7986c/src/appliance.c#L196-202 to determine if an appliance is a fixed one.
1) Please post your `emerge --info app-emulation/libguestfs-appliance' output in a comment. 2) Please explain the problem, along with command output and anything else particular to this bug report.
Created attachment 393248 [details, diff] Fix. % echo $LIBGUESTFS_PATH /usr/share/guestfs/appliance/ % virt-list-filesystems -a /dev/null cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/share/guestfs/appliance/) at /usr/bin/virt-list-filesystems line 163. % sudo touch $LIBGUESTFS_PATH/README.fixed % virt-list-filesystems -a /dev/null /dev/sda % eix libguestfs [I] app-emulation/libguestfs Available versions: (~)1.26.1(0/1.26) (~)1.28.3(0/1.28) (~)1.28.5(0/1.28) {bash-completion debug doc erlang +fuse inspect-icons introspection lua (+)ocaml +perl ruby selinux static-libs systemtap test} Installed versions: 1.28.5(16:09:33 12/31/14)(bash-completion fuse lua ocaml perl -debug -doc -erlang -inspect-icons -introspection -ruby -selinux -static-libs -systemtap -test) Homepage: http://libguestfs.org/ Description: Tools for accessing, inspect and modifying virtual machine (VM) disk images [I] app-emulation/libguestfs-appliance Available versions: (~)1.26.0-r1 (~)1.28.1 Installed versions: 1.28.1(11:43:13 12/31/14) Homepage: http://libguestfs.org/ Description: VM appliance disk image used in libguestfs package Found 2 matches.
(In reply to Jeroen Roovers from comment #1) > 1) Please post your `emerge --info app-emulation/libguestfs-appliance' > output in a comment.
> 1) Please post your `emerge --info app-emulation/libguestfs-appliance' > output in a comment. I'm not sure of the point of this. There is already - reproduction instructions - a link to the upstream code that is relevant to the bug. - a patch.
I'm sure of it.
*** Bug 537082 has been marked as a duplicate of this bug. ***
Rather than what is suggested here I recommend this patch: https://bugs.gentoo.org/attachment.cgi?id=394356 that makes libguestfs ignore the README.fixed requirement. Also see https://bugzilla.redhat.com/show_bug.cgi?id=1183780 for the redhat bug for this. Additional details are in the resolved duplicated bug #537082
Is there any point in diverging from upstream? If a user builds their own appliance, it seems like the changed the detection logic will mis-detect the type of appliance. If the point is not having duplicate documentation or something, the README.fixed in the appliance directory could just be a file explaning that it needs to be there for proper detection, or a symlink, or a empty file.
Another option would be to have some file that explicitly describes the appliance, but that seems like something that is best done upstream, and it seems like upstream is reluctant to add another appliance format (they already have 3). From Richard W.M. Jones (https://bugzilla.redhat.com/show_bug.cgi?id=1183780#c4) > Or we could work on something upstream (not sure exactly what -- I > don't want to introduce yet another "type" of appliance, we have > too many of them already).
Well, sorry for the delay. I was poked by user today and finally fixed it. Now README.fixed is installed. Enjoy!