Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: ml@communistcode.co.uk,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] lib/oe/lsb: Add basic LSB functions
Date: Mon, 30 Jul 2012 15:50:41 -0400	[thread overview]
Message-ID: <20120730195041.GB11175@denix.org> (raw)
In-Reply-To: <5013B7B8.5020908@communistcode.co.uk>

On Sat, Jul 28, 2012 at 10:58:16AM +0100, Jack Mitchell wrote:
> On 28/07/2012 10:37, Martin Jansa wrote:
> >On Sat, Jul 28, 2012 at 11:16:14AM +0200, Martin Jansa wrote:
> >>>by installing lsb_release. Archlinux 64.
> >>>
> >>>Should it check to see if it installed first and error otherwise? It
> >>>looks like it tries to do it here:
> >>>
> >>>+    try:
> >>>+        output, err = bb.process.run(['lsb_release', '-a'], stderr=PIPE)
> >>>+    except bb.process.CmdError as exc:
> >>>+        return
> >>>
> >>>
> >>>but it must be missing something.
> >>
> >>Same here, interesting is that it failed only during 2nd build, 1st
> >>with this commit applied finished fine.
> >
> >Ah no, it was there also first time I've overlooked it as it's not
> >fatal.
> >
> 
> It was fatal for me as it trashed my sstate folder naming and then
> refused to build some packages. The directory in my sstate was
> created as:
> 
> ${NATIVELSBSTRING}
> 
> Then when Bitbake tried to use shared state it expanded
> NATIVELSBSTRING to nothing and failed.

I have the same issue here - Gentoo/64. Can we get it fixed in the master, 
please? Thanks.

-- 
Denys



  reply	other threads:[~2012-07-30 21:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 13:05 [PATCH] lib/oe/lsb: Add basic LSB functions Richard Purdie
2012-07-28  9:03 ` Jack Mitchell
2012-07-28  9:16   ` Martin Jansa
2012-07-28  9:37     ` Martin Jansa
2012-07-28  9:58       ` Jack Mitchell
2012-07-30 19:50         ` Denys Dmytriyenko [this message]
2012-07-31 10:47           ` 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=20120730195041.GB11175@denix.org \
    --to=denis@denix.org \
    --cc=ml@communistcode.co.uk \
    --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