From: Caleb Cushing <xenoterracide@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bash-4.0-r1 for ~arch
Date: Tue, 3 Mar 2009 01:25:49 -0500 [thread overview]
Message-ID: <81bfc67a0903022225w25a17769o68ba94d980c3c272@mail.gmail.com> (raw)
In-Reply-To: <20090303035627.GA3811@comet>
On Mon, Mar 2, 2009 at 10:56 PM, Donnie Berkholz <dberkholz@gentoo.org> wrote:
> Actually seems like quite a few of the bash-completion scripts have
> issues with 4.0 ... might want to just run through those.
nam-1.11.ebuild has the same error. repoman can't source it.
/mnt/sda8/portdev/tree/regen2/net-analyzer/nam/nam-1.11.ebuild: line
36: unexpected EOF while looking for matching `)'
/mnt/sda8/portdev/tree/regen2/net-analyzer/nam/nam-1.11.ebuild: line
75: syntax error: unexpected end of file
*
* ERROR: net-analyzer/nam-1.11 failed.
* Call stack:
* ebuild.sh, line 1881: Called die
* The specific snippet of code:
* source "${EBUILD}" || die "error sourcing ebuild"
* The die message:
* error sourcing ebuild
*
* If you need support, post the topmost build error, and the call
stack if relevant.
*
!!! getFetchMap(): aux_get() error reading net-analyzer/nam-1.11;
aborting.
Unable to generate manifest.
out of all the ebuilds in the tree... it seems to be the only one with
a problem given that -r1 doesn't seem to have the issue removing it
sounds like a good idea.
--
Caleb Cushing
http://xenoterracide.blogspot.com
next prev parent reply other threads:[~2009-03-03 6:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 0:27 [gentoo-dev] bash-4.0-r1 for ~arch Mike Frysinger
2009-03-03 3:56 ` Donnie Berkholz
2009-03-03 6:25 ` Caleb Cushing [this message]
2009-03-03 6:39 ` Mike Frysinger
2009-03-03 6:43 ` Caleb Cushing
2009-03-03 6:27 ` Mike Frysinger
2009-03-03 6:58 ` [gentoo-dev] " ABCD
2009-03-03 7:54 ` [gentoo-dev] " Donnie Berkholz
2009-03-03 7:56 ` Donnie Berkholz
2009-03-03 20:04 ` Mike Frysinger
2009-03-03 22:55 ` Mike Frysinger
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=81bfc67a0903022225w25a17769o68ba94d980c3c272@mail.gmail.com \
--to=xenoterracide@gmail.com \
--cc=gentoo-dev@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