From 9ebe11e40796c8d000a50eac0d9bce1f630c5668 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Wed, 16 May 2012 12:44:15 -0700 Subject: [PATCH] _eapi_invalid: elog permission issue, bug #416231 --- pym/portage/package/ebuild/_eapi_invalid.py | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/pym/portage/package/ebuild/_eapi_invalid.py b/pym/portage/package/ebuild/_eapi_invalid.py index 1ee8a8be6..d23677d23 100644 --- a/pym/portage/package/ebuild/_eapi_invalid.py +++ b/pym/portage/package/ebuild/_eapi_invalid.py @@ -3,6 +3,7 @@ import textwrap +import portage from portage.dep import _repo_separator from portage.elog import elog_process from portage.elog.messages import eerror @@ -40,7 +41,14 @@ def eapi_invalid(self, cpv, repo_name, settings, " FEATURES=parse-eapi-ebuild-head in make.conf in order to" " make this error fatal."), 70)) - for line in msg: - eerror(line, phase="other", key=cpv) - elog_process(cpv, settings, - phasefilter=("other",)) + if portage.data.secpass >= 2: + # TODO: improve elog permission error handling (bug #416231) + for line in msg: + eerror(line, phase="other", key=cpv) + elog_process(cpv, settings, + phasefilter=("other",)) + + else: + out = portage.output.EOutput() + for line in msg: + out.eerror(line) -- 2.26.2