From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60656) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YgF4W-0008UD-JJ for qemu-devel@nongnu.org; Thu, 09 Apr 2015 12:12:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YgF4S-0008Tm-Fg for qemu-devel@nongnu.org; Thu, 09 Apr 2015 12:12:52 -0400 Received: from cantor2.suse.de ([195.135.220.15]:46602 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YgF4S-0008Tg-AD for qemu-devel@nongnu.org; Thu, 09 Apr 2015 12:12:48 -0400 Message-ID: <5526A4F6.1040300@suse.de> Date: Thu, 09 Apr 2015 18:12:38 +0200 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="50miGIDjrsKaNbglUjBM3R9wg8G0VBCAG" Subject: [Qemu-devel] glusterfs-api.pc versioning breaks QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Niels de Vos , gluster-devel@gluster.org Cc: Kevin Wolf , Peter Maydell , Jeff Cody , qemu-devel , Stefan Hajnoczi , Raghavendra Bhat , Kaleb KEITHLEY , Lalatendu Mohanty , p.drouand@gmail.com This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --50miGIDjrsKaNbglUjBM3R9wg8G0VBCAG Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 >=3D 3 What our configure is doing is pkg-config --atleast-version=3D3 glusterfs-api on success followed by pkg-config --atleast-version=3D5 glusterfs-api and pkg-config --atleast-version=3D6 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 --=20 SUSE Linux GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Felix Imend=C3=B6rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,= Graham Norton; HRB 21284 (AG N=C3=BCrnberg) --50miGIDjrsKaNbglUjBM3R9wg8G0VBCAG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJVJqT8AAoJEPou0S0+fgE/d9oP/inqUwsBS4lIeilxiBtSKouz b3Q1RJzv93MkNdIbkLYTzk6DhWWdrf8qyUgj4XOfyy3EBdI//gNyF6wpewTCwdB3 8LPZibizA2r8oKBCqPTbDo1m0exkkIVUkcQqrIkpKa8+DQlijFUc/erra8Nvg/hp tWnWJ6qa8q+wuloE1x2AR3qpTAXZ4c6m9ibL11gzpeEZEFeFhL4f3wjMhahBMN5M 5TzGOUQZPJwmevr+6DE/n5W9JBzhNhE1q3c0dvYHKPIIxNnMcVZhXA9h52+1v6Ny 9WAtDEdyT+NmcLL8NF5v5hQUMm0dTH1VLwWImQB8bqQfJz16jK+JpGy0vSTQC5u5 qWH7vOI5tJcH2IacD+CTRZMuiqT0hVHooc74daNHgWpRQFDgMwf7Pxwf7oXXblBp EXsg+Swi/wPqHtn6F+j9KTlVls1IUEtndKQU1F6vYVyKADd6oP+1i/9wqce9T/A1 rLslB26uWEstutp1fIje0idP1ME52rL7UP3cxpgXpEmI5KTPNa8y0ZdymLzUG6cR BGikJ6dhwD5fScCiUA5Io+KA2MeAIST714DL16oQxxVblj1BTr+eTtF1PWc6i1IY 6NuMHcB/Ke7zZU+k0ygMo0D/CA125JL873oiTmZp+oE3+XVY4KdT0UloC38Oa3b2 mxtFcHfI2oxwuVX1hrbi =vmdh -----END PGP SIGNATURE----- --50miGIDjrsKaNbglUjBM3R9wg8G0VBCAG--