Patti Vacek
Patti Vacek
> > It does say that the value is optional, yes, but to me that does not mean it is _optionally accurate_. I would expect it to be the exact...
> We don't need to check the length of the targets metadata (which is optional in the snapshot metadata), but we [do](https://uptane.github.io/uptane-standard/uptane-standard.html#verify_image) ask to check the length of a target...
> does anyone have strong objections about this? That sounds like a valid use case, even if I don't remember exactly who asked for it. :) No objections myself, although...
Kirkstone is supported in [the uptane namespace](https://github.com/uptane/meta-updater/pull/13). FYI I'm not sure if anyone is maintaining the repo in this namespace anymore. See also https://github.com/advancedtelematic/meta-updater/issues/825. FYI I currently still only use...
> How do you mean by others? You mean other team members that are working on meta-updater? The original team that created this repo no longer exists. I happen to...
> Are you sure kirkstone is supported? Yes, to the extent that [there's a branch for it](https://github.com/uptane/meta-updater/tree/kirkstone). Others are using it, including for production purposes, to my understanding. See for...
> The build is failing with as it seems I am missing some checksum for the ostree.git. That's strange. These days the main OSTree recipe lives in meta-openembedded, so meta-updater...
I recommend using the latest version of the bitbake manual: https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html. 1.6 is pretty old at this point.
I think it's still an open question if it's really appropriate the use ORT on Yocto in the first place. In our case, we provide [meta-updater](https://github.com/advancedtelematic/meta-updater/) and some additional supporting...