Bug 2332931 - Remaining time to download is negative
Summary: Remaining time to download is negative
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf5
Version: 41
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Petr Pisar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-12-17 22:21 UTC by Jeffrey Walton
Modified: 2025-01-11 01:42 UTC (History)
7 users (show)

Fixed In Version: dnf5-5.2.8.1-4.fc42 dnf5-5.2.8.1-3.fc41
Clone Of:
Environment:
Last Closed: 2025-01-11 01:42:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rpm-software-management dnf5 issues 1963 0 None open Remaining time to download is negative 2024-12-18 11:31:04 UTC

Description Jeffrey Walton 2024-12-17 22:21:26 UTC
There's a user on fedora-users mailing list who is upset that dnf5 starts at a negative time, and counts up to 0. See "DNF Stats Issue," <https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/NOJIIFRBDAQKGJKCCGWFM43INBRF7D4U/>.

Please consider adding an option to provide previous behavior of counting down to 0.


Reproducible: Always

Steps to Reproduce:
Run `dnf upgrade`.
Actual Results:  
Start at a negative time, and count up to 0.

Expected Results:  
Start at a positive time, and count down to 0.

I did not see an option in the dnf5 man pages, or the upgrade plugin man pages. My apologies if I missed it.

Comment 1 Petr Pisar 2024-12-18 10:57:06 UTC
I'm not sure the negative are a feature. Maybe it's a plain bug and instead of adding new configuration option the counting should be changed.

Comment 2 Petr Pisar 2024-12-18 11:25:06 UTC
An example. Observe the "-03h18m" value in the last column:

# dnf --setopt=optional_metadata_types=filelists makecache --refresh
Updating and loading repositories:
 Fedora 42 on Koji                          1% [                  ] |   4.9 KiB/s | 854.1 KiB | -03h18m

This is bug.

Comment 3 Evan Goode 2024-12-20 18:05:53 UTC
It seems to have been implemented intentionally years ago, but I agree with you and Petr that it's unusual and should be changed. I filed https://github.com/rpm-software-management/dnf5/pull/1971.

Comment 4 Fedora Update System 2025-01-09 12:46:48 UTC
FEDORA-2025-f3bc917e71 (dnf5-5.2.8.1-3.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f3bc917e71

Comment 5 Fedora Update System 2025-01-10 03:12:05 UTC
FEDORA-2025-f3bc917e71 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-f3bc917e71`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f3bc917e71

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2025-01-11 01:42:40 UTC
FEDORA-2025-f3bc917e71 (dnf5-5.2.8.1-3.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


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