Description of problem: Program logs and error messages must be written to fd 2 (i.e. stderr), and the actual output to fd 1 (i.e. stdout). Doing anything else makes it very hard to use the program in a pipeline. dnf5 repoquery writes log messages to stdout. $ dnf5 repoquery 2>/dev/null | grep Repositories Repositories loaded. "Repositories loaded." is obviously not a package name. Version-Release number of selected component (if applicable): dnf5-5.0.6-1.fc39.x86_64
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
*** Bug 2223347 has been marked as a duplicate of this bug. ***
Discussed during the 2024-08-19 blocker review meeting: [1] The decision to classify this bug as a RejectedBlocker (Final) was made: "This is annoying, but we don't see anywhere it violates the release criteria. Please re-propose it with more details if there is a criteria violation we're missing." [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-08-19/f41-blocker-review.2024-08-19-15.59.log.html
This has been reported a long time ago, please repsond.
Sorry, somehow it got out of our sight. I agree this is important to resolve, though it's not a release blocker. We'll try to address it before the release.
We've discussed this within the team and decided to close the ticket, leaving the current behavior unchanged. For more details, please refer to the explanation in the upstream ticket: https://github.com/rpm-software-management/dnf5/issues/1361.
You just said this is important to resolve.
(In reply to Miro Hrončok from comment #7) > You just said this is important to resolve. Yes and I believe closing the ticket with an explanation is a valid resolution, right? :) Anyway, thanks for the feedback upstream. I had a slightly different perspective on the distinction between stdout and stderr in this case. We'll look into this, but ensuring consistent behavior across all dnf commands might require a significant amount of work.