You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Uptane org maintains the meta-updater layer but lacks the target devices to demo the technology. These bsp layers still lies under the advancedtelematic github repo but are outdated.
For testing purpose I revived the updater-repo repository (manifests) and the meta-updater-qemux86-64 layer repository to latest poky/oe-core.
Will you be interested to host the 2 repositories in order to have a test bed for PR and reduce the barrier to entry?
Eventually, I'm also interested to contribute a qemuarm64 machine (not done yet).
The text was updated successfully, but these errors were encountered:
I think it would not at all be a bad idea to host those repos (and meta-updater-raspberrypi) in the Uptane namespace.
@tkfu@JustinCappos what do you think? Who else might we need to consider?
Honestly at this point I wonder if we couldn't ask Here to move some of the repos directly here, instead of having them forked or copied. It's not a big deal, but if they're not really supporting those repos anymore, it doesn't make sense to keep the "originals" there.
Wonder if it would be better to just merge qemu (x86 and arm) support as part of meta-updater itself? Qemu bsp is kind of special and it is quite useful for testing purposes, and it is also the standard bsp supported by oe-core.
Hi,
Uptane org maintains the meta-updater layer but lacks the target devices to demo the technology. These bsp layers still lies under the advancedtelematic github repo but are outdated.
For testing purpose I revived the updater-repo repository (manifests) and the meta-updater-qemux86-64 layer repository to latest poky/oe-core.
Will you be interested to host the 2 repositories in order to have a test bed for PR and reduce the barrier to entry?
Eventually, I'm also interested to contribute a qemuarm64 machine (not done yet).
The text was updated successfully, but these errors were encountered: