On 01/23/2018 05:56 AM, Niels de Vos wrote: > On Mon, Jan 22, 2018 at 12:22:37PM -0500, Shyam Ranganathan wrote: >> On 01/20/2018 08:32 AM, Niels de Vos wrote: >>> On Sat, Jan 20, 2018 at 11:55:33AM +0000, jenk...@build.gluster.org wrote: >>>> SRC: >>>> https://build.gluster.org/job/release-new/38/artifact/glusterfs-3.13.2.tar.gz >>>> HASH: >>>> https://build.gluster.org/job/release-new/38/artifact/glusterfs-3.13.2.sha512sum >>> >>> Packages for CentOS 6 and 7 have been built and will become available in >>> the testing repository within the next few hours. Please test and let me >>> know when they can be marked for release. >>> >>> # yum install centos-release-gluster313 >>> # yum --enablerepo=centos-gluster313-test install glusterfs-server >> >> There seems to be a problem with our userspace-rcu dependency. As >> follows, if this package is updated, we get into the following >> dependency issue. >> >> Niels, is there a way to get this corrected? >> >> ---> Package userspace-rcu.x86_64 0:0.7.16-3.el7 will be updated >> --> Processing Dependency: liburcu-bp.so.1()(64bit) for package: >> glusterfs-server-3.13.2-1.el7.x86_64 >> --> Processing Dependency: liburcu-cds.so.1()(64bit) for package: >> glusterfs-server-3.13.2-1.el7.x86_64 >> ---> Package userspace-rcu.x86_64 0:0.10.0-3.el7 will be an update >> --> Finished Dependency Resolution >> Error: Package: glusterfs-server-3.13.2-1.el7.x86_64 >> (@centos-gluster313-test) >> Requires: liburcu-bp.so.1()(64bit) >> Removing: userspace-rcu-0.7.16-3.el7.x86_64 (@centos-gluster310) >> liburcu-bp.so.1()(64bit) >> Updated By: userspace-rcu-0.10.0-3.el7.x86_64 (centos-gluster313) >> ~liburcu-bp.so.6()(64bit) >> Error: Package: glusterfs-server-3.13.2-1.el7.x86_64 >> (@centos-gluster313-test) >> Requires: liburcu-cds.so.1()(64bit) >> Removing: userspace-rcu-0.7.16-3.el7.x86_64 (@centos-gluster310) >> liburcu-cds.so.1()(64bit) >> Updated By: userspace-rcu-0.10.0-3.el7.x86_64 (centos-gluster313) >> ~liburcu-cds.so.6()(64bit) > > It seems that the glusterfs-3.13 packages got built against > userspace-rcu-0.7 and not the newer 0.10 version. There seems to have > been some kind of build-override in the > storage7-gluster-common-candidate tag, removing the 0.7 version from > there made the 0.10 version available for glusterfs-3.13. > > Next steps: > - rebuild glusterfs-3.13.2 > - verify none of the other versions that require 0.7 have been broken > > Note that it might have been possible that others can install > glusterfs-3.13.x when EPEL is enabled. Fedora EPEL provides a (possibly > and surely untested) compatible older version of userspace-rcu. Also, > userspace-rcu was only updated in CentOS-7 for ppc64le/aarch64 fixes, > these architectures are not available for CentOS-6.
Have we checked that userspace-rcu-0.10 is tagged correctly? From #centos-devel [16:48:53] <bstinson> kkeithley: if you need userspace-rcu-0.10 in the buildroot you should tag it into storage7-gluster-313-candidate (anything in that tag gets inherited in subsequent builds) -- Kaleb _______________________________________________ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging