Bug 1198975

Thanks for the report. The size of DRPMs is contained in prestodelta metadata so it should be possible to show the progress. Although the downloading of deltas are usually that fast that you would not see the progress bar.

Hi, I think you misunderstood me. I'm talking about showing how many DRPMs have already been reconstructed into RPMs and how many of them are still waiting to be reconstructed. So I'm *not* talking about a progress bar of a) a single DRPM->RPM reconstruction phase b) anything related to downloading.

Look at the sample output snippet I posted above. This happens after all downloading is complete.

This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

*** Bug 1242588 has been marked as a duplicate of this bug. ***

Jan Silhan wrote:

> Thanks for the report. The size of DRPMs is contained in prestodelta
> metadata so it should be possible to show the progress.

Excelent.

> This bug appears to have been reported against 'rawhide' during the Fedora 
> 23 development cycle.
> Changing version to '23'.

As reported in my bug 1242588, it also happens in Fedora 22.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

I am sorry but we cannot implement that. According to my research some of DRPM are created before last package is downloaded, therefore I don't know how many elements will be in queue. Therefore the counter will not know how many elements will be there, because not for all packages downloaded drpms are available.

So why not do this?

# so far we downloaded 3 DRPMs, unclear how many more we will download. first was assembled.
[DRPM 1/3+] XXX: done
# so far we downloaded 7 DRPMs, unclear how many more we will download. second was assembled.
[DRPM 2/7+] XXX: done
# third was assembled
[DRPM 3/7+] XXX: done
# we've downloaded 15 DRPMs and we know we won't download any more. fourth was assembled.
[DRPM 4/15] XXX: done
...
# last one was assembled
[DRPM 15/15] XXX: done


Or if this is easier for you:
[DRPM 1/?] XXX: done
[DRPM 2/?] XXX: done
[DRPM 3/?] XXX: done
[DRPM 4/15] XXX: done
...
[DRPM 15/15] XXX: done

Ok, here is PR https://github.com/rpm-software-management/dnf/pull/790

I found an impossible and it should work like it was originally requested. Unfortunately it requires change in API.

dnf-plugins-extras-2.0.1-1.fc26 dnf-plugins-core-2.1.0-1.fc26 libdnf-0.9.0-1.fc26 dnf-2.5.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-92e5a01da8

dnf-2.5.0-1.fc26, dnf-plugins-core-2.1.0-1.fc26, dnf-plugins-extras-2.0.1-1.fc26, libdnf-0.9.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-92e5a01da8

dnf-2.5.0-1.fc26 dnf-plugins-core-2.1.0-1.fc26 dnf-plugins-extras-2.0.1-1.fc26 dnfdaemon-0.3.17-3.fc26 libdnf-0.9.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-92e5a01da8

dnf-2.5.0-2.fc26 dnf-plugins-core-2.1.0-1.fc26 dnf-plugins-extras-2.0.1-1.fc26 dnfdaemon-0.3.18-1.fc26 libdnf-0.9.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-92e5a01da8

dnf-2.5.0-2.fc26, dnf-plugins-core-2.1.0-1.fc26, dnf-plugins-extras-2.0.1-1.fc26, dnfdaemon-0.3.18-2.fc26, libdnf-0.9.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-92e5a01da8

dnf-2.5.0-2.fc26, dnf-plugins-core-2.1.0-1.fc26, dnf-plugins-extras-2.0.1-1.fc26, dnfdaemon-0.3.18-2.fc26, libdnf-0.9.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.