All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Tricca <flihp@twobit.us>
To: yocto@yoctoproject.org
Subject: Re: [meta-selinux][PATCH] MAINTAINERS: Update maintainers file
Date: Sat, 20 Feb 2016 20:24:55 -0800	[thread overview]
Message-ID: <56C93C17.20704@twobit.us> (raw)
In-Reply-To: <1455763309-9622-1-git-send-email-joe_macdonald@mentor.com>

On 02/17/2016 06:41 PM, Joe MacDonald wrote:
> Adding Philip Tricca as a common layer maintainer and marking Pascal as
> away.

While the admins upstream get my ssh key in place I did a pass over the
pending patches and the current state of the repo. There isn't a lot to
do in the actual meta-selinux layer beyond what's already on the list.
There was only one fix needed to get the build working again:

The xattr patches to e2fsprogs have been superseded by the work that
WindRiver has been doing in upstream e2fsprogs. There's a bug in their
implementation though and the root directory on the rootfs image doesn't
get labeled. I've sent a fix to the upstream maintainer. In the meantime
the current patches can just be dropped and replaced with this one.

There's also one fix required to get a login shell working. In
openembedded-core, commit
http://git.openembedded.org/openembedded-core/commit/?id=b93369a7943949f51057e0a704f5524ab7682fe6
breaks the login process when the SELinux policy is enforced. I've sent
a patch upstream to fix this:
http://article.gmane.org/gmane.comp.handhelds.openembedded.core/76599

When I can commit these changes they're ready to go. After that I'll do
another pass over the list and pick up the remaining patches that
weren't required to get basic functionality back.

Philip


  parent reply	other threads:[~2016-02-21  4:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18  2:41 [meta-selinux][PATCH] MAINTAINERS: Update maintainers file Joe MacDonald
2016-02-18  7:59 ` 欧阳 鑫
2016-02-18 21:13 ` Philip Tricca
2016-02-21  4:24 ` Philip Tricca [this message]
2016-02-22 14:00   ` Joe MacDonald

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=56C93C17.20704@twobit.us \
    --to=flihp@twobit.us \
    --cc=yocto@yoctoproject.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.