On Thu, Nov 23, 2017 at 10:21 AM, Lukas Vrabec wrote:
> On 11/23/2017 10:17 AM, Javier Martinez Canillas wrote:
>>
>> Hello,
>>
>> On Fri, Oct 20, 2017 at 2:12 PM, Lukas Vrabec wrote:
>>
>> [snip]
>>
>>>
>>> Hello community,
>>> We, as Red Hat SELinux team, apologise for recent delays with our an
On 11/23/2017 10:17 AM, Javier Martinez Canillas wrote:
Hello,
On Fri, Oct 20, 2017 at 2:12 PM, Lukas Vrabec wrote:
[snip]
Hello community,
We, as Red Hat SELinux team, apologise for recent delays with our answers to
your requests and questions related to SELinux. We have been quite busy la
Hello,
On Fri, Oct 20, 2017 at 2:12 PM, Lukas Vrabec wrote:
[snip]
>
> Hello community,
> We, as Red Hat SELinux team, apologise for recent delays with our answers to
> your requests and questions related to SELinux. We have been quite busy last
> couple of weeks so we decided to set a lower pr
On Tue, Oct 24, 2017 at 12:25:14PM +0200, Petr Lautrbach wrote:
> On Tue, Oct 24, 2017 at 09:10:32AM +0200, Dominik 'Rathann' Mierzejewski
> wrote:
> > Hello, Lukas.
> > Thanks for this thread.
> >
> > On Monday, 23 October 2017 at 17:50, Lukas Vrabec wrote:
> > > On 10/21/2017 08:48 PM, Kevin Fe
On Tue, Oct 24, 2017 at 09:10:32AM +0200, Dominik 'Rathann' Mierzejewski wrote:
> Hello, Lukas.
> Thanks for this thread.
>
> On Monday, 23 October 2017 at 17:50, Lukas Vrabec wrote:
> > On 10/21/2017 08:48 PM, Kevin Fenzi wrote:
> [...]
> > > Also, perhaps it would make sense to move to a more no
Hello, Lukas.
Thanks for this thread.
On Monday, 23 October 2017 at 17:50, Lukas Vrabec wrote:
> On 10/21/2017 08:48 PM, Kevin Fenzi wrote:
[...]
> > Also, perhaps it would make sense to move to a more normal looking
> > release flow instead of a massive patch? I think that might make it
> > easie
On 10/21/2017 08:48 PM, Kevin Fenzi wrote:
On 10/20/2017 05:12 AM, Lukas Vrabec wrote:
Hello community,
Hey Lukas. Thanks for chiming in here.
We, as Red Hat SELinux team, apologise for recent delays with our
answers to your requests and questions related to SELinux. We have been
quite busy
On 10/20/2017 05:12 AM, Lukas Vrabec wrote:
> Hello community,
Hey Lukas. Thanks for chiming in here.
> We, as Red Hat SELinux team, apologise for recent delays with our
> answers to your requests and questions related to SELinux. We have been
> quite busy last couple of weeks so we decided to s
On 10/13/2017 11:07 PM, Jerry James wrote:
On Sat, Oct 7, 2017 at 9:34 AM, Jerry James wrote:
I don't believe that anybody looks at those pull requests on a regular
basis. Should somebody be doing so? There are 8 pull requests,
dating back to about the time of the above conversation. Five of
On Mon, Oct 16, 2017 at 12:04:58PM -0700, Japheth Cleaver wrote:
> On 10/13/2017 2:41 PM, Richard W.M. Jones wrote:
> >On Fri, Oct 13, 2017 at 03:07:05PM -0600, Jerry James wrote:
> >>But that's not the end of the fun. GCL failed the mass rebuild this
> >>summer. It built successfully on every ar
On 10/16/2017 09:04 PM, Japheth Cleaver wrote:
On 10/13/2017 2:41 PM, Richard W.M. Jones wrote:
On Fri, Oct 13, 2017 at 03:07:05PM -0600, Jerry James wrote:
But that's not the end of the fun. GCL failed the mass rebuild this
summer. It built successfully on every architecture but s390x. On
s
On 10/13/2017 2:41 PM, Richard W.M. Jones wrote:
On Fri, Oct 13, 2017 at 03:07:05PM -0600, Jerry James wrote:
But that's not the end of the fun. GCL failed the mass rebuild this
summer. It built successfully on every architecture but s390x. On
s390x, the build failed due to a failed call to m
> On Fri, 2017-10-13 at 14:53 -0700, Kevin Fenzi wrote:
> >
I don't know. Others have expressed frustration with selinux policy
> > maintainers of late as well. It's really hard to say what the trouble
> > is... are there to few of them? Overtasked with other work? Workflow too
> > difficult? Perh
On 14 Oct 2017 12:08 am, "Adam Williamson"
wrote:
On Fri, 2017-10-13 at 15:58 -0700, Kevin Fenzi wrote:
> On 10/13/2017 03:00 PM, Adam Williamson wrote:
> > On Fri, 2017-10-13 at 14:53 -0700, Kevin Fenzi wrote:
> > > It's really hard to say what the trouble
> > > is... are there to few of them? O
On Fri, 2017-10-13 at 15:58 -0700, Kevin Fenzi wrote:
> On 10/13/2017 03:00 PM, Adam Williamson wrote:
> > On Fri, 2017-10-13 at 14:53 -0700, Kevin Fenzi wrote:
> > > It's really hard to say what the trouble
> > > is... are there to few of them? Overtasked with other work? Workflow too
> > > diffic
On 10/13/2017 03:00 PM, Adam Williamson wrote:
> On Fri, 2017-10-13 at 14:53 -0700, Kevin Fenzi wrote:
>> It's really hard to say what the trouble
>> is... are there to few of them? Overtasked with other work? Workflow too
>> difficult?
>
> AFAIK it's basically just lvrabec at the moment, and I th
On Fri, 2017-10-13 at 14:53 -0700, Kevin Fenzi wrote:
> It's really hard to say what the trouble
> is... are there to few of them? Overtasked with other work? Workflow too
> difficult?
AFAIK it's basically just lvrabec at the moment, and I think the 'map'
permission issues that showed up this cycl
On 10/13/2017 02:07 PM, Jerry James wrote:
> On Sat, Oct 7, 2017 at 9:34 AM, Jerry James wrote:
...snip...
> But that's not the end of the fun. GCL failed the mass rebuild this
> summer. It built successfully on every architecture but s390x. On
> s390x, the build failed due to a failed call t
On 10/13/2017 11:07 PM, Jerry James wrote:
But that's not the end of the fun. GCL failed the mass rebuild this
summer. It built successfully on every architecture but s390x. On
s390x, the build failed due to a failed call to mprotect(), almost
certainly a sign that SELinux was in enforcing mod
On Fri, Oct 13, 2017 at 03:07:05PM -0600, Jerry James wrote:
> But that's not the end of the fun. GCL failed the mass rebuild this
> summer. It built successfully on every architecture but s390x. On
> s390x, the build failed due to a failed call to mprotect(), almost
> certainly a sign that SELi
20 matches
Mail list logo
