Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Maxin B. John" <maxin.john@intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sstatesig: don't squash dependencies of useradd packages
Date: Mon, 23 Jan 2017 15:59:31 +0000	[thread overview]
Message-ID: <1485187171.30673.25.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170123145537.GA6330@mbabyjoh-desk.ger.corp.intel.com>

On Mon, 2017-01-23 at 16:55 +0200, Maxin B. John wrote:
> Ping.

This never merged as I was never 100% convinced this was the correct
way to solve this problem. I'd be interested to understand if the
sstatesig tests in oe-selftest worked after this.

I'm hoping this issue has also now been resolved in a different way
though the switch to recipe specific sysroots. Would you be able test
if recipe specific sysroots have addressed this issue?

Cheers,

Richard


  reply	other threads:[~2017-01-23 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 13:48 [PATCH] sstatesig: don't squash dependencies of useradd packages Maxin B. John
2017-01-23 14:55 ` Maxin B. John
2017-01-23 15:59   ` Richard Purdie [this message]
2017-01-25 14:43     ` Maxin B. John

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=1485187171.30673.25.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=maxin.john@intel.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