On Mon, 2009-08-03 at 08:55 -0400, Frank Peters wrote:
> On Mon, 3 Aug 2009 07:12:09 +0000 (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
>
> >
> > I haven't run python-updater in some time but it ran fine when I ran it
> > last. I do need to run it again since python-3.1 was just in yesterday's
> > updates, tho, and see what happens.
> >
>
> OK. I've found the source of the problem.
>
> Again, Line 415 is:
>
> broken_libs="$(scanelf -qBN ${OLD_SONAME} <<(grep -e '^obj' ${content} | cut
> -d' ' -f2))"
>
> At first glance, I wasn't sure exactly what this line was doing.
> Reading someone else's code has to be done very thoroughly and carefully.
>
> At first glance, I thought it was a nested command substitution
> but it is actually a type of input redirection from a string (a string
> that is formed by a command substitution).
>
> However, the construction is INCORRECT. The line should be this:
>
> broken_libs="$(scanelf -qBN ${OLD_SONAME} <<< $(grep -e '^obj' ${content} |
> cut -d' ' -f2))"
>
> Notice the "<<< $"
>
> With this correction, python-updater now works as intended
> with no errors or funny messages.
>
> Keep in mind that python-updater has had this INCORRECT CODE
> for the last several releases (0.7, 0.6, 0.5).
>
> I will file a report with bugs.gentoo.org
>
> (Now I'll try to root out the difficulty with eselect.)
>
> Frank Peters
>
>
Frank,
Can you post the bug number here to the list?
Thanks,
Lance
