Bug 29887 – No progress during a time-consuming postinst

Bug 29887 - No progress during a time-consuming postinst


Summary:	No progress during a time-consuming postinst

Status:	CLOSED WORKSFORME

Product:	UCS
Classification:	Unclassified
Component:	UMC - App-Center
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	Dirk Wiesenthal
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-12-21 22:43 CET by Stefan Gohmann
Modified:	2017-02-08 10:21 CET (History)
CC List:	1 user (show)

See Also:
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:

Attachments
Parse package_manager.log and present it to the frontend (1.05 KB, patch) 2012-12-29 14:33 CET, Dirk Wiesenthal	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Gohmann

2012-12-21 22:43:24 CET

UCC downloads during the installation a 1 GB image file from our download server. During this time the Admin doesn't see any progress.

It would be nice if the postinst of the app can send progress or alive messages, so that the Admin won't close the UMC session.

Comment 1 Dirk Wiesenthal

2012-12-29 14:33:49 CET

Created attachment 4951 [details]
Parse package_manager.log and present it to the frontend

This should work. The dpkg log file is read while written and the last line is presented to the frontend. You would have to somehow echo the download progress in the postinst.

Comment 2 Dirk Wiesenthal

2013-01-03 18:00:55 CET

Errata Bug#29239 required some changes in the way dpkg-output is handled. During the fix of that bug it was necessary to pass the dpkg-output to the frontend. This obsoletes this bug hopefully. You still have to echo the progress manually of course.

Comment 3 Dirk Wiesenthal

2017-02-08 10:21:43 CET

This is no longer an issue. If you feel I am wrong, please REOPEN the bug.