On Wed, Jun 12, 2019 at 8:13 PM Deepshikha Khandelwal
wrote:
>
> On Thu, Jun 13, 2019 at 4:41 AM Kaleb Keithley
> wrote:
>
>>
>>
>> On Wed, Jun 12, 2019 at 11:36 AM Kaleb Keithley
>> wrote:
>>
>>>
>>> On Wed, Jun 12, 2019 at 10:43 AM Amar Tumballi Suryanarayan <
>>> atumb...@redhat.com> wrote:
Thanks Atin for pointing this out. Yes, I'll upgrade the matching build
tool on builders once coverity is upgraded on scan.coverity.com
On Thu, Jun 13, 2019 at 8:01 AM Atin Mukherjee
wrote:
> Fyi..no scan for 3-4 days starting from June 17th for the upgrade. Post
> that we may have to do some ch
On Thu, Jun 13, 2019 at 4:41 AM Kaleb Keithley wrote:
>
>
> On Wed, Jun 12, 2019 at 11:36 AM Kaleb Keithley
> wrote:
>
>>
>> On Wed, Jun 12, 2019 at 10:43 AM Amar Tumballi Suryanarayan <
>> atumb...@redhat.com> wrote:
>>
>>>
>>> We recently noticed that in one of the package update on builder (i
Fyi..no scan for 3-4 days starting from June 17th for the upgrade. Post
that we may have to do some changes to use the new build tool?
-- Forwarded message -
From: Peter Degen-Portnoy
Date: Thu, 13 Jun 2019 at 00:48
Subject: Details on the Scan.coverity.com June 2019 Upgrade
Jun
On Wed, Jun 12, 2019 at 11:36 AM Kaleb Keithley wrote:
>
> On Wed, Jun 12, 2019 at 10:43 AM Amar Tumballi Suryanarayan <
> atumb...@redhat.com> wrote:
>
>>
>> We recently noticed that in one of the package update on builder (ie,
>> centos7.x machines), python3.6 got installed as a dependency. So,
On Wed, Jun 12, 2019 at 10:43 AM Amar Tumballi Suryanarayan <
atumb...@redhat.com> wrote:
>
> We recently noticed that in one of the package update on builder (ie,
> centos7.x machines), python3.6 got installed as a dependency. So, yes, it
> is possible to have python3 in centos7 now.
>
EPEL upda
On Wed, Jun 12, 2019 at 8:42 PM Niels de Vos wrote:
> On Wed, Jun 12, 2019 at 07:54:17PM +0530, Hari Gowtham wrote:
> > We haven't sent any patch to fix it.
> > Waiting for the decision to be made.
> > The bz: https://bugzilla.redhat.com/show_bug.cgi?id=1719778
> > The link to the build log:
> >
On Wed, Jun 12, 2019 at 06:28:17PM +0200, Sander Eikelenboom wrote:
> On 12/06/2019 16:12, Kirill Smelkov wrote:
> > On Wed, Jun 12, 2019 at 03:03:49PM +0200, Sander Eikelenboom wrote:
> >> On 12/06/2019 13:25, Kirill Smelkov wrote:
> >>> On Wed, Jun 12, 2019 at 09:44:49AM +0200, Miklos Szeredi wro
On 12/06/2019 16:12, Kirill Smelkov wrote:
> On Wed, Jun 12, 2019 at 03:03:49PM +0200, Sander Eikelenboom wrote:
>> On 12/06/2019 13:25, Kirill Smelkov wrote:
>>> On Wed, Jun 12, 2019 at 09:44:49AM +0200, Miklos Szeredi wrote:
On Tue, Jun 11, 2019 at 10:28 PM Kirill Smelkov wrote:
>
On Wed, Jun 12, 2019 at 07:54:17PM +0530, Hari Gowtham wrote:
> We haven't sent any patch to fix it.
> Waiting for the decision to be made.
> The bz: https://bugzilla.redhat.com/show_bug.cgi?id=1719778
> The link to the build log:
> https://build.gluster.org/job/strfmt_errors/1/artifact/RPMS/el
We haven't sent any patch to fix it.
Waiting for the decision to be made.
The bz: https://bugzilla.redhat.com/show_bug.cgi?id=1719778
The link to the build log:
https://build.gluster.org/job/strfmt_errors/1/artifact/RPMS/el6/i686/build.log
The last few messages in the log:
config.status: crea
On Wed, Jun 12, 2019 at 03:03:49PM +0200, Sander Eikelenboom wrote:
> On 12/06/2019 13:25, Kirill Smelkov wrote:
> > On Wed, Jun 12, 2019 at 09:44:49AM +0200, Miklos Szeredi wrote:
> >> On Tue, Jun 11, 2019 at 10:28 PM Kirill Smelkov wrote:
> >>
> >>> Miklos, would 4K -> `sizeof(fuse_in_header) +
On Wed, Jun 12, 2019 at 02:44:04PM +0530, Hari Gowtham wrote:
> Hi,
>
> Due to the recent changes we made. we have a build issue because of glupy.
> As glupy is already removed from master, we are thinking of removing
> it in 5.7 as well rather than fixing the issue.
>
> The release of 5.7 will b
On 12/06/2019 13:25, Kirill Smelkov wrote:
> On Wed, Jun 12, 2019 at 09:44:49AM +0200, Miklos Szeredi wrote:
>> On Tue, Jun 11, 2019 at 10:28 PM Kirill Smelkov wrote:
>>
>>> Miklos, would 4K -> `sizeof(fuse_in_header) + sizeof(fuse_write_in)` for
>>> header room change be accepted?
>>
>> Yes, next
On 12/06/2019 13:25, Kirill Smelkov wrote:
> On Wed, Jun 12, 2019 at 09:44:49AM +0200, Miklos Szeredi wrote:
>> On Tue, Jun 11, 2019 at 10:28 PM Kirill Smelkov wrote:
>>
>>> Miklos, would 4K -> `sizeof(fuse_in_header) + sizeof(fuse_write_in)` for
>>> header room change be accepted?
>>
>> Yes, next
On Wed, Jun 12, 2019 at 09:44:49AM +0200, Miklos Szeredi wrote:
> On Tue, Jun 11, 2019 at 10:28 PM Kirill Smelkov wrote:
>
> > Miklos, would 4K -> `sizeof(fuse_in_header) + sizeof(fuse_write_in)` for
> > header room change be accepted?
>
> Yes, next cycle. For 4.2 I'll just push the revert.
T
Hi,
Due to the recent changes we made. we have a build issue because of glupy.
As glupy is already removed from master, we are thinking of removing
it in 5.7 as well rather than fixing the issue.
The release of 5.7 will be delayed as we have send a patch to fix this issue.
And if anyone has any c
On Tue, Jun 11, 2019 at 10:28 PM Kirill Smelkov wrote:
> Miklos, would 4K -> `sizeof(fuse_in_header) + sizeof(fuse_write_in)` for
> header room change be accepted?
Yes, next cycle. For 4.2 I'll just push the revert.
Thanks,
Miklos
18 matches
Mail list logo