Bug 36252 - Info about package download for the appliance mode
Info about package download for the appliance mode
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: System setup
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UCS maintainers
:
: 36840 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-21 21:15 CEST by Stefan Gohmann
Modified: 2019-01-03 07:16 CET (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2014-10-21 21:15:19 CEST
Currently, if the Administrator aborts the system setup installation via CTRL-Q, the startwithfirefox prgram downloads the packages and prepares the appliance mode. This must be done before the sources.list file is regenerated.

The user should get more information about the progress since it takes some seconds. I think the whole steps could be moved to the di-univention-system-setup.postinst file.
Comment 1 Stefan Gohmann univentionstaff 2014-11-18 22:29:08 CET
*** Bug 36840 has been marked as a duplicate of this bug. ***
Comment 2 Stefan Gohmann univentionstaff 2014-11-19 10:01:57 CET
*** Bug 36855 has been marked as a duplicate of this bug. ***
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:16:11 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.