From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Saul Wold <saul.wold@intel.com>
Subject: Re: [PATCH V2 0/5] fix WARNING: QA Issue on kmod/udev/nfs-utils (unsafe references [/ references to /usr/lib])
Date: Mon, 04 Nov 2013 12:10:00 +0000 [thread overview]
Message-ID: <1383567000.6271.109.camel@ted> (raw)
In-Reply-To: <CAP9ODKqr8eHVck5YSpVCgxugW7UJZrXfNey=sM=_6Eo-W1HPDg@mail.gmail.com>
On Mon, 2013-11-04 at 09:48 -0200, Otavio Salvador wrote:
> On Mon, Nov 4, 2013 at 9:39 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Mon, 2013-11-04 at 17:56 +0800, Hongxu Jia wrote:
> >> Change in V2: The fourth patch fixed the QA Issue on udev, it was missed on previous version.
> >>
> >> //Hongxu
> >>
> >> The following changes since commit f3541226b8b1187e79dec0f6f9f3c58cedf9ac9b:
> >>
> >> bitbake: hob: do not display the "Package list may be incomplete!" dialog (2013-11-01 17:59:31 +0000)
> >>
> >> are available in the git repository at:
> >>
> >> git://git.pokylinux.org/poky-contrib hongxu/fix-qa-issue
> >> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/fix-qa-issue
> >>
> >> Hongxu Jia (5):
> >> insane.bbclass: support to skip unsafe references in binaries qa
> >> check.
> >> kmod: fix QA issue
> >> udev: fix QA issue
> >> udev: fix QA issue
> >> nfs-utils: fix QA issue
> >
> > Last time these warnings came up I asked for a clear plan about what
> > needed to live in / and what needed to live in /usr and how we were
> > going to fix things once and for all (or forget this idea).
> >
> > Where is the plan? Why is it ok to just ignore these particular
> > warnings?
>
> I don't think supporting /bin and /sbin separated than /usr is worth the work.
I keep hearing that some people do need this. I'm not against it in
principle, equally I do want to see a plan and/or complete patchset
before we take more patches for it.
Cheers,
Richard
next prev parent reply other threads:[~2013-11-04 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 9:56 [PATCH V2 0/5] fix WARNING: QA Issue on kmod/udev/nfs-utils (unsafe references [/ references to /usr/lib]) Hongxu Jia
2013-11-04 9:56 ` [PATCH 1/5] insane.bbclass: support to skip unsafe references in binaries qa check Hongxu Jia
2013-11-04 9:56 ` [PATCH 2/5] kmod: fix QA issue Hongxu Jia
2013-11-04 9:56 ` [PATCH 3/5] udev: " Hongxu Jia
2013-11-04 9:56 ` [PATCH 4/5] " Hongxu Jia
2013-11-04 9:56 ` [PATCH 5/5] nfs-utils: " Hongxu Jia
2013-11-04 11:39 ` [PATCH V2 0/5] fix WARNING: QA Issue on kmod/udev/nfs-utils (unsafe references [/ references to /usr/lib]) Richard Purdie
2013-11-04 11:48 ` Otavio Salvador
2013-11-04 12:10 ` Richard Purdie [this message]
2013-11-04 12:08 ` Hongxu Jia
2013-11-09 5:26 ` ChenQi
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=1383567000.6271.109.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=saul.wold@intel.com \
/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.