Hello, Testing QEMU v2.3.0-rc2, I have run into QEMU's glusterfs support being broken on openSUSE Tumbleweed, resulting in its configure complaining:
[ 76s] ERROR: User requested feature GlusterFS backend support [ 76s] configure was not able to find it. [ 76s] Install glusterfs-api devel >= 3 What our configure is doing is pkg-config --atleast-version=3 glusterfs-api on success followed by pkg-config --atleast-version=5 glusterfs-api and pkg-config --atleast-version=6 glusterfs-api Here's a short overview of the glusterfs-api.pc versions: release-3.4: "Version: 4" v3.5.0..v3.5.3: "Version: 6" v3.5.4beta1 and release-3.5: "Version: 4.${PACKAGE_VERSION}" v3.6.0: "Version: 7.0.0" v3.6.1: "Version: 0.0.0" v3.6.2..v3.6.3beta2 and release-3.6: "Version: 4.${PACKAGE_VERSION}" So, both 3.5 and 3.6 series have gone backwards in their version compared to released versions and are thus not backwards-compatible, unlike what the commit message claims. openSUSE 13.1 and 13.2 and reportedly Fedora 21 are still at versions with "Version: 6", so not yet affected. openSUSE Tumbleweed is still at v3.6.1 (with 3 > 0.0.0), but even once I get it updated to v3.6.2 the checks for versions 5 and 6 would still fail, disabling features. Naively I would consider versions jumping backwards a bug in glusterfs, so I wonder why you chose 4.* and not 6.* and 7.* respectively. How do you expect this to be handled by packages such as QEMU? Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg)
signature.asc
Description: OpenPGP digital signature