diff options
author | Mark Hatle <mark.hatle@windriver.com> | 2019-05-15 07:53:20 -0400 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-06-18 11:43:22 +0100 |
commit | 12a8a51e960d4ce31a64f5a7dc02c201238e760c (patch) | |
tree | 22a5c4dac6d924ca99007f575ba0127d33fac8a2 /bitbake/bin | |
parent | 33f9b99a47cc2ecf80e8d3258a68b45cc8116e03 (diff) | |
download | poky-12a8a51e960d4ce31a64f5a7dc02c201238e760c.tar.gz |
bitbake: gitsm: Fix a bug where the wrong path was used for the submodule init
Because we are trying to avoid network activity and use our own fetcher,
the system emulates the behavior of 'git submodule init'.
git submodule init uses the .gitmodules file, where typically the module
name and path are the same. However, in this case the module name and
path (in the tree) were different. i.e.:
[submodule "edgelet/hsm-sys/azure-iot-hsm-c/deps/azure-c-shared-utility"]
path = edgelet/hsm-sys/azure-iot-hsm-c/deps/c-shared
url = https://github.com/Azure/azure-c-shared-utility.git
Previously the code assumed the 'path' was both the checkout location
under .git/modules, as well as the path to extract the components. This
proved to be incorrect as the .git/modules path needs to match the submodule
'name'. This causes the components that were fetched to be initialized in
the wrong location, which later caused the 'git submodule update' process to
skip not properly initialized modules.
A test case was added for this specific case to ensure a regression does
not appear in the future.
(Bitbake rev: 2a823584a5dbc2427060352f3b4798dbb2640cfd)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/bin')
0 files changed, 0 insertions, 0 deletions