[prev in list] [next in list] [prev in thread] [next in thread] 

List:       selinux-commits
Subject:    [SELinux commit]SELinux userland upstream repository branch, master,
From:       csellers () oss ! tresys ! com (csellers at oss ! tresys ! com)
Date:       2009-11-19 22:19:40
Message-ID: 200911192219.nAJMJeKQ008942 () oss ! tresys ! com
[Download RAW message or body]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "SELinux userland upstream repository".

The branch, master has been updated
       via  3d2f8e21d2508e0a481e54cf0cf898a051d344c7 (commit)
       via  ae50dd55e064525c40cfe257581d52dbc4808a22 (commit)
       via  32ae03e8a7a5200ecfb9063b0a8d383763853596 (commit)
      from  88a57ca14b1fc645648e63e6117a125d3af5ea55 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 3d2f8e21d2508e0a481e54cf0cf898a051d344c7
Author: Chad Sellers <csellers at tresys.com>
Date:   Thu Nov 19 17:16:03 2009 -0500

    Bump policycoreutils to 2.0.77
    
    Signed-off-by: Chad Sellers <csellers at tresys.com>

commit ae50dd55e064525c40cfe257581d52dbc4808a22
Author: Chad Sellers <csellers at tresys.com>
Date:   Thu Nov 19 15:01:13 2009 -0500

    Fix bug in semanage fcontext
    
    Apparently I failed to split out the whitespace changes from a
    previous patchset, and a bit of the equivalence patch of the
    day snuck in. This causes a stack trace when you execute
    semanage fcontext -l. This patch reverts the accidentally
    included code.
    
    Signed-off-by: Chad Sellers <csellers at tresys.com>

commit 32ae03e8a7a5200ecfb9063b0a8d383763853596
Author: Chad Sellers <csellers at tresys.com>
Date:   Thu Nov 19 14:32:42 2009 -0500

    semanage node -a bug
    
    This patch fixes a bug that causes semanage node -a to not work
    (failing with a python traceback). You can test the bug with any
    semanage node -a command, such as:
    
    semanage node -a -t node_t -p ipv4 -M 255.255.255.0 192.168.1.0
    
    Signed-off-by: Chad Sellers <csellers at tresys.com>

-----------------------------------------------------------------------

Summary of changes:
 policycoreutils/ChangeLog            |    6 ++++++
 policycoreutils/VERSION              |    2 +-
 policycoreutils/semanage/seobject.py |    8 +-------
 3 files changed, 8 insertions(+), 8 deletions(-)


hooks/post-receive
--
SELinux userland upstream repository

[prev in list] [next in list] [prev in thread] [next in thread]