summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/fetch2/gitsm.py
diff options
context:
space:
mode:
authorNeil Horman <nhorman@gmail.com>2022-08-30 07:44:45 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-09-01 10:07:00 +0100
commit9e22a3cccf69a54384767c8d2f22b4badcdab36c (patch)
tree2e4fbb67ac410227c20309f999822745fbbfd83d /bitbake/lib/bb/fetch2/gitsm.py
parentb5597638c7f25daa14f6c439b5af4fbb02267dd7 (diff)
downloadpoky-9e22a3cccf69a54384767c8d2f22b4badcdab36c.tar.gz
bitbake: Fix npm to use https rather than http
Hit this error while building nlf-native recently: { "error": { "summary": "URI malformed", "detail": "" } } Some poking about led me to discover that: 1) The npm.py tool replaces npm:// with http://, not https:// 2) Some versions of the npm tool don't handle 301 redirects properly, choosing to display the above error instead when using the default nodejs registry It would be good to go fix npm to handle the redirect properly, but it seems like it would also be good to assume secure http when contacting a registry, hence, this patch (Bitbake rev: 2cd76e8aabe4e803c760e60f06cfe1f470714ec7) Signed-off-by: Neil Horman <nhorman@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/fetch2/gitsm.py')
0 files changed, 0 insertions, 0 deletions