From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] fs: fix fakeroot issue with SElinux contexts
Date: Sat, 29 Oct 2016 10:33:43 +0200 [thread overview]
Message-ID: <20161029103343.7e4647b5@free-electrons.com> (raw)
In-Reply-To: <cover.1477729581.git.yann.morin.1998@free.fr>
Hello,
On Sat, 29 Oct 2016 10:26:38 +0200, Yann E. MORIN wrote:
> This series is an attempt at fixing fakeroot, which has issues with
> SElinux contexts (in extended attributes), as reported as one of our
> bug report, but also reported in Fedora Core and Debian:
> https://bugzilla.redhat.com/show_bug.cgi?id=1238802
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799858
>
> Since there has been absolutely no activity on the upstream (== Debian)
> report since it was filled more than a year ago, follow the path
> suggested in the FC report, and switch to using pseudo as a replacement
> for fakeroot.
>
> This can probably go in right now. If there are issues, we can still
> revert this before the end of the stabilisation month.
There are lots of other references to fakeroot all over the place, both
in fs/common.mk, but also the relatively new option we have to call a
script within the fakeroot context.
Do we keep them as-is, or do we rename everything to "pseudo" ? I find
the name "pseudo" very confusing, while "fakeroot" is a lot clearer, so
perhaps it is OK to keep everything named fakeroot even though in
practice we're using pseudo.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-29 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 8:26 [Buildroot] [PATCH 0/2] fs: fix fakeroot issue with SElinux contexts Yann E. MORIN
2016-10-29 8:26 ` [Buildroot] [PATCH 1/2] package/pseudo: new package Yann E. MORIN
2016-11-03 20:41 ` Thomas Petazzoni
2016-10-29 8:26 ` [Buildroot] [PATCH 2/2] fs: use pseudo instead of fakeroot Yann E. MORIN
2016-10-29 8:33 ` Thomas Petazzoni [this message]
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=20161029103343.7e4647b5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox