Univention Bugzilla – Full Text Bug Listing |
Summary: | App Center needs to use the target version during release upgrade | ||
---|---|---|---|
Product: | UCS | Reporter: | Stefan Gohmann <gohmann> |
Component: | UMC - App-Center | Assignee: | Dirk Wiesenthal <wiesenthal> |
Status: | CLOSED FIXED | QA Contact: | Florian Best <best> |
Severity: | enhancement | ||
Priority: | P5 | CC: | hahn, jmm, wiesenthal |
Version: | UCS 3.1 | ||
Target Milestone: | UCS 3.2-0-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
What kind of report is it?: | --- | What type of bug is this?: | --- |
Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
User Pain: | Enterprise Customer affected?: | ||
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | ||
Max CVSS v3 score: | |||
Bug Depends on: | |||
Bug Blocks: | 33535, 33549 | ||
Attachments: | Parse updater.status file to get next_version. |
Description
Stefan Gohmann
2013-11-22 20:23:50 CET
The App Center already uses the variable (knowing that it is unset at the moment). There it is called "version/version/target". If the variable is named differently, it has to be adapted in the App Center, too. Created attachment 5774 [details] Parse updater.status file to get next_version. The information is already available since Bug #14346 for local programs through /var/lib/univention-updater/univention-updater.status and also for the UMC via the UMCP-Command updater/installer/status: # ucr set version/version=3.1 # univention-upgrade ^Z # umc-command -r -U Administrator -P univention -o job=release updater/installer/status ... RESULT : { '_current_version_': '3.1-0', '_next_version_': '3.1-1', '_status_': 'RUNNING', ... 'statusfile': '/var/lib/univention-updater/univention-updater.status'} If I remember correctly there were some very tricky problem with using UCR during updates (Bug #23202): With the update from UCS-2.4 with Python2-4 to UCS-3.0 with Python-2.6 we had the situation, where the still running Updater was still using the old UCR-implementation, which was already partly removed and replaced with the 3.0 version. Therefore I don't very much like to add setting UCR variables during the update. See attached patch for an alternative to parse the updater status file. Move bug back to App-Center: parsing the file is okay, but needs additional caching. Fixed in univention-management-console-module-appcenter 3.0.50-20.232.201402051242 UCS Version is read from /var/lib/univention-updater/univention-updater.status. The value is cached but uncached when all applications should be re-read (done when opening the App Center). The version should not change so this is probably too much uncaching. Scripts like postinst and joinscripts would get the correct version anyway. But it _may_ be that someone uses the Software Updater to run a release update and open the App Center at the same time. Not very common but just in case, this could lead to extensive network load if not false results. OK, the next version is correctly detected and packages are downloaded from that /meta-inf. |