<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-virtualization.git/recipes-devtools/yq, branch hardknott</title>
<subtitle>Mirror of git.yoctoproject.org/meta-virtualization</subtitle>
<id>https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=hardknott</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=hardknott'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/'/>
<updated>2021-12-03T14:01:33+00:00</updated>
<entry>
<title>global: add explicit branch to all SRC_URIs</title>
<updated>2021-12-03T14:01:33+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-10-29T13:51:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=f6a52458e895c4b4e30926b08c5a95e3cb3ff9b5'/>
<id>urn:sha1:f6a52458e895c4b4e30926b08c5a95e3cb3ff9b5</id>
<content type='text'>
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 &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>yq: add SRCREV_FORMAT</title>
<updated>2021-10-20T03:28:16+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-10-20T03:18:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=c85ca05fe9035610419c18230db26fe6e8b64c6d'/>
<id>urn:sha1:c85ca05fe9035610419c18230db26fe6e8b64c6d</id>
<content type='text'>
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 &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>yq: export GO111MODULE=off</title>
<updated>2021-03-01T22:02:33+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-03-01T16:37:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=4218573b08e7cd4d5f6ed06d49165311a605d2c4'/>
<id>urn:sha1:4218573b08e7cd4d5f6ed06d49165311a605d2c4</id>
<content type='text'>
With the latest go version bump in oe-core export GO111MODULE is
on by default. Our build is not setup to use go modules, so we
disable it and avoid configuration errors:

  no required module provides package ... : working directory is not part of a module

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>devtoos: introduce 'yq'</title>
<updated>2020-10-08T14:53:39+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2020-10-08T14:53:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=96c644f896b14b246e57fbb80a7fbb86cea93d31'/>
<id>urn:sha1:96c644f896b14b246e57fbb80a7fbb86cea93d31</id>
<content type='text'>
yq is used by some builds to do command line parsing of yaml config
files.

We introduce the recipe/package and all of its dependencies.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
</feed>
