On 06/06/2017 06:11 PM, Julian Andres Klode wrote:
>
> I'm not sure what you mean. The entire output is shown to the
> user - we don't hide anything.
>
Sorry, user error (i.e. me). Please close.
Regards
Harri
On Tue, Jun 06, 2017 at 11:22:53AM +0200, Harald Dunkel wrote:
> On 06/01/2017 09:02 AM, Julian Andres Klode wrote:
> >
> > What would you want us to show? Obviously, we do not know
> > what is happening - the postinst script could in fact be
> > hanging. We could display a progress par that steps
Maybe a verbose option "apt -v" would do, showing
the dpkg output.
A busybee could read the output of dpkg, rotating
for every new line dpkg has written.
Just a suggestion, of course.
Harri
On 06/01/2017 09:02 AM, Julian Andres Klode wrote:
>
> What would you want us to show? Obviously, we do not know
> what is happening - the postinst script could in fact be
> hanging. We could display a progress par that steps one
> further and then back or something, but that might give
> a wrong
On Thu, Jun 01, 2017 at 07:56:37AM +0200, Harald Dunkel wrote:
> Package: apt
> Version: 1.0.9.8.4
>
> Some postinst scripts (e.g. building kernel modules) take
> a few minutes to complete, even on a fast machine. Thats
> a long time for not increasing the progress bar on running
> "apt install".
Package: apt
Version: 1.0.9.8.4
Some postinst scripts (e.g. building kernel modules) take
a few minutes to complete, even on a fast machine. Thats
a long time for not increasing the progress bar on running
"apt install".
Makes me really nervous, so I prefer aptitude over apt.
This could be impro
6 matches
Mail list logo
