Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: native sysroot race with rpmbuild
Date: Mon, 14 Aug 2017 12:02:34 +0100	[thread overview]
Message-ID: <1502708554.13978.7.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAHiDW_GXRzkW14wT1o_v27WS1m72+bW5U55yZWjMSm2wKX4uNA@mail.gmail.com>

On Mon, 2017-08-14 at 13:55 +0300, Jussi Kukkonen wrote:
> Adwaita I had lost already but I've put the logs for failing
> packagegroup-core-x11-sato here:
> https://github.com/jku/packagegroup-core-x11-sato-logs
>  
> There's this in the log:
> | NOTE: rpm-native exists in sysroot, skipping

What is really interesting is:

https://github.com/jku/packagegroup-core-x11-sato-logs/blob/master/log.do_package_qa.28854

which looks to have been running about the same time as:

https://github.com/jku/packagegroup-core-x11-sato-logs/blob/master/log.do_package_write_rpm.28850

(similar pids and listed in https://github.com/jku/packagegroup-core-x11-sato-logs/blob/master/log.task_order after one another)

Note that package_qa seems to think the dependency disappeared and is
uninstalling elfutils (which provides libdw) from the sysroot.

That might be enough to figure out some kind of reproducer. All very
interesting and "potentially problematic"...

Cheers,

Richard


  reply	other threads:[~2017-08-14 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14  8:33 native sysroot race with rpmbuild Jussi Kukkonen
2017-08-14 10:38 ` Richard Purdie
2017-08-14 10:55   ` Jussi Kukkonen
2017-08-14 11:02     ` Richard Purdie [this message]
2017-08-26 22:36 ` Richard Purdie

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=1502708554.13978.7.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jussi.kukkonen@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