On Mon, Jun 18, 2018 at 11:30 PM Kaleb S. KEITHLEY wrote:
>
> On 06/18/2018 12:03 PM, Kaushal M wrote:
> >
> > GD2 packages have been built for Fedora 28 and available from the
> > updates-testing repo, and soon from the updates repo
> > Packages are also available for Fedora 29/Rawhide.
> >
> I
On 06/18/2018 12:03 PM, Kaushal M wrote:
>
> GD2 packages have been built for Fedora 28 and available from the
> updates-testing repo, and soon from the updates repo
> Packages are also available for Fedora 29/Rawhide.
>
I built GD2 rpms for Fedora 27 using the -vendor tar file. They are
On Fri, Jun 15, 2018 at 6:26 PM Niels de Vos wrote:
>
> On Fri, Jun 15, 2018 at 05:03:38PM +0530, Kaushal M wrote:
> > In Tue, Jun 12, 2018 at 10:15 PM Niels de Vos wrote:
> > >
> > > On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan wrote:
> > > > On 05/31/2018 09:22 AM, Shyam
what about packages built in Fedora?
On 06/15/2018 07:33 AM, Kaushal M wrote:
> In Tue, Jun 12, 2018 at 10:15 PM Niels de Vos wrote:
>>
>> On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan wrote:
>>> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
As brick-mux tests were failing
In Tue, Jun 12, 2018 at 10:15 PM Niels de Vos wrote:
>
> On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan 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.
> > >
>
On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan 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
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.
On Mon, Jun 4, 2018 at 10:55 PM Kaleb S. KEITHLEY wrote:
>
> On 06/04/2018 11:32 AM, Kaushal M wrote:
>
> >
> > We have a proper release this time. Source tarballs are available from [1].
> >
> > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0
> >
>
> I didn't wait for you to do
On Mon, Jun 04, 2018 at 09:02:30PM +0530, Kaushal M wrote:
> On Mon, Jun 4, 2018 at 8:54 PM Kaushal M wrote:
> >
> > On Mon, Jun 4, 2018 at 8:39 PM Kaushal M wrote:
> > >
> > > On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote:
> > > >
> > > > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan
>
On 06/04/2018 11:32 AM, Kaushal M wrote:
>
> We have a proper release this time. Source tarballs are available from [1].
>
> [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0
>
I didn't wait for you to do COPR builds.
There are rpm packages for RHEL/CentOS 7, Fedora 27,
On Mon, Jun 4, 2018 at 8:54 PM Kaushal M wrote:
>
> On Mon, Jun 4, 2018 at 8:39 PM Kaushal M wrote:
> >
> > On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote:
> > >
> > > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan
> > > wrote:
> > > >
> > > > On 05/31/2018 09:22 AM, Shyam Ranganathan
On Mon, Jun 4, 2018 at 8:39 PM Kaushal M wrote:
>
> On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote:
> >
> > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan
> > wrote:
> > >
> > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
> > > > As brick-mux tests were failing (and still are on
On 06/04/2018 11:05 AM, Kaushal M wrote:
>
>> And it's good that RC0 was tagged in a timely matter. Who is building
>> those packages?
>
> I can build the RPMs. I'll build them on the COPR I've been
> maintaining. But I don't believe that those can be used as the
> official RPM sources.
> So
On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote:
>
> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan 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
On Mon, Jun 4, 2018 at 5:29 PM Kaleb S. KEITHLEY 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
> >> wrote:
> >>>
> >>> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
>
On Mon, Jun 4, 2018 at 7:05 PM Kaleb S. KEITHLEY 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
> >> wrote:
> >>>
> >>> On 05/31/2018 09:22 AM, Shyam Ranganathan 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 wrote:
>>>
>>> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
As brick-mux tests were failing (and still are on master), this was
On Sat, Jun 02, 2018 at 12:11:55AM +0530, Kaushal M wrote:
> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan 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.
> > >
> >
On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan 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
> >
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.
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
21 matches
Mail list logo
