From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Python-updater line 415 error
Date: Mon, 3 Aug 2009 08:31:02 -0400 [thread overview]
Message-ID: <20090803083102.ef215d17.frank.peters@comcast.net> (raw)
In-Reply-To: <1249281863.5149.16.camel@localhost>
On Mon, 03 Aug 2009 01:44:23 -0500
Lance Lassetter <lancelassetter@gmail.com> wrote:
>
> afaik, latest stable is:
> bash-3.2_p39
>
> might not be a good idea to run unstable stuff such as bash and python;
> just a thought.
>
After downgrading to bash-3.2, the problem remains. Bash
is thus apparently not the culprit.
My greatest fear has been realized. No one else experiences
this problem; therefore, I have a gremlin lurking somewhere on
my system.
I can't devote excessive time right now to explore this more
deeply. So far, only eselect and python-updater are affected
and I can fix both of these.
Incidentally, eselect, also a bash script, produces this error:
`ec_do_list-options': not a valid identifier
`ec_do_list-modules': not a valid identifier
If I rename these identifiers to
ec_do_list_options
ec_do_list_modules
the problem disappears.
Frank Peters
next prev parent reply other threads:[~2009-08-03 12:31 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 [this message]
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
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=20090803083102.ef215d17.frank.peters@comcast.net \
--to=frank.peters@comcast.net \
--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