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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Did anybody yet test if the autoupdater works for v10?
My tests had an issue resulting some kind of "no matching image"-message (did not capture it), despite the fact that it was well present in the manifest.
f292ba1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did anybody yet test if the autoupdater works for v10?
My tests had an issue resulting some kind of "no matching image"-message (did not capture it), despite the fact that it was well present in the manifest.
f292ba1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You probably generated the manifest without BROKEN=1 (when the v10 image was still guarded by the BROKEN check).
f292ba1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Adorfer Ah, sorry, I didn't read that you checked that the image was present in the manifest. Can you post the content of
/var/sysinfo/model
?f292ba1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ja, mein fehler, ich hatte das "make manifest" ohne $BROKEN aufgerufen in meinem buildscript.