Univention Bugzilla – Bug 40005
App Center cancels update if no packages are affected
Last modified: 2016-03-02 13:25:58 CET
Some apps ship packages that are only installed on a subset of app installations. If those (and only those) packages are updated in a new version of an app, those systems that do not have them installed cannot update the app:
The frontend asks the backend for the changes in a dry_run call. The dry_run yields "nothing to do" as no packages are to be updated. So the frontend cancels the process without saying "whatever, set the component!"
This results in the App still marked as to-be-updated as the component is not set to the newest version.
Note that on the command line, this is easy to fix. This is a frontend problem due to the dry_run.
The dry-run seems to need some re-thinking. Bug #38396.
dry_run must always return can_continue = False otherwise the page which shows the changes is not shown. Now this page is shown which tells 'No package changes' but offers to continue. (Are you okay with that sentence, otherwise I can replace it by 'No package changes are going to happen but the app meta information gets updated.' or something like this.
r67671 | Bug #40005: don't stop installation/upgrading if no package changes are going to happen
r67672 | YAML Bug #40005
Works great. Wording is fine until we get feedback stating otherwise.