Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1161950
Summary: | [visual] output and progress bar not visible during package downloads specified by remote url | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Antonio T. (sagitter) <anto.trande> |
Component: | dnf | Assignee: | Michal Luscon <mluscon> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | low | ||
Version: | 25 | CC: | akozumpl, anto.trande, bugzilla, elad, jmracek, jzeleny, lantw44, mluscon, packaging-team-maint, ptoscano, rjones, tla |
Target Milestone: | --- | Keywords: | Reopened, Triaged, UserExperience |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | dnf-2.4.0-1.fc26 dnf-2.6.2-1.fc26 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-07-25 16:56:06 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: | |||
Bug Depends On: | |||
Bug Blocks: | 910269, 1156498 |
Description
Antonio T. (sagitter)
2014-11-09 17:15:11 UTC
Thanks for the report, we'll take a look. I just hit this as well, when working on improving the usage of dnf in supermin (#1156498). From a very cursory glance, could it be dnf/cli/output.py: def setup_progress_callbacks(self): """Set up the progress callbacks and various output bars based on debug level. """ progressbar = None if self.conf.debuglevel >= 2 and sys.stdout.isatty(): progressbar = dnf.cli.progress.MultiFileProgressMeter(fo=sys.stdout) self.progress = dnf.cli.progress.MultiFileProgressMeter(fo=sys.stdout) # setup our depsolve progress callback return (progressbar, DepSolveProgressCallBack()) and indeed: $ dnf download -vvv tree.x86_64 cachedir: /var/tmp/dnf-pino-S9P5Sa/x86_64/22 Loaded plugins: copr, playground, download, Query, kickstart, generate_completion_cache, debuginfo-install, builddep, noroot, protected_packages DNF version: 0.6.2 repo: using cache for: rawhide not found updateinfo for: Fedora - Rawhide - Developmental packages for the next Fedora release tree-1.7.0-3.fc22.x86_64.rpm [...] 7.7 MB/s | 55 kB 00:00 $ dnf download -vvv tree.x86_64 &> out $ cat out cachedir: /var/tmp/dnf-pino-S9P5Sa/x86_64/22 Loaded plugins: copr, playground, download, Query, kickstart, generate_completion_cache, debuginfo-install, builddep, noroot, protected_packages DNF version: 0.6.2 repo: using cache for: rawhide not found updateinfo for: Fedora - Rawhide - Developmental packages for the next Fedora release Even if not outputting things like speed as they change, at least getting feedback on what is happening would be nice (and needed actually, otherwise dnf is basically undebuggable when run in some automated way). Hi Pino, any reason why is this visual drawback a blocker? (In reply to Jan Silhan from comment #3) > Hi Pino, any reason why is this visual drawback a blocker? Because running dnf with its output e.g. piped to a file means that that log file would have no information about what was done by dnf; see also comment #0. YMMV, but personally I don't find it useful that the actual "useful" parts of dnf output get nullified when the output is not a tty. *** Bug 1222011 has been marked as a duplicate of this bug. *** Since Michal assigned the duplicate to himself, I'm assigning this to him as well. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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. Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. remote packages should be treated the same as any package downloaded from repository. *** Bug 1294953 has been marked as a duplicate of this bug. *** Still reproduceable in current rawhide, with the same example of comment #2. This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'. I try to implement it in pull request: https://github.com/rpm-software-management/dnf/pull/778 . Hope that it helps dnf-plugins-core-2.0.0-1.fc26 libdnf-0.8.2-1.fc26 dnf-2.4.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4e95959f0d dnf-2.4.0-1.fc26 dnf-plugins-core-2.0.0-1.fc26 dnf-plugins-extras-2.0.0-1.fc26 libdnf-0.8.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4e95959f0d dnf-2.4.0-1.fc26, dnf-plugins-core-2.0.0-1.fc26, dnf-plugins-extras-2.0.0-1.fc26, libdnf-0.8.2-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-4e95959f0d dnf-2.4.0-1.fc26, dnf-plugins-core-2.0.0-1.fc26, dnf-plugins-extras-2.0.0-1.fc26, libdnf-0.8.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. This can be still reproduced in current rawhide, with the same example of comment #2 -- using dnf-2.5.0-2.fc27.noarch. I create pull-request that should solve the problem from Comment 2 (https://github.com/rpm-software-management/dnf/pull/833). Anyone that could test it is more then welcome. libdnf-0.9.3-1.fc26 dnf-plugins-core-2.1.3-1.fc26 dnf-2.6.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-6f4c06b2d7 dnf-2.6.2-1.fc26, dnf-plugins-core-2.1.3-1.fc26, libdnf-0.9.3-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-6f4c06b2d7 dnf-2.6.2-1.fc26, dnf-plugins-core-2.1.3-1.fc26, libdnf-0.9.3-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |