From: Petr Lautrbach <plautrba@redhat.com>
To: Russell Coker <russell@coker.com.au>
Cc: selinux@vger.kernel.org
Subject: Re: libsepol releases
Date: Tue, 7 Apr 2020 10:59:22 +0200 [thread overview]
Message-ID: <20200407085922.GA438349@workstation> (raw)
In-Reply-To: <3581425.j52oWYpJar@liv>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Sun, Apr 05, 2020 at 07:46:37PM +1000, Russell Coker wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955154
>
> We have the above Debian bug report requesting a GIT patch for libsepol for
> GCC-10 support.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955286
>
> We also have the above for a policy constraint error.
>
> Could we have a new upstream release soon to cover all GCC-10 issues as well
> as any other important things? Maybe version 3.0.1?
>
It's more than 4 months since the latest release so I think it's worth it to release 3.1.
If there's no objection, I'll send a heads up that we'll release 3.1-rc1 next week.
Petr
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-07 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 9:46 libsepol releases Russell Coker
2020-04-07 8:59 ` Petr Lautrbach [this message]
[not found] ` <20200422065053.GA167999@workstation>
[not found] ` <CAHC9VhQUmY=ue3zWdTnE1Ehi90Lj3077sLbu+jyaWoAVKuKyeQ@mail.gmail.com>
[not found] ` <CAFftDdo1hqbacU2TD6zQp_t_KJq-KS5pWBMr89c4HA3=aUdUbQ@mail.gmail.com>
[not found] ` <20200423150039.GC204116@workstation>
2020-05-14 21:00 ` Fedora VM On Travis for Testing William Roberts
2020-05-14 22:03 ` Nicolas Iooss
2020-05-14 22:23 ` William Roberts
2020-05-14 22:20 ` Stephen Smalley
2020-05-14 22:31 ` William Roberts
2020-05-15 20:51 ` William Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200407085922.GA438349@workstation \
--to=plautrba@redhat.com \
--cc=russell@coker.com.au \
--cc=selinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.