All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Kiernan <alex.kiernan@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bmap-tools: update from 3.4 to 3.5
Date: Sat, 16 Feb 2019 12:22:55 +0000	[thread overview]
Message-ID: <CAO5Uq5Q=GWBrsUGpk=uMGRrBapcnmB31XwYLve7OuhiXNOvp7g@mail.gmail.com> (raw)
In-Reply-To: <689a3e6f6f81d9f9e300ea5d0d0e9641f753d87b.camel@linuxfoundation.org>

On Sat, Feb 16, 2019 at 11:32 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Sat, 2019-02-16 at 09:25 +0000, Alex Kiernan wrote:
> > On Fri, Feb 15, 2019 at 11:16 PM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > > On Thu, 2019-02-14 at 21:09 +0000, Alex Kiernan wrote:
> > > > bmap-tools 3.5 was released August 2018 but has no release tarball,
> > > > so
> > > > switch to using the git fetcher. Also pull in the fix for
> > > > StopIteration
> > > > being transformed into RuntimeError for Python 3.7.
> > > >
> > > > Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
> > >
> > > Unfortunately this triggers a selftest failure:
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/236
> > >
> > > (ignore the virtgl piece, that is something else)
> > >
> > > oe-selftest -r wic.Wic2.test_bmap_short
> > > and
> > > oe-selftest -r wic.Wic2.test_bmap_long
> > >
> > > should reproduce. Might be as simple as a missing RDEPENDS.
> > >
> >
> > Looks like it's gained a dependency on six. And thanks for the
> > reproducing steps - I've never got to grips with that stuff before.
> >
> > That said I'm struggling to get the tests to actually pass. I've
> > added
> > in python3-six to RDEPENDS, but it still fails with
> > `ModuleNotFoundError: No module named 'six'`?
>
> We appear to have walked into spools of razor wire :/
>
> This is an open bug:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10113
>
> which I'm struggling to know how to fix.
>
> What does appear to work locally is adding something like:
>
> # We need the native dependency on python3-six at runtime
> # See bug 10113
> EXTRASYSROOTDEPTASK = ""
> EXTRASYSROOTDEPTASK_class-native = "do_populate_sysroot"
> do_populate_sysroot[rdeptask] = "${EXTRASYSROOTDEPTASK}"
>
> Whether this is the right thing to do I'm less sure about.
>
> It may be an idea to start introducing these dependencies where we need
> them to fix bugs, until we can sort the problem properly in
> native.bbclass.
>

Thanks, that seems to work... I'd have been here forever trying to find that.

I'll send a v3 with that change in it.

-- 
Alex Kiernan


  reply	other threads:[~2019-02-16 12:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 21:09 [PATCH] bmap-tools: update from 3.4 to 3.5 Alex Kiernan
2019-02-14 21:17 ` Alexander Kanavin
2019-02-15 11:27   ` Richard Purdie
2019-02-15 12:15     ` Alexander Kanavin
2019-02-15 14:55     ` Alex Kiernan
2019-02-15 23:16 ` Richard Purdie
2019-02-16  9:25   ` Alex Kiernan
2019-02-16 11:31     ` Richard Purdie
2019-02-16 12:22       ` Alex Kiernan [this message]
2019-02-16 15:08         ` 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='CAO5Uq5Q=GWBrsUGpk=uMGRrBapcnmB31XwYLve7OuhiXNOvp7g@mail.gmail.com' \
    --to=alex.kiernan@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 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.