9231 2016-03-09 05:01:01 +0000 npm fetcher registry handling is faulty 2016-04-18 19:29:06 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 2.0 x86 Multiple RESOLVED FIXED Medium+ normal 2.1 M4 1 bluelightning brendan.le.foll brendan.le.foll francisco.j.pedraza.gonzalez poky.bs.watcher poky.watcher richard.purdie francisco.j.pedraza.gonzalez --- --- No (bug/feature does not impact docs) oldest_to_newest 59819 0 bluelightning 2016-03-09 05:01:01 +0000 The npm fetcher attempts to construct a registry URL to pass to --registry, but unfortunately it's not doing this correctly at the moment - ud.basename ends up as '' with the result that ud.registry is 'http://'. npm doesn't seem to care, so I wonder if it's paying any attention to this option at all. Either way we need to fix all of the problems here so that registries other than the main one can actually be used. 60029 1 richard.purdie 2016-03-16 17:49:38 +0000 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=3c66619d50921a17b911f99f095baac3a049cad3 61355 2 francisco.j.pedraza.gonzalez 2016-04-18 19:29:06 +0000 Hi Paul, Could you please tell me more details in order to be able to reproduce this one?, I need to verify this. Regards,