Your message dated Tue, 5 Apr 2016 18:27:00 +0100
with message-id <[email protected]>
and subject line Re: seconds remaining methods differ update vs. upgrade
has caused the Debian Bug report #717580,
regarding seconds remaining methods differ update vs. upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
717580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717580
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.8.2-1
Severity: minor
Problem: the time estimation of remaining seconds shown at the right during
aptitude update
differs from that shown during aptitude safe-upgrade.
The former is per-line, and the latter is per-whole-upgrade (or maybe
per-upstream-server?!*).
Naturally the latter method is preferred, lest one tell one's boss "Oh,
only two minutes left", when that is merely for this line, and he will
be waiting downstairs much longer than that!
Now of course one could say one cannot estimate for more than one
upstream server at a time due to ... ...
*Anyway perhaps prefix the time estimate with the server name so it is
clear what is going on.
Anyway this all needs to be made unambiguous to somebody watching it
tick along.
--- End Message ---
--- Begin Message ---
severity 717580 wishlist
tags 717580 + wontfix
stop
2013-07-22 18:05 [email protected]:
Package: aptitude
Version: 0.6.8.2-1
Severity: minor
Problem: the time estimation of remaining seconds shown at the right during
aptitude update
differs from that shown during aptitude safe-upgrade.
The former is per-line, and the latter is per-whole-upgrade (or maybe
per-upstream-server?!*).
Naturally the latter method is preferred, lest one tell one's boss "Oh,
only two minutes left", when that is merely for this line, and he will
be waiting downstairs much longer than that!
Now of course one could say one cannot estimate for more than one
upstream server at a time due to ... ...
*Anyway perhaps prefix the time estimate with the server name so it is
clear what is going on.
Anyway this all needs to be made unambiguous to somebody watching it
tick along.
This is not a bug, not even minor, but the way that downloads work with
the current implementation. Besides, it comes from libapt, and aptitude
doesn't have any knowledge of files remaining to be donwnloaded, or
where from, and it doesn't estimate the time itself. It just prints
information coming from libapt.
At most this is a wishlist to make it work in a different way, which I
am marking as +wontfix (and closing, no use in having hundreds of
non-bugs opened for years that nobody is working to address).
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
