From: Lance Lassetter <lancelassetter@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Python-updater line 415 error [Solved]
Date: Tue, 04 Aug 2009 10:40:00 -0500 [thread overview]
Message-ID: <1249400400.14158.0.camel@localhost> (raw)
In-Reply-To: <20090803085515.2862c2ee.frank.peters@comcast.net>
On Mon, 2009-08-03 at 08:55 -0400, Frank Peters wrote:
> On Mon, 3 Aug 2009 07:12:09 +0000 (UTC)
> Duncan <1i5t5.duncan@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
next prev parent reply other threads:[~2009-08-04 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 4:36 [gentoo-amd64] Python-updater line 415 error Frank Peters
2009-08-03 4:42 ` Lance Lassetter
2009-08-03 5:59 ` Frank Peters
2009-08-03 6:07 ` Lance Lassetter
2009-08-03 6:16 ` Frank Peters
2009-08-03 6:21 ` Lance Lassetter
2009-08-03 6:28 ` Frank Peters
2009-08-03 6:44 ` Lance Lassetter
2009-08-03 12:31 ` Frank Peters
2009-08-03 7:12 ` [gentoo-amd64] " Duncan
2009-08-03 8:04 ` Lance Lassetter
2009-08-03 12:55 ` [gentoo-amd64] Re: Python-updater line 415 error [Solved] Frank Peters
2009-08-04 15:40 ` Lance Lassetter [this message]
2009-08-04 16:29 ` Frank Peters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1249400400.14158.0.camel@localhost \
--to=lancelassetter@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox