<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-updater.git/conf, branch feat/2020.4</title>
<subtitle>Mirror of github.com/advancedtelematic/meta-updater</subtitle>
<id>https://git.enea.com/cgit/linux/meta-updater.git/atom?h=feat%2F2020.4</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-updater.git/atom?h=feat%2F2020.4'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/'/>
<updated>2020-01-30T15:07:07+00:00</updated>
<entry>
<title>meta: move HOSTTOOLS definitions to sota.conf.inc</title>
<updated>2020-01-30T15:07:07+00:00</updated>
<author>
<name>Ming Liu</name>
<email>liu.ming50@gmail.com</email>
</author>
<published>2020-01-26T21:14:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=3a2fecfc1d78e4b161f7180f35fc7d0a1a967ae6'/>
<id>urn:sha1:3a2fecfc1d78e4b161f7180f35fc7d0a1a967ae6</id>
<content type='text'>
HOSTTOOLS and HOSTTOOLS_NONFATAL are global variables that being
handled in base_eventhandler, so they must be defined in config files
or in INHERIT classes or classes being inherited by base.bbclass, or
else we might run into the following problems:
```
$ bitbake pkgname
$ bitbake imgname
```

the HOSTTOOLS and HOSTTOOLS_NONFATAL in the above image recipe, for
instance, 'repo python' in image_repo_manifest.bbclass, they would not
be copied to HOSTTOOLS_DIR.

Signed-off-by: Ming Liu &lt;liu.ming50@gmail.com&gt;
</content>
</entry>
<entry>
<title> build and run image without ostree support for qemux86-64</title>
<updated>2020-01-20T21:00:41+00:00</updated>
<author>
<name>Kostiantyn Bushko</name>
<email>kbushko@intellias.com</email>
</author>
<published>2020-01-17T11:37:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=ad01ab114dd83edda61c06aa01fd899c80ee0a68'/>
<id>urn:sha1:ad01ab114dd83edda61c06aa01fd899c80ee0a68</id>
<content type='text'>
Signed-off-by: Kostiantyn Bushko &lt;kbushko@intellias.com&gt;
</content>
</entry>
<entry>
<title>Force a simple reproducible build mechanism</title>
<updated>2019-12-04T10:46:30+00:00</updated>
<author>
<name>Laurent Bonnans</name>
<email>laurent.bonnans@here.com</email>
</author>
<published>2019-12-04T10:39:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=af1694c7044aee54761750080819d5c5d6ce09e4'/>
<id>urn:sha1:af1694c7044aee54761750080819d5c5d6ce09e4</id>
<content type='text'>
In 25a17f0346ab05b3212bb280e4a8b622bcf99bce, poky sets
reproducible_build by defaults. However, it is quite complex as it tries
to compute a plausible timestamp from source files, in a reproducible
ways.

Setting the timestamps to 0, just like ostree, is probably safer in our
case, so let's switch to our old behavior.

Signed-off-by: Laurent Bonnans &lt;laurent.bonnans@here.com&gt;
</content>
</entry>
<entry>
<title>OTA-3988: Split the local.conf to a base and a distro specific part</title>
<updated>2019-11-06T12:35:34+00:00</updated>
<author>
<name>Mykhaylo Sul</name>
<email>ext-mykhaylo.sul@here.com</email>
</author>
<published>2019-11-06T08:44:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=c74c4eb5399ed7a195e00172774a283582da6e44'/>
<id>urn:sha1:c74c4eb5399ed7a195e00172774a283582da6e44</id>
<content type='text'>
Signed-off-by: Mykhaylo Sul &lt;ext-mykhaylo.sul@here.com&gt;
</content>
</entry>
<entry>
<title>OTA-3988: make the DISTRO value in poky-sota-systemd.conf aligned to the systemd case</title>
<updated>2019-11-05T16:35:43+00:00</updated>
<author>
<name>Mykhaylo Sul</name>
<email>ext-mykhaylo.sul@here.com</email>
</author>
<published>2019-11-05T16:35:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=3f904325ad5d307f308e020e9bc4d24a8afdf7af'/>
<id>urn:sha1:3f904325ad5d307f308e020e9bc4d24a8afdf7af</id>
<content type='text'>
Signed-off-by: Mykhaylo Sul &lt;ext-mykhaylo.sul@here.com&gt;
</content>
</entry>
<entry>
<title>OTA-3988: force an ostree boot indication only in case of non-systemd distro</title>
<updated>2019-11-05T09:09:25+00:00</updated>
<author>
<name>Mykhaylo Sul</name>
<email>ext-mykhaylo.sul@here.com</email>
</author>
<published>2019-11-05T08:17:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=40153ba5d77a83e78a9b844a8117b44be8b55df0'/>
<id>urn:sha1:40153ba5d77a83e78a9b844a8117b44be8b55df0</id>
<content type='text'>
Signed-off-by: Mykhaylo Sul &lt;ext-mykhaylo.sul@here.com&gt;
</content>
</entry>
<entry>
<title>OTA-3988: Non-systemd/poky-sota local.conf</title>
<updated>2019-11-01T10:02:30+00:00</updated>
<author>
<name>Mykhaylo Sul</name>
<email>ext-mykhaylo.sul@here.com</email>
</author>
<published>2019-11-01T10:02:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=6680bfb70ce2285ef5243e489073fb26bc63f0e7'/>
<id>urn:sha1:6680bfb70ce2285ef5243e489073fb26bc63f0e7</id>
<content type='text'>
Signed-off-by: Mykhaylo Sul &lt;ext-mykhaylo.sul@here.com&gt;
</content>
</entry>
<entry>
<title>aktualizr-device-prov-creds: remove it.</title>
<updated>2019-10-18T11:34:13+00:00</updated>
<author>
<name>Patrick Vacek</name>
<email>patrickvacek@gmail.com</email>
</author>
<published>2019-10-17T15:01:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=3f70b2d2f4a3a2fb50be4b8c395d9d09b0853f1a'/>
<id>urn:sha1:3f70b2d2f4a3a2fb50be4b8c395d9d09b0853f1a</id>
<content type='text'>
Originally I was just trying to remove the reference to DEPLOY_DIR_IMAGE
because it depends on MACHINE, but then I realized that this recipe is
just plain not worth keeping. It isn't viable for anything except the
most limited testing, since it bakes device-specific credentials into an
image, but we weren't even using it for testing.

Signed-off-by: Patrick Vacek &lt;patrickvacek@gmail.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: Update LAYERDEPENDS_sota.</title>
<updated>2019-10-17T15:03:38+00:00</updated>
<author>
<name>Patrick Vacek</name>
<email>patrickvacek@gmail.com</email>
</author>
<published>2019-10-14T10:30:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=d1118a121810c5c76e33a63909d43b4e25439250'/>
<id>urn:sha1:d1118a121810c5c76e33a63909d43b4e25439250</id>
<content type='text'>
It was missing a few dependencies.

Signed-off-by: Patrick Vacek &lt;patrickvacek@gmail.com&gt;
</content>
</entry>
<entry>
<title>aktualizr: use SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS for config recipes.</title>
<updated>2019-10-17T15:03:38+00:00</updated>
<author>
<name>Patrick Vacek</name>
<email>patrickvacek@gmail.com</email>
</author>
<published>2019-10-14T10:06:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-updater.git/commit/?id=837b2fc0f2ccf6d334ebf026a44f3ea0f83323a7'/>
<id>urn:sha1:837b2fc0f2ccf6d334ebf026a44f3ea0f83323a7</id>
<content type='text'>
This is a bit of a compromise. These recipes are allarch, since they do
not depend on an architecture, but they depend on aktualizr, which is
definitely not allarch. Therefore, we must tell bitbake not to treat the
aktualizr architecture as a dependency of these recipes.

However, this means that if one of the config files changes in the
aktualizr repo, we need to bump the version of the recipe that uses it
to make sure bitbake picks up that change.

Signed-off-by: Patrick Vacek &lt;patrickvacek@gmail.com&gt;
</content>
</entry>
</feed>
