From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: chris.laplante@agilent.com, openembedded-core@lists.openembedded.org
Subject: Re: UNVERIFIED SENDER Re: Running BitBake multiple times without rechecking upstream AUTOREV versions
Date: Mon, 14 May 2018 14:13:17 +0100 [thread overview]
Message-ID: <1526303597.5720.115.camel@linuxfoundation.org> (raw)
In-Reply-To: <BN6PR1201MB019568D1F8B405A49C7121CA8B9C0@BN6PR1201MB0195.namprd12.prod.outlook.com>
On Mon, 2018-05-14 at 13:05 +0000, chris.laplante@agilent.com wrote:
> Hi Richard,
>
> That looks perfect, thanks! On a related note, it seems "bitbake --
> revisions-changed" is broken in Sumo:
>
> ERROR: Command execution failed: Traceback (most recent call last):
> File "/home/laplante/yocto/sources/poky/bitbake/lib/bb/command.py",
> line 116, in runAsyncCommand
> commandmethod(self.cmds_async, self, options)
> File "/home/laplante/yocto/sources/poky/bitbake/lib/bb/command.py",
> line 723, in compareRevisions
> if bb.fetch.fetcher_compare_revisions(command.cooker.data):
> TypeError: fetcher_compare_revisions() takes 0 positional arguments
> but 1 was given
>
>
>
> Looks like commit 97617fd6755ffa25c058215ffb060cbb86240b44 dropped
> the 'd' argument from that method, but command.py was never updated
> to reflect that.
>
> Shall I submit a patch to change the line to be "if
> bb.fetch.fetcher_compare_revisions():" ?
A patch to the bitbake list would be great thanks!
Cheers,
Richard
next prev parent reply other threads:[~2018-05-14 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 18:23 Running BitBake multiple times without rechecking upstream AUTOREV versions chris.laplante
2018-05-14 8:20 ` Richard Purdie
2018-05-14 13:05 ` UNVERIFIED SENDER " chris.laplante
2018-05-14 13:13 ` Richard Purdie [this message]
2018-05-15 15:43 ` Andrea Galbusera
2018-05-15 21:46 ` Andrea Galbusera
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=1526303597.5720.115.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=chris.laplante@agilent.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