Summary: | sys-apps/portage-2.2.12 prints incorrect fetch log location: tail -f /var/log/emerge-fetch.log | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Douglas J Hunley <doug.hunley> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | james.al.stevenson |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 785484 |
Description
Douglas J Hunley
2014-08-21 04:04:44 UTC
It's hardcoded in pym/_emerge/Binpkg.py and pym/_emerge/EbuildBuild.py. The validated EMERGE_LOG_DIR setting is stored in the _emerge.emergelog._emerge_log_dir variable. The hardcoding issue appears to be resolved. EMERGE_LOG_DIR is parsed in lib/_emerge/actions.py if it exists and set to a variable, emergelog._emerge_log_dir. The output referring to logs use that variable now. That said, the EMERGE_LOG_DIR setting is not completely integrated with the code. I've found at least one issue where the solution to another bug was not respecting it and continued writing out to the default log file https://bugs.gentoo.org/285614. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=f8ab6cb0acf5074f56bcb5b3b58aa7e3e2f0711e commit f8ab6cb0acf5074f56bcb5b3b58aa7e3e2f0711e Author: James Stevenson <james.al.stevenson@gmail.com> AuthorDate: 2021-05-23 17:25:36 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2021-05-23 19:54:51 +0000 emerge --fetch and regenworld: Respect EMERGE_LOG_DIR setting Closes: https://github.com/gentoo/portage/pull/720 Bug: https://bugs.gentoo.org/520378 Signed-off-by: James Stevenson <james.al.stevenson@gmail.com> Signed-off-by: Zac Medico <zmedico@gentoo.org> bin/regenworld | 7 ++++++- lib/_emerge/actions.py | 27 +++++++++++++++++++++------ 2 files changed, 27 insertions(+), 7 deletions(-) The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cba21902d9a8d1ac07d2ff5b0d932e71fc1fac67 commit cba21902d9a8d1ac07d2ff5b0d932e71fc1fac67 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2021-05-24 07:47:11 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2021-05-24 09:05:08 +0000 sys-apps/portage: Bump to version 3.0.19 #520378: allow emerge --fetchonly to log to emerge-fetch.log #698244: portage(5) document user patch / eapply_user #781854: Suggest PORTAGE_LOG_FILTER_FILE_CMD cat fallback #782724: sort emerge --unmerge order for determinism #783957: lazily evaluate cnf_* variables in tests #784566: make emerge insensitive to relative order of optional and positional arguments #787545: emerge CTRL C may be ignored when running pkg_pretend #787563: ebuild-ipc could handle KeyboardInterrupt #788967: emerge --jobs= triggers TypeError Bug: https://bugs.gentoo.org/785484 Bug: https://bugs.gentoo.org/788967 Bug: https://bugs.gentoo.org/787563 Bug: https://bugs.gentoo.org/787545 Bug: https://bugs.gentoo.org/784566 Bug: https://bugs.gentoo.org/783957 Bug: https://bugs.gentoo.org/782724 Bug: https://bugs.gentoo.org/781854 Bug: https://bugs.gentoo.org/698244 Bug: https://bugs.gentoo.org/520378 Package-Manager: Portage-3.0.18, Repoman-3.0.3 Signed-off-by: Zac Medico <zmedico@gentoo.org> sys-apps/portage/Manifest | 1 + sys-apps/portage/portage-3.0.19.ebuild | 266 +++++++++++++++++++++++++++++++++ 2 files changed, 267 insertions(+) |