This is upgradepath changes. It will also need accompanying libtaskotron changes.
Details
- Reviewers
lbrabec tflink jskladan - Maniphest Tasks
- T558: Test libtaskotron against bodhi 2.0
- Commits
- rUPGR6d87567ba663: update for bodhi 2.0
I ran it manually against staging Bodhi 2.0, it seemed to work (a lot of updates were not found, because its data set is different I guess).
Diff Detail
- Repository
- rUPGR task-upgradepath
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Questions about the bodhi-related changes to libtaskotron - I thought we didn't need to worry about whether or not an update had an updateid/alias anymore
upgradepath.py | ||
---|---|---|
90–91 | Is this needed anymore? I thought that bodhi12 was assigning an updateid (or alias?) to updates on creation instead of at push time. can we just ignore the title? | |
567 | same question as above - do we need to have the title as a backup anymore? |
upgradepath.py | ||
---|---|---|
90–91 | It seems that updateid was renamed to alias, at least I haven't seen updateid anywhere. If Luke confirms that alias exists for all update objects, then yes, we can get rid of falling back to title. |
upgradepath.py | ||
---|---|---|
90–91 | Confirmed by Luke. I'll amend the patch. |
Is this needed anymore? I thought that bodhi12 was assigning an updateid (or alias?) to updates on creation instead of at push time. can we just ignore the title?