Gentoo Archives: gentoo-amd64

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

Replies

Subject Author
Re: [gentoo-amd64] Re: Python-updater line 415 error [Solved] Frank Peters <frank.peters@×××××××.net>