Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] [PATCH] portage/util.py: Identify the source of a "bad sustitution" error message (bug 542796)
Date: Thu, 23 Apr 2015 17:38:30
Message-Id: 55392E10.5030809@gentoo.org
In Reply to: [gentoo-portage-dev] [PATCH] portage/util.py: Identify the source of a "bad sustitution" error message (bug 542796) by Brian Dolbec
1 On 04/23/2015 09:01 AM, Brian Dolbec wrote:
2 > This bug caused great difficulty in determining the cause of the error message.
3 > This adds identifying code which states where the error message is coming from.
4 > It also adds the actual source which caused the error message in the first place.
5 > X-Gentoo-Bug: 542796
6 > X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=542796
7 > X-Gentoo-forum-thread: https://forums.gentoo.org/viewtopic-t-1014842.html
8
9 Since varexpand already has an error_leader argument, we could use that
10 to report the source. The relevant varexpand calls are in
11 pym/portage/util/_dyn_libs/LinkageMapELF.py, added in commit
12 f1c1b8a77eebf7713b32e5f9945690f60f4f46de.
13 --
14 Thanks,
15 Zac

Replies