From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9386] ubinize fails with or without custom config
Date: Sat, 29 Oct 2016 07:45:05 +0000 [thread overview]
Message-ID: <bug-9386-163-sHfxavEba9@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9386-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9386
--- Comment #10 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Gustavo, Andrey,
OK, so this is a known issue with fakeroot relating to xattrs.
There is nothing we can do in Buildroot, except as you said,
to run outside fakeroot.
But that solution means we need to tweak our fs infra just
for the sake of a bug in fakeroot. That's not nice...
However, following the bug report Gustavo copied, I got to:
https://www.yoctoproject.org/tools-resources/projects/pseudo
As they say:
> Pseudo is a program that can either be used directly or as
> an LD_PRELOAD, which allows these operations to succeed as
> if the user did have system administrator privileges even
> though they are an ordinary user.
>
> Pseudo has a lot of similarities to fakeroot but is a new
> implementation that improves on the problems seen using
> fakeroot.
Maybe we should also go with pseudo in Buildroot, and ditch
fakeroot? I'll try to have a look at that, and see if I can
come up with a patch.
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-10-29 7:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 18:20 [Buildroot] [Bug 9386] New: ubinize fails with or without custom config bugzilla at busybox.net
2016-10-27 20:30 ` [Buildroot] [Bug 9386] " bugzilla at busybox.net
2016-10-27 20:39 ` bugzilla at busybox.net
2016-10-27 21:22 ` bugzilla at busybox.net
2016-10-27 21:24 ` bugzilla at busybox.net
2016-10-27 21:56 ` bugzilla at busybox.net
2016-10-27 22:13 ` bugzilla at busybox.net
2016-10-27 23:08 ` bugzilla at busybox.net
2016-10-28 18:42 ` bugzilla at busybox.net
2016-10-28 21:31 ` bugzilla at busybox.net
2016-10-29 7:45 ` bugzilla at busybox.net [this message]
2016-10-29 8:28 ` bugzilla at busybox.net
2016-11-03 20:40 ` bugzilla at busybox.net
2016-11-23 12:37 ` bugzilla at busybox.net
2016-11-23 12:41 ` bugzilla at busybox.net
2016-11-23 12:56 ` bugzilla at busybox.net
2016-11-27 20:29 ` bugzilla at busybox.net
2016-11-28 18:06 ` bugzilla at busybox.net
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=bug-9386-163-sHfxavEba9@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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