Bug 836751
Summary: | PackageKit doesn't report download progress | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andre Cunha <andre.lv.cunha> |
Component: | PackageKit | Assignee: | Richard Hughes <hughsient> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | greta_watson, hugh, hughsient, jonathan, rdieter, rhughes, rvitale, smparrish |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-10 16:56:36 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andre Cunha
2012-06-30 22:32:21 UTC
This is disabled on purpose, since the PackageKit-yum backend time estimation isn't very good (apparently, I don't know the full history behind it, only that fedora carries a patch for it). Feel free to enable it yourself, set in /etc/PackageKit/PackageKit.conf UseRemainingTimeEstimation=true I've searched the Web, and found that the spec file for PackageKit 0.7.4 in Fedora 17 has these lines: # Fedora specific: the yum backend doesn't do time estimation correctly Patch1: PackageKit-0.4.4-Fedora-turn-off-time.conf.patch The mentioned patch disables the time estimation in /etc/PackageKit/PackageKit.conf: # enough and will not be set at the very start or end of a transaction. # # default=true -UseRemainingTimeEstimation=true +UseRemainingTimeEstimation=false So it really seems that the yum backend doesn't do remaining time estimation correctly. I hope this be fixed in future releases. Thank you very much for your help! Was the original request to show the files as they are being downloaded? That is what I would like to see. For example: ... downloaded <whatever package> downloading <whatever is currently being downloaded> This is being done during the update and clean up phases, but not during the download phase. If yum is done from the command line, then the files are listed as they are being downloaded, as they are being installed or updated, and as they are being cleaned up. (In reply to comment #3) > Was the original request to show the files as they are being downloaded? > That is what I would like to see. For example: > > ... > downloaded <whatever package> > downloading <whatever is currently being downloaded> > > This is being done during the update and clean up phases, but not during the > download phase. > > If yum is done from the command line, then the files are listed as they are > being downloaded, as they are being installed or updated, and as they are > being cleaned up. Exactly! This was precisely what I meant. I believe it would be good to visualize, if it is possible, the individual progress also in the download phase. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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. For Fedora 21 we've switched to the hawkey backend, and that performs much better with time and percentage updates working well. (In reply to Richard Hughes from comment #6) > For Fedora 21 we've switched to the hawkey backend, and that performs much > better with time and percentage updates working well. Excellent! Thank you very much. |