----- Original Message ----- | From: "Niels de Vos" <ndevos@xxxxxxxxxx> | To: "Humble Devassy Chirammal" <humble.devassy@xxxxxxxxx> | Cc: "Anders Blomdell" <anders.blomdell@xxxxxxxxxxxxxx>, "Gluster-users@xxxxxxxxxxx List" <gluster-users@xxxxxxxxxxx>, | "Gluster Devel" <gluster-devel@xxxxxxxxxxx>, "Humble Chirammal" <hchiramm@xxxxxxxxxx> | Sent: Wednesday, October 29, 2014 1:52:35 PM | Subject: Re: [Gluster-users] Dependency issue while installing glusterfs-3.6beta with vdsm | | On Wed, Oct 29, 2014 at 09:26:36AM +0530, Humble Devassy Chirammal wrote: | > Rebuilding related packages looks to be a solution , however it may not be | > possible for each and every release builds of GlusterFS. lets discuss it in | > community meeting and act. | | No, these rebuilds are only needed for major releases. The SONAME for | libgfapi is not supposed to change in a stable release. That means that | the next rebuild would potentially be needed when glusterfs-3.7 gets | released. | Not really. afaict, the SONAME jump can happen if there is a new api exposed via libgfapi which can happen even in same release version of GlusterFS. As a second thought, What happens if qemu or dependent packages released a new version in between ? Dont we need to rebuild ? Also, we need to build these related packages for f19, 20 and 21. --Humble | | > | > | > On Wed, Oct 29, 2014 at 1:03 AM, Niels de Vos <ndevos@xxxxxxxxxx> wrote: | > | > > On Tue, Oct 28, 2014 at 05:52:38PM +0100, Anders Blomdell wrote: | > > > On 2014-10-28 17:30, Niels de Vos wrote: | > > > > On Tue, Oct 28, 2014 at 08:42:00AM -0400, Kaleb S. KEITHLEY wrote: | > > > >> On 10/28/2014 07:48 AM, Darshan Narayana Murthy wrote: | > > > >>> Hi, | > > > >>> Installation of glusterfs-3.6beta with vdsm | > > (vdsm-4.14.8.1-0.fc19.x86_64) fails on | > > > >>> f19 & f20 because of dependency issues with qemu packages. | > > > >>> | > > > >>> I installed vdsm-4.14.8.1-0.fc19.x86_64 which installs | > > glusterfs-3.5.2-1.fc19.x86_64 | > > > >>> as dependency. Now when I try to update glusterfs by downloading | > > rpms from : | > > > >>> | > > http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.6.0beta3/Fedora/fedora-19/ | > > > >>> It fails with following error: | > > > >>> | > > > >>> Error: Package: 2:qemu-system-lm32-1.4.2-15.fc19.x86_64 (@updates) | > > > >>> Requires: libgfapi.so.0()(64bit) | > > > >>> Removing: glusterfs-api-3.5.2-1.fc19.x86_64 (@updates) | > > > >>> libgfapi.so.0()(64bit) | > > > >>> Updated By: glusterfs-api-3.6.0-0.5.beta3.fc19.x86_64 | > > (/glusterfs-api-3.6.0-0.5.beta3.fc19.x86_64) | > > > >>> ~libgfapi.so.7()(64bit) | > > > >>> Available: glusterfs-api-3.4.0-0.5.beta2.fc19.x86_64 | > > (fedora) | > > > >>> libgfapi.so.0()(64bit) | > > > >>> | > > > >>> Full output at: http://ur1.ca/ikvk8 | > > > >>> | > > > >>> For having snapshot and geo-rep management through ovirt, we | > > need glusterfs-3.6 to be | > > > >>> installed with vdsm, which is currently failing. | > > > >>> | > > > >>> Can you please provide your suggestions to resolve this issue. | > > > >> | > > > >> Hi, | > > > >> | > > > >> Starting in 3.6 we have bumped the SO_VERSION of libgfapi. | > > > >> | > > > >> You need to install glusterfs-api-devel-3.6.0... first and build | > > > >> vdsm. | > > > >> | > > > >> But.... we are (or were) not planning to release glusterfs-3.6.0 on | > > f19 and | > > > >> f20... | > > > >> | > > > >> Off hand I don't believe there's anything in glusterfs-api-3.6.0 | > > > >> that | > > vdsm | > > > >> needs. vdsm with glusterfs-3.5.x on f19 and f20 should be okay. | > > > >> | > > > >> Is there something new in vdsm-4-14 that really needs glusterfs-3.6? | > > If so | > > > >> we can revisit whether we release 3.6 to fedora 19 and 20. | > > > > | > > > > The chain of dependencies is like this: | > > > > | > > > > vdsm -> qemu -> libgfapi.so.0 | > > > > | > > > > I think a rebuild of QEMU should be sufficient. I'm planning to put | > > > > glusterfs-3.6 and rebuilds of related packages in a Fedora COPR. This | > > > > would make it possible for Fedora users to move to 3.6 before they | > > > > switch to Fedora 22. | > > > AFAICT the only difference between libgfapi.so.0 and libgfapi.so.7 are | > > > two added synbols (glfs_get_volfile, glfs_h_access) and __THROW on | > > > functions. Wouldn't it be possible to provide a compatibilty | > > libgfapi.so.0 | > > > to ease migration? | > > | > > That is possible, sure. I think that rebuilding related packages is just | > > easier, there are only a few needed. Users that would like to run 3.6 | > > before it is made available with Fedora 22 need to add a repository for | > > the glusterfs-3.6 packages anyway, using the same repository to provide | > > related packages is simple enough. | > > | > > But, if there is a strong interest in having a -compat package, we can | > > discuss that during tomorrows (Wednesdays) meeting. | > > | > > Thanks, | > > Niels | > > _______________________________________________ | > > Gluster-devel mailing list | > > Gluster-devel@xxxxxxxxxxx | > > http://supercolony.gluster.org/mailman/listinfo/gluster-devel | > > | _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
