Summary: | sys-apps/portage: emerge --quiet option suppresses eqawarn messages in build log (though elog framework captures and outputs them) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Agostino Sarubbo <ago> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 711148 | ||
Attachments: | build log |
Description
Agostino Sarubbo
2020-03-21 16:39:23 UTC
This emerge --quiet behavior goes back to this commit from bug 160075 where eqawarn was changed to use the vecho function which suppresses output for --quiet mode: https://gitweb.gentoo.org/proj/portage.git/commit/?id=c53f52941c88b24c20204f1795dc02f595ee3a57 Is there a way from options to overwrite this behavior? I'm compiling with -q but as you can see the log misses the QA notice useful for who receives the bug report. (In reply to Agostino Sarubbo from comment #2) > Is there a way from options to overwrite this behavior? I'm compiling with > -q but as you can see the log misses the QA notice useful for who receives > the bug report. This --quiet behavior is currently not adjustable, but I doubt that anyone will complain if we change eqawarn to use echo instead of vecho. Bug 160075 was from a time before emerge --jobs and emerge --quiet-build, when emerge --quiet did not suppress build output to the tty. I've checked history to see when emerge --quiet stopped sending build output to the tty, and it was this change (~1.5 years after bug 160075): https://gitweb.gentoo.org/proj/portage.git/commit/?id=0398470e5029fe096a4400a2a6a79ef40076a691 The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=6569381d5d22b287963bcbabe4c510fad9845ea2 commit 6569381d5d22b287963bcbabe4c510fad9845ea2 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2020-03-21 21:27:43 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2020-03-21 21:42:42 +0000 eqawarn: output to build log regardless of --quiet (bug 713818) Make eqwarn output to the build log regardless of --quiet, via echo to stderr instead of __vecho. This __vecho usage was originally introduced in commit c53f52941c88, which was during the time when build output went to the tty regardless of --quiet mode (that changed in commit 0398470e5029). Bug: https://bugs.gentoo.org/713818 Signed-off-by: Zac Medico <zmedico@gentoo.org> bin/isolated-functions.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) I would be grateful to you if you can make a release so with the new version my bugs from AT findind will make more sense The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6a0c4eab7417a7823cabe54ace677377114b18dd commit 6a0c4eab7417a7823cabe54ace677377114b18dd Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2020-03-23 03:02:25 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2020-03-23 03:03:33 +0000 sys-apps/portage: Bump to version 2.3.95 #713100 fix FEATURES=userpriv $HOME permissions #713726 emerge --info: Filter variables for credentials #713818 eqawarn: output to build log regardless of --quiet Bug: https://bugs.gentoo.org/711148 Bug: https://bugs.gentoo.org/713100 Bug: https://bugs.gentoo.org/713726 Bug: https://bugs.gentoo.org/713818 Package-Manager: Portage-2.3.95, Repoman-2.3.21 Signed-off-by: Zac Medico <zmedico@gentoo.org> sys-apps/portage/Manifest | 1 + sys-apps/portage/portage-2.3.95.ebuild | 268 +++++++++++++++++++++++++++++++++ 2 files changed, 269 insertions(+) |