From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Randy MacLeod <Randy.MacLeod@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] util-linux: fix alternatives setting for switch-root
Date: Fri, 19 Oct 2018 14:44:46 +0100 [thread overview]
Message-ID: <0420480dc8b495d9ff23c34ee0fbf13aa64c17c8.camel@linuxfoundation.org> (raw)
In-Reply-To: <8e1d32fc8f616637638b48e2ab18131fd4a9fef6.camel@linuxfoundation.org>
On Fri, 2018-10-19 at 14:37 +0100, Richard Purdie wrote:
> On Tue, 2018-10-16 at 19:24 -0400, Randy MacLeod wrote:
> > The alternative setting for switch_root belongs to the util-linux-
> > switch-root
> > package instead of the util-linux package. Fix this problem to
> > avoid
> > a dangling symlink:
> > /usr/bin/switch_root-> /usr/bin/switch_root.util-linux
> > on target and in the sdk.
> >
> > Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
> > ---
> > meta/recipes-core/util-linux/util-linux.inc | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
>
> As far as I can tell, this still breaks on the autobuilder:
>
>
https://autobuilder.yoctoproject.org/typhoon/#/builders/13/builds/125/steps/7/logs/step1b
>
https://autobuilder.yoctoproject.org/typhoon/#/builders/13/builds/125/steps/7/logs/step2b
>
https://autobuilder.yoctoproject.org/typhoon/#/builders/21/builds/132/steps/7/logs/step1b
It also appears I did merge the v2 so master is now broken and it
doesn't cleanly revert due to other patches against util-linux :(
If someone could figure out why its breaking for debian packaging and
help get it fixed that would be most appreciated!
Cheers,
Richard
prev parent reply other threads:[~2018-10-19 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 4:40 [PATCH] util-linux: fix alternatives setting for switch-root Randy MacLeod
2018-10-14 15:03 ` Richard Purdie
2018-10-16 23:24 ` [PATCH v2] " Randy MacLeod
2018-10-16 23:24 ` Randy MacLeod
2018-10-19 13:37 ` Richard Purdie
2018-10-19 13:44 ` Richard Purdie [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=0420480dc8b495d9ff23c34ee0fbf13aa64c17c8.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Randy.MacLeod@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