From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake dies with an python exception | AttributeError: 'NoneType' object has no attribute 'rfind'
Date: Sun, 28 Jul 2013 17:46:54 +0100 [thread overview]
Message-ID: <1989833.hj21tvi2MC@helios> (raw)
In-Reply-To: <CANyK_8deKJoCUCEnQeqCyBJNy0eKkk2GmJcX6ZDG80A66u52ng@mail.gmail.com>
Hi Paul,
On Sunday 28 July 2013 15:09:46 Paul Barker wrote:
> I've just ran into this again building dylan with the latest version
> of bitbake as it doesn't appear that the dylan branch of
> openembedded-core sets FAKEROOTCMD in bitbake.conf. I've cherry-picked
> the commit below from master onto dylan and it looks like the build is
> now going ahead happily.
>
> Bitbake has no dylan branch so I just assumed I was correct using
> master. Am I wrong here?
Technically the matching bitbake branch for dylan is 1.18. I'm not sure if we
spell this out anywhere, we probably should if not.
> If bitbake master is supposed to be able to build old branches of
> OpenEmbedded, perhaps this commit needs backporting to dylan/danny/etc? It
> looks like it shouldn't cause any harm if an older bitbake version is used
> as it simply adds values for FAKEROOTBASEENV and FAKEROOTCMD.
I haven't checked if it's a genuine problem, but I'd be concerned that any
fixes that went into OE-Core for bitbake's worker refactoring are not in dylan
and therefore you might get problems other than the one with FAKEROOTCMD.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-28 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 13:21 bitbake dies with an python exception | AttributeError: 'NoneType' object has no attribute 'rfind' Cestonaro Thilo
2013-07-04 8:18 ` Cestonaro Thilo
2013-07-04 9:17 ` Paul Eggleton
2013-07-04 9:53 ` Paul Barker
2013-07-04 10:48 ` Paul Eggleton
2013-07-04 10:55 ` Paul Barker
2013-07-05 12:35 ` Cestonaro Thilo
2013-07-28 14:09 ` Paul Barker
2013-07-28 16:46 ` Paul Eggleton [this message]
2013-07-29 7:47 ` Paul Barker
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=1989833.hj21tvi2MC@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.