All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Subject: ANN: SELinux userspace 3.4-rc3 release candidate
Date: Wed, 04 May 2022 20:48:41 +0200	[thread overview]
Message-ID: <878rrh877a.fsf@redhat.com> (raw)

Hello,

A 3.4-rc3 release candidate for the SELinux userspace is now
available at:

https://github.com/SELinuxProject/selinux/wiki/Releases

Tarballs are signed with
https://people.redhat.com/plautrba/plautrba@redhat.com.asc

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!

Changes since 3.4-rc2
---------------------
* A new setfiles option [-C] for distinguishing file tree walk errors

* Added missing sandbox translations

Shortlog of changes since the 3.4-rc2 release
---------------------------------------------
Christian Göttsche (1):
      checkpolicy: mention class name on invalid permission

Laszlo Ersek (5):
      setfiles: fix up inconsistent indentation
      setfiles: remove useless assignment and comment (after RHBZ#1926386)
      setfiles: remove useless "iamrestorecon" checks in option parsing
      selinux_restorecon: introduce SELINUX_RESTORECON_COUNT_ERRORS
      setfiles: introduce the -C option for distinguishing file tree walk errors

Petr Lautrbach (2):
      Update missing sandbox translations
      Update VERSIONs to 3.4-rc3 for release.


             reply	other threads:[~2022-05-04 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 18:48 Petr Lautrbach [this message]
2022-05-05 17:47 ` ANN: SELinux userspace 3.4-rc3 release candidate Christian Göttsche

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=878rrh877a.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.