Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o
Cc: Zac Medico <zmedico@g.o>
Subject: [gentoo-portage-dev] [PATCH] dblink: elog failed postinst (bug 547778)
Date: Sat, 02 May 2015 19:28:13
Message-Id: 1430594880-28741-1-git-send-email-zmedico@gentoo.org
1 This ensures that there's still an eerror elog message, even if the
2 failed postinst did not call eerror itself.
3
4 X-Gentoo-Bug: 547778
5 X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=547778
6 ---
7 pym/portage/dbapi/vartree.py | 5 +++--
8 1 file changed, 3 insertions(+), 2 deletions(-)
9
10 diff --git a/pym/portage/dbapi/vartree.py b/pym/portage/dbapi/vartree.py
11 index cacbf96..fca84d1 100644
12 --- a/pym/portage/dbapi/vartree.py
13 +++ b/pym/portage/dbapi/vartree.py
14 @@ -4376,8 +4376,9 @@ class dblink(object):
15 if a != os.EX_OK:
16 # It's stupid to bail out here, so keep going regardless of
17 # phase return code.
18 - showMessage(_("!!! FAILED postinst: ")+str(a)+"\n",
19 - level=logging.ERROR, noiselevel=-1)
20 + self._elog("eerror", "postinst", [
21 + _("FAILED postinst: %s") % (a,),
22 + ])
23
24 #update environment settings, library paths. DO NOT change symlinks.
25 env_update(
26 --
27 2.3.5

Replies