2016-10-23 21:29:25

by Chris PeBenito

[permalink] [raw]
Subject: [refpolicy] ANN: Reference Policy Release

A new release of the SELinux Reference Policy is now available on the
GitHub site, https://github.com/TresysTechnology/refpolicy.

The full changelog is too long to include in this email, so here's the
diffstat instead:

Core:
82 files changed, 1411 insertions(+), 225 deletions(-)

Contrib:
125 files changed, 1275 insertions(+), 133 deletions(-)

--
Chris PeBenito


2016-11-02 04:13:07

by Russell Coker

[permalink] [raw]
Subject: [refpolicy] ANN: Reference Policy Release

On Sunday, 23 October 2016 5:29:25 PM AEDT Chris PeBenito wrote:
> A new release of the SELinux Reference Policy is now available on the
> GitHub site, https://github.com/TresysTechnology/refpolicy.

https://github.com/TresysTechnology/refpolicy/wiki/DownloadRelease

The archive at the above page has the files policy.28 and policy.30.orig which
comprise more than half the compressed archive size.

Could you make a new release without them? Otherwise we are going to have
that in all the distribution archives and mirror sites.

Also in future could we have more frequent releases? More frequent upstream
releases makes it easier for distribution people to send changes upstream and
gives a greater incentive to do so.

--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/

2016-11-02 22:19:13

by Chris PeBenito

[permalink] [raw]
Subject: [refpolicy] ANN: Reference Policy Release

On 11/02/16 00:13, Russell Coker wrote:
> On Sunday, 23 October 2016 5:29:25 PM AEDT Chris PeBenito wrote:
>> A new release of the SELinux Reference Policy is now available on the
>> GitHub site, https://github.com/TresysTechnology/refpolicy.
>
> https://github.com/TresysTechnology/refpolicy/wiki/DownloadRelease
>
> The archive at the above page has the files policy.28 and policy.30.orig which
> comprise more than half the compressed archive size.
>
> Could you make a new release without them? Otherwise we are going to have
> that in all the distribution archives and mirror sites.

I've fixed the release package; sorry about that.

> Also in future could we have more frequent releases? More frequent upstream
> releases makes it easier for distribution people to send changes upstream and
> gives a greater incentive to do so.

Yes, I'd like to get back closer to 4/year at least.

--
Chris PeBenito