The design here is different from the download progress, yes. The
download progress has to deal with potentially long times whereas the
cache unlocking only needs to wait for a number of seconds you can count
(unless it's waiting indefinitely..., but even then I'd expect you'd
have stopped earlier and revisited that later), its also closely related
to percentage with the maximum of 120 in non-interactive cases.
I believe that for the max timeout of 120s a seconds based approach
makes more sense, and arguably we need that for the interactive one for
consistency too. In terms of progress, this also jumps around less.
I have not analysed this further, but I also vaguely recall some size
constraints in terms of the length of the string and how it fits into
standard 80 character width terminal.
** Changed in: apt (Ubuntu)
Status: New => Opinion
** Changed in: apt (Ubuntu)
Status: Opinion => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909729
Title:
Remaining time while running "sudo apt upgrade"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1909729/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
