[Gluster-Maintainers] [Gluster-devel] Release 4.1: Branched

[Kaushal M]

On Mon, Jun 4, 2018 at 7:05 PM Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote:
>
> On 06/02/2018 07:47 AM, Niels de Vos wrote:
> > On Sat, Jun 02, 2018 at 12:11:55AM +0530, Kaushal M wrote:
> >> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan <srangana at redhat.com> wrote:
> >>>
> >>> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
> >>>> As brick-mux tests were failing (and still are on master), this was
> >>>> holding up the release activity.
> >>>>
> >>>> We now have a final fix [1] for the problem, and the situation has
> >>>> improved over a series of fixes and reverts on the 4.1 branch as well.
> >>>>
> >>>> So we hope to branch RC0 today, and give a week for package and upgrade
> >>>> testing, before getting to GA. The revised calendar stands as follows,
> >>>>
> >>>> - RC0 Tagging: 31st May, 2018
> >>>
> >>> RC0 Tagged and off to packaging!
> >>
> >> GD2 has been tagged as well. [1]
> >>
> >> [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0
> >
> > What is the status of the RPM for GD2? Can the Fedora RPM be rebuilt
> > directly on CentOS, or does it need additional dependencies? (Note that
> > CentOS does not allow dependencies from Fedora EPEL.)
> >
>
> My recollection of how this works is that one would need to build from
> the "bundled vendor" tarball.
>
> Except when I tried to download the vendor bundle tarball I got the same
> bits as the unbundled tarball.
>
> ISTR Kaushal had to do something extra to generate the vendor bundled
> tarball. It doesn't appear that that occured.

That is right. For CentOS/EL, the default in the spec is to use the
vendored tarball. Using this, the only requirement to build GD2 is
golang>=1.8.
Are you sure you're downloading the right tarball [1]?

[1]: https://github.com/gluster/glusterd2/releases/download/v4.1.0-rc0/glusterd2-v4.1.0-rc0-vendor.tar.xz
>
> --
>
> Kaleb