managerd: fix ref used on successful upgrade
AUM does not set the right refs to the repo commit when the upgrade contains development and release entries in its ref-bindings, e.g. it will use v2022dev3 instead of v2022 if both are present.
When adding ref-bindings to a commit, OSTree sort them in default alphabetic order using strcmp().
This commit looks for the correct ref for the repo commit.
https://phabricator.apertis.org/T8609
Signed-off-by: Frédéric Danis frederic.danis@collabora.com
Merge request reports
Activity
-
Apart from that and really nitpicking, could you please make sure the new changes follow the current coding style? (space after parenthesis for function calls, function names as new line on method declarations, etc).
No need to change other places (if any) that are not being touched by the changes here but would be good to make sure new changes follow the current style.
That should make the code much nicer to read and maintain.
Edited by Andre Moreira Magalhaes mentioned in merge request !88 (merged)
mentioned in issue infrastructure/apertis-issues#77 (closed)