From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] fakeroot "bug"
Date: Mon, 19 Feb 2018 10:40:32 +0100 [thread overview]
Message-ID: <20180219094032.agthcjdkd7xjwjsb@pengutronix.de> (raw)
In-Reply-To: <1518988283.11720.23.camel@erwinrol.com>
Hi,
On Sun, Feb 18, 2018 at 10:11:23PM +0100, Erwin Rol wrote:
> From time to time I run into this problem;
>
> http://lists.busybox.net/pipermail/buildroot/2017-August/200014.html
>
> which should be fixed by this patch;
>
> https://patchwork.ozlabs.org/patch/801046/
>
>
> But fakeroot doesn't seem to have a real "release" so my question, is
> this already part of the latest ptxdist fakeroot ?
We don't even have the latest release, and we don't have a patch for this,
so I don't think this is fixed in PTXdist. Patches welcome.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2018-02-19 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 21:11 Erwin Rol
2018-02-19 9:40 ` Michael Olbrich [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=20180219094032.agthcjdkd7xjwjsb@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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