Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] Systemd Upgrade
Date: Mon, 07 Sep 2015 22:15:24 +0100	[thread overview]
Message-ID: <1441660524.24871.269.camel@linuxfoundation.org> (raw)
In-Reply-To: <E437DE0B-65F0-42B4-B061-BC30F27A24B8@gmail.com>

On Mon, 2015-09-07 at 14:12 -0700, Khem Raj wrote:
> > On Sep 7, 2015, at 2:09 PM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > 
> > On Mon, 2015-09-07 at 14:00 -0700, Khem Raj wrote:
> >>> On Sep 7, 2015, at 1:56 PM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> >>> 
> >>> A "bitbake core-image-sato -c testimage" replicated it here FWIW, have
> >>> you tried testimage to see if that somehow makes a difference? Shoudn't
> >>> be hard to test with that and for sato, it should run pretty quickly.
> >>> 
> >>> It all works with 219, its only the upgrade patches that seem to break
> >>> things :(
> >> 
> >> yeah my machine is w/o X and moreover I don’t have sudo on it test image seems to need X
> >> I will try to build core-image-sato and try to reproduce it locally. in order to analyze
> >> systemd defect it needs to be reproducible outside testimage infra anyway.
> > 
> > I believe the tests will run with the nographic options to qemu which
> > then won't need X, Ross had a patch around for that recently. To be
> > honest when looking at this kind of issue, I usually debug it using
> > testimage now, its actually easier in many cases…
> 
> in this case it will be faster. Care to point to Ross’s patch ?

http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=ross/mut&id=e67ab458ab2d67908d80f9aa1954dee05cb21fc1

Cheers,

Richard



  reply	other threads:[~2015-09-07 21:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 15:25 [PATCH 0/4] Systemd Upgrade Khem Raj
2015-09-06 15:25 ` [PATCH 1/4] busybox: Enable getopt applet Khem Raj
2015-09-06 15:25 ` [PATCH 2/4] rootfs: Do not uninstall update-rc.d Khem Raj
2015-09-07 19:36   ` Phil Blundell
2015-09-07 21:15     ` Khem Raj
2015-09-07 21:48       ` Phil Blundell
2015-09-08  7:03         ` Khem Raj
2015-09-08 19:38           ` Khem Raj
2015-09-10 15:48             ` Richard Purdie
2015-09-10 23:35               ` Khem Raj
2015-09-10 23:39                 ` Khem Raj
2015-09-06 15:25 ` [PATCH 3/4] systemd: Upgrade 219 -> 225 Khem Raj
2015-09-06 15:25 ` [PATCH 4/4] systemd: Implement OE-Specific systemd-sysv-install Khem Raj
2015-09-07 19:26 ` [PATCH 0/4] Systemd Upgrade Richard Purdie
2015-09-07 20:53   ` Khem Raj
2015-09-07 20:56     ` Richard Purdie
2015-09-07 21:00       ` Khem Raj
2015-09-07 21:09         ` Richard Purdie
2015-09-07 21:12           ` Khem Raj
2015-09-07 21:15             ` Richard Purdie [this message]
2015-09-08 10:31             ` Burton, Ross
2015-09-08 18:12               ` Khem Raj
2015-09-08 18:09   ` Khem Raj
2015-09-09 20:13     ` Burton, Ross

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=1441660524.24871.269.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox