Gentoo Archives: gentoo-amd64

From: Frank Peters <frank.peters@×××××××.net>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] Re: Python-updater line 415 error [Solved]
Date: Mon, 03 Aug 2009 12:55:49
Message-Id: 20090803085515.2862c2ee.frank.peters@comcast.net
In Reply to: [gentoo-amd64] Re: Python-updater line 415 error by Duncan <1i5t5.duncan@cox.net>
1 On Mon, 3 Aug 2009 07:12:09 +0000 (UTC)
2 Duncan <1i5t5.duncan@×××.net> wrote:
3
4 >
5 > I haven't run python-updater in some time but it ran fine when I ran it
6 > last. I do need to run it again since python-3.1 was just in yesterday's
7 > updates, tho, and see what happens.
8 >
9
10 OK. I've found the source of the problem.
11
12 Again, Line 415 is:
13
14 broken_libs="$(scanelf -qBN ${OLD_SONAME} <<(grep -e '^obj' ${content} | cut -d' ' -f2))"
15
16 At first glance, I wasn't sure exactly what this line was doing.
17 Reading someone else's code has to be done very thoroughly and carefully.
18
19 At first glance, I thought it was a nested command substitution
20 but it is actually a type of input redirection from a string (a string
21 that is formed by a command substitution).
22
23 However, the construction is INCORRECT. The line should be this:
24
25 broken_libs="$(scanelf -qBN ${OLD_SONAME} <<< $(grep -e '^obj' ${content} | cut -d' ' -f2))"
26
27 Notice the "<<< $"
28
29 With this correction, python-updater now works as intended
30 with no errors or funny messages.
31
32 Keep in mind that python-updater has had this INCORRECT CODE
33 for the last several releases (0.7, 0.6, 0.5).
34
35 I will file a report with bugs.gentoo.org
36
37 (Now I'll try to root out the difficulty with eselect.)
38
39 Frank Peters

Replies

Subject Author
Re: [gentoo-amd64] Re: Python-updater line 415 error [Solved] Lance Lassetter <lancelassetter@×××××.com>