From: Petr Lautrbach <plautrba@redhat.com>
To: SELinux list <selinux@vger.kernel.org>
Subject: ANN: SELinux userspace 3.0-rc2 release candidate
Date: Fri, 22 Nov 2019 15:54:15 +0100 [thread overview]
Message-ID: <pjd1ru0dkrs.fsf@redhat.com> (raw)
Hello,
A 3.0-rc2 release candidate for the SELinux userspace is now
available at:
https://github.com/SELinuxProject/selinux/wiki/Releases
Please give it a test and let us know if there are any issues.
If there are specific changes that you think should be called out
in release notes for packagers and users in the final release
announcement, let us know.
Thanks to all the contributors to this release candidate!
User-visible changes (since 3.0-rc1):
* Python 2 code is not be supported in this project anymore and new Python code
should be written only for Python 3.
* Messages about the statement failing to resolve and the optional block being
disabled are displayed at the highest verbosity level.
* Fixed redundant console log output error in restorecond
Issues fixed:
* https://github.com/SELinuxProject/selinux/issues/170
A shortlog of changes since the 3.0-rc1 release:
Baichuan Kong (1):
restorecond: Fix redundant console log output error
James Carter (1):
libsepol/cil: Report disabling an optional block only at high verbose levels
Nicolas Iooss (3):
libselinux,libsemanage: never create -.o in exception.sh
libselinux,libsemanage: fix python_exception.i dependencies
libselinux,libsemanage: check in python_exception.i files
Petr Lautrbach (5):
Replace www.nsa.gov references by github.com/SELinuxProject
python/sepolicy: Revert "Only invoke RPM on RPM-enabled Linux distributions"
Travis-CI: Drop Python 2 from matrix
dbus: Fix FileNotFoundError in org.selinux.relabel_on_boot
Update VERSIONs to 3.0-rc2 for release.
Thomas Petazzoni (1):
libselinux/src/Makefile: don't pass bogus -I and -L to python setup.py build_ext
reply other threads:[~2019-11-22 14:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pjd1ru0dkrs.fsf@redhat.com \
--to=plautrba@redhat.com \
--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.