| 1 |
On Mon, Mar 2, 2009 at 10:56 PM, Donnie Berkholz <dberkholz@g.o> wrote: |
| 2 |
> Actually seems like quite a few of the bash-completion scripts have |
| 3 |
> issues with 4.0 ... might want to just run through those. |
| 4 |
|
| 5 |
nam-1.11.ebuild has the same error. repoman can't source it. |
| 6 |
|
| 7 |
/mnt/sda8/portdev/tree/regen2/net-analyzer/nam/nam-1.11.ebuild: line |
| 8 |
36: unexpected EOF while looking for matching `)' |
| 9 |
/mnt/sda8/portdev/tree/regen2/net-analyzer/nam/nam-1.11.ebuild: line |
| 10 |
75: syntax error: unexpected end of file |
| 11 |
* |
| 12 |
* ERROR: net-analyzer/nam-1.11 failed. |
| 13 |
* Call stack: |
| 14 |
* ebuild.sh, line 1881: Called die |
| 15 |
* The specific snippet of code: |
| 16 |
* source "${EBUILD}" || die "error sourcing ebuild" |
| 17 |
* The die message: |
| 18 |
* error sourcing ebuild |
| 19 |
* |
| 20 |
* If you need support, post the topmost build error, and the call |
| 21 |
stack if relevant. |
| 22 |
* |
| 23 |
!!! getFetchMap(): aux_get() error reading net-analyzer/nam-1.11; |
| 24 |
aborting. |
| 25 |
Unable to generate manifest. |
| 26 |
|
| 27 |
out of all the ebuilds in the tree... it seems to be the only one with |
| 28 |
a problem given that -r1 doesn't seem to have the issue removing it |
| 29 |
sounds like a good idea. |
| 30 |
-- |
| 31 |
Caleb Cushing |
| 32 |
|
| 33 |
http://xenoterracide.blogspot.com |
Archives