[bitbake-devel] Sumo to Thud migration: Fetch failure from gitsm.py
Robert Yang
liezhi.yang at windriver.com
Fri Nov 23 10:30:33 UTC 2018
Hi,
Please refer to the following 2 commits in bitbake which may help:
commit a042179a784bab6a6f4bd5d63db80c1c02624b1c
Author: Mark Hatle <mark.hatle at windriver.com>
Date: Wed Oct 31 15:21:44 2018 -0400
bitbake: fetch2/gitsm.py: Fix the references when the module and path are
different
commit a28637abbceb05b52a6e38ab2340d3da9d0b1b37
Author: Mark Hatle <mark.hatle at windriver.com>
Date: Wed Oct 31 15:21:43 2018 -0400
bitbake: fetch2/gitsm.py: Disable branch checking on submodules
// Robert
On 11/22/18 11:31 PM, da Silva Filho, Josias Inacio wrote:
> Hi folks,
>
> I’m working on migrating my environment from Sumo to Thud. After fixing a few
> quirks, it seems the fetch is failing for my foo.bb which uses gitsm.
>
> *.gitmodules content in foo repo:*
>
> [submodule "common-lib"]
>
> path = common-lib
>
> url = ssh://git@<url_to_common-lib>/common-lib.git
>
> *foo.bb:*
>
> SRC_URI="gitsm://git@b<url_to_foo>.git;protocol=ssh;branch=master"
>
> SRCREV="f55fae9dc9b476f8ed193f15e2d5cd6747777451"
>
> Digging inside gitsm.py it looks like module_hash is not being set correctly
> (empty) and that causes the issue:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/lib/bb/fetch2/gitsm.py#n87
>
> I added the following right after line 87, so I could dump the variables
> content. This is how I confirmed module_hash is empty:
>
> *raise bb.fetch2.FetchError('module: %s, submodules: %s, module_hash: %s,
> basecmd: %s, revisions: %s, paths: %s, clonedir: %s ' % ( module, submodules,
> module_hash, ud.basecmd, ud.revisions[name], paths[module], ud.clonedir))*
>
> And the output:
>
> ERROR: Fetcher failure: module: common-lib, submodules: ['common-lib'],
> *module_hash*: , basecmd: git -c core.fsyncobjectfiles=0, revisions:
> f55fae9dc9b476f8ed193f15e2d5cd6747777451, paths: common-lib, clonedir:
> /localdata/yocto/downloads/git2/<foo's path>.git
>
> Any ideas why module_hash is not being set correctly?
>
>
More information about the bitbake-devel
mailing list