Bug 1358245
| Summary: | repoquery: valid use of stderr and stdout, use stdout only for requested data | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pavel Raiskup <praiskup> |
| Component: | dnf | Assignee: | rpm-software-management |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | low | ||
| Version: | 24 | CC: | jmracek, mluscon, ngompa13, packaging-team-maint, pmatilai, pnemade, RadekHolyPublic, rpm-software-management, vmukhame |
| Target Milestone: | --- | Keywords: | EasyFix, Reopened, Triaged, UserExperience |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | dnf-2.0.1-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-10 10:57:33 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
Pavel Raiskup
2016-07-20 10:40:11 UTC
I would like to inform you about possibility to use -q or --quiet option. In combination with a non-interactive command it shows just the relevant content. It suppresses messages notifying about current state or actions of DNF. It should solve the problem, therefore I am closing the bug. Please if you will find any further problem, don't hesitate to report it. I'm thinking that reporter is correct. Fixed in PR: https://github.com/rpm-software-management/dnf/pull/673 If anything else appear in stdout, please report it again. This seems like a terrible idea. It might just be better to have a flag for suppressing info messages as well as warnings, etc. (I thought we do with --quiet?) Warnings are for potential problems, not informational messages. The behavior done in PR 673 should be reverted. (In reply to Neal Gompa from comment #4) > This seems like a terrible idea. It might just be better to have a flag for > suppressing info messages as well as warnings, etc. (I thought we do with > --quiet?) Well, that's different thing. The idea was about moving some writes from stdout to stderr, so stdout is (ideally) easily parseable. > Warnings are for potential problems, not informational messages. The > behavior done in PR 673 should be reverted. Thanks for the point, I tend to agree - this is not the ideal fix. Ok, but this is not the first change of that kind. The information about Last metadate ... is now also on stderr. Also -q option behave differently. Now it suppress all (info, debud, warning, error, critical), but originally it only suppress info. From my point of view if output of repoquery is used for any script, it should use -q option, therefore any adjustments are nonsense. We can really play with it, but one user will request that and another something different. I took this bug as an advice only.
That's how things work in our GNU/Linux ecosystem (at least) .. data goes
to stdout, and warnings/errors go to stderr -> which makes it trivial to parse
what I ask for and to suppress warnings by '2>/dev/null' (-q is not important
usually, unless you want to suppress some stdout output, too).
> We can really play with it, but one user will request that and another
> something different.
I believe that the behavior I explained is what random hacker would expect,
but that's really just a matter of quality of implementation, not a huge deal.
Neither a blocker of any kind for me - with a bit of carefulness I can
parse the output anyway or hack my own repoquery-like script in python
as a replacement for repoquery, it is just not that convenient.
So pick the resolution arbitrarily.
My 5c: The original yum-based repoquery was first and foremost designed for as a scripting tool in the traditional unix sense - zero extra output *by default*, errors to stderr and none of the interactive-text-ui-thing that yum itself is/was. Like yum, dnf provides list and search etc commands for interactive work, with progress reports and all that. So please preserve the hardcore scripting orientation in repoquery, it always was a specialized tool just for that. Well here is the new solution: https://github.com/rpm-software-management/dnf/pull/681 Fixed in dnf-2.0.1-1 and released into rawhide |