FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Alt

 
 
LinkBack Thread Tools
 
Old 12-15-2011, 12:17 PM
Alan Hourihane
 
Default But in new portage ?

Hi all,

When I try to emerge I'm getting this...

ParseError: Invalid token '0700' (not '='):
/usr/share/portage/config/make.globals: line 139 in
/usr/share/portage/config/make.globals

At line 139, there's this...

# Mode bits for ${WORKDIR} (see ebuild.5).
PORTAGE_WORKDIR_MODE="0700"

Is this right ?

Thanks,

Alan.
 
Old 12-15-2011, 12:21 PM
Alan Hourihane
 
Default But in new portage ?

On 12/15/11 13:17, Alan Hourihane wrote:
> Hi all,
>
> When I try to emerge I'm getting this...
>
> ParseError: Invalid token '0700' (not '='):
> /usr/share/portage/config/make.globals: line 139 in
> /usr/share/portage/config/make.globals
>
> At line 139, there's this...
>
> # Mode bits for ${WORKDIR} (see ebuild.5).
> PORTAGE_WORKDIR_MODE="0700"
>
> Is this right ?
>
Ah, noticed above this line it says this.....

# The offset prefix this Portage was configured with (not used by
# Portage itself)
CONFIGURE_EPREFIX=

Notice, that the line above doesn't have "" at all.

I guess this is a bug because of the way I'm using EPREFIX.

Fabian ?

Alan.
 
Old 12-20-2011, 01:54 PM
Alan Hourihane
 
Default But in new portage ?

On 12/15/11 13:21, Alan Hourihane wrote:
> On 12/15/11 13:17, Alan Hourihane wrote:
>> Hi all,
>>
>> When I try to emerge I'm getting this...
>>
>> ParseError: Invalid token '0700' (not '='):
>> /usr/share/portage/config/make.globals: line 139 in
>> /usr/share/portage/config/make.globals
>>
>> At line 139, there's this...
>>
>> # Mode bits for ${WORKDIR} (see ebuild.5).
>> PORTAGE_WORKDIR_MODE="0700"
>>
>> Is this right ?
>>
> Ah, noticed above this line it says this.....
>
> # The offset prefix this Portage was configured with (not used by
> # Portage itself)
> CONFIGURE_EPREFIX=
>
> Notice, that the line above doesn't have "" at all.
>
> I guess this is a bug because of the way I'm using EPREFIX.
>
> Fabian ?
>

This is still a problem in the latest portage.

Alan.
 
Old 12-20-2011, 02:03 PM
Fabian Groffen
 
Default But in new portage ?

On 20-12-2011 14:54:52 +0000, Alan Hourihane wrote:
> On 12/15/11 13:21, Alan Hourihane wrote:
> > On 12/15/11 13:17, Alan Hourihane wrote:
> >> Hi all,
> >>
> >> When I try to emerge I'm getting this...
> >>
> >> ParseError: Invalid token '0700' (not '='):
> >> /usr/share/portage/config/make.globals: line 139 in
> >> /usr/share/portage/config/make.globals
> >>
> >> At line 139, there's this...
> >>
> >> # Mode bits for ${WORKDIR} (see ebuild.5).
> >> PORTAGE_WORKDIR_MODE="0700"
> >>
> >> Is this right ?
> >>
> > Ah, noticed above this line it says this.....
> >
> > # The offset prefix this Portage was configured with (not used by
> > # Portage itself)
> > CONFIGURE_EPREFIX=
> >
> > Notice, that the line above doesn't have "" at all.
> >
> > I guess this is a bug because of the way I'm using EPREFIX.
> >
> > Fabian ?
> >
>
> This is still a problem in the latest portage.

uhm yes, it slips off the radar because it's not in bugzilla, sorry for
that.


--
Fabian Groffen
Gentoo on a different level
 
Old 12-20-2011, 04:16 PM
Alan Hourihane
 
Default But in new portage ?

On 12/20/11 15:03, Fabian Groffen wrote:
> On 20-12-2011 14:54:52 +0000, Alan Hourihane wrote:
>> On 12/15/11 13:21, Alan Hourihane wrote:
>>> On 12/15/11 13:17, Alan Hourihane wrote:
>>>> Hi all,
>>>>
>>>> When I try to emerge I'm getting this...
>>>>
>>>> ParseError: Invalid token '0700' (not '='):
>>>> /usr/share/portage/config/make.globals: line 139 in
>>>> /usr/share/portage/config/make.globals
>>>>
>>>> At line 139, there's this...
>>>>
>>>> # Mode bits for ${WORKDIR} (see ebuild.5).
>>>> PORTAGE_WORKDIR_MODE="0700"
>>>>
>>>> Is this right ?
>>>>
>>> Ah, noticed above this line it says this.....
>>>
>>> # The offset prefix this Portage was configured with (not used by
>>> # Portage itself)
>>> CONFIGURE_EPREFIX=
>>>
>>> Notice, that the line above doesn't have "" at all.
>>>
>>> I guess this is a bug because of the way I'm using EPREFIX.
>>>
>>> Fabian ?
>>>
>> This is still a problem in the latest portage.
> uhm yes, it slips off the radar because it's not in bugzilla, sorry for
> that.
>

O.k. thanks. I guess I thought I'd check here first before logging. Let
me know if you still want me to do that.

Alan.
 

Thread Tools




All times are GMT. The time now is 01:19 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org