From: Seebs <seebs@seebs.net>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] pseudo: Upgrade to latest to fix openat() with a directory symlink [NAK]
Date: Thu, 1 Aug 2019 18:57:25 -0500 [thread overview]
Message-ID: <20190801185725.139cfa73@seebsdell> (raw)
In-Reply-To: <8934e4e0-aaf6-5eb6-5d1b-355063bee94a@windriver.com>
On Thu, 1 Aug 2019 16:37:26 -0500
Jason Wessel <jason.wessel@windriver.com> wrote:
> It seems to have caused really odd problems with the oe link
> management that were not there previously, such as:
>
>
> WARNING: pinentry-1.1.0-r0 do_package_qa: QA Issue:
> pinentry: /usr/bin/pinentry is owned by uid 5002, which is the same
> as the user running bitbake. This may be due to host contamination
> [host-user-contaminated]
>
> I'll continue to look into the problem.
There's a possibility that the right flag is something like
(flags&O_NOFOLLOW)&&!(flags&O_PATH)
or something like that. There's a handful of references to this in
wrapfuncs.in in ports/unix and ports/linux.
-s
next prev parent reply other threads:[~2019-08-01 23:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 20:03 [PATCH v2] pseudo: Upgrade to latest to fix openat() with a directory symlink Jason Wessel
2019-08-01 21:37 ` [PATCH v2] pseudo: Upgrade to latest to fix openat() with a directory symlink [NAK] Jason Wessel
2019-08-01 23:57 ` Seebs [this message]
2019-08-02 16:27 ` Jason Wessel
2019-08-02 17:07 ` Seebs
2019-08-02 17:42 ` Seebs
2019-08-03 12:33 ` Khem Raj
2019-08-03 14:23 ` Seebs
2019-08-03 14:57 ` Khem Raj
2019-08-04 16:13 ` Mark Hatle
2019-08-05 14:23 ` Jason Wessel
2019-08-05 22:42 ` Bystricky, Juro
2019-08-06 6:51 ` Martin Jansa
2019-08-14 16:02 ` Randy MacLeod
2019-08-14 17:09 ` Martin Jansa
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=20190801185725.139cfa73@seebsdell \
--to=seebs@seebs.net \
--cc=jason.wessel@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox