linux/meta-virtualization.git/recipes-devtools, branch master-nxtMirror of git.yoctoproject.org/meta-virtualizationhttps://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=master-nxt2021-11-08T14:18:20+00:00yq: convert github SRC_URI to use https protocol2021-11-08T14:18:20+00:00Martin JansaMartin.Jansa@gmail.com2021-11-07T17:37:23+00:00urn:sha1:1aadb327304588d62bef50969b429d6dd7669fd1
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
go-{distribution,systemd}: convert github SRC_URIs to use https protocol2021-11-07T03:05:26+00:00Martin JansaMartin.Jansa@gmail.com2021-11-05T14:58:39+00:00urn:sha1:057889e54188841ac453f44de0115383fc6b3358
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
crun/oci-image-spec: specify https in github src_uri2021-11-05T12:57:46+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-11-05T12:57:46+00:00urn:sha1:3fea81e4c58f7c0f263341a96eec2cca39e87a59
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
global: convert github SRC_URIs to use https protocol2021-11-03T13:37:00+00:00Martin JansaMartin.Jansa@gmail.com2021-11-03T08:51:23+00:00urn:sha1:baf9e1a06f116c12af46a4400edfc1aa10d3fc8b
* apply the same also for recipes using PKG_NAME starting
with github.com which the conversion script doesn't update
automatically
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
global: convert github SRC_URIs to use https protocol2021-11-02T13:57:03+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-11-02T13:24:33+00:00urn:sha1:0a7ae8bc50208a7409198a8e92c4ce4afb2b5ed3
github is removing git:// access, and fetches will start experiencing
interruptions in service, and eventually will fail completely.
bitbake will also begin to warn on github src_uri's that don't use
https. So we convert the meta-virt instances to use protocol=https
(done using the oe-core contrib conversion script)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
global: add explicit branch to all SRC_URIs2021-11-02T13:57:03+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-10-29T13:51:13+00:00urn:sha1:ac399ad09105dce73bccde9574216377613a98de
As introduced in the oe-core post:
https://lists.openembedded.org/g/openembedded-core/message/157623
SRC_URIs without an explicit branch will generate warnings, and
eventually be an error.
We run the provided conversion script to make sure that meta-virt
is ready for the change.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
yq: add SRCREV_FORMAT2021-10-20T03:21:20+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-10-20T03:18:11+00:00urn:sha1:89b1a89d9ef25b357ac31c2de5a93aecbd1a369b
recipes that use multiple SCMs in the SRC_URI, must supply
SRCREV_FORMAT or SRCPV triggers an expansion error. While
this isn't fatal during the build, it can cause issues with
setscene (and possibly) other tasks failing, which then
leads to no sstate re-use, etc.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
python3-sphinx: add specific Licenses2021-09-16T22:01:55+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-09-14T18:01:42+00:00urn:sha1:36cf756b0a829391ca3cb8c0f29bcc21d55251cd
The LICENSE field for python3-sphinx is not specific enough, and doesn't
contain all the integrated package licenses.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
python3-sphinx: update to 4.2.02021-09-16T22:01:55+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-09-14T17:53:56+00:00urn:sha1:6fed58d8cb55d4dad7c79adbe0b109e0670e64f3
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
grpc-go: update license to Apache-2.02021-09-16T22:01:55+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-09-14T17:37:30+00:00urn:sha1:fc7fb6fbaaf1b28c7ea4985507e5430f81a05332
The LICENSE was incorrect in grpc-go. According to the LICENSE file,
it is Apache-2.0, so we update the recipe accordingly.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>