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 10-29-2010, 03:38 PM
justin
 
Default Portage-tree not found anymore

Hi all,

Today I synced and bumped portage to 2.2.01.17086. Now I get this:

# emerge --sync
!!! Repository name or alias 'gentoo_prefix', defined for repository
'gentoo', overrides existing alias or repository.
!!! main-repo not set in DEFAULT and PORTDIR is empty.
!!! Location not set for repository gentoo
!!! Location not set for repository gentoo_prefix
WARNING: One or more repositories have missing repo_name entries:

None/profiles/repo_name

NOTE: Each repo_name entry should be a plain text file containing a
unique name for the repository on the first line.


!!! PORTDIR is undefined. Is
/opt/scisoft64/usr/share/portage/config/make.globals missing?



But /opt/scisoft64/usr/share/portage/config/make.globals is there and
PORTDIR is defined. I also redefined it in make.conf without success.


Any idea?

justin
 
Old 10-29-2010, 03:43 PM
Fabian Groffen
 
Default Portage-tree not found anymore

On 29-10-2010 17:38:37 +0200, justin wrote:
> Hi all,
>
> Today I synced and bumped portage to 2.2.01.17086. Now I get this:
>
> # emerge --sync
> !!! Repository name or alias 'gentoo_prefix', defined for repository
> 'gentoo', overrides existing alias or repository.
> !!! main-repo not set in DEFAULT and PORTDIR is empty.
> !!! Location not set for repository gentoo
> !!! Location not set for repository gentoo_prefix
> WARNING: One or more repositories have missing repo_name entries:

Interesting. It seems it finds more repos to start with. Do you have
PORTDIR_OVERLAY set?




--
Fabian Groffen
Gentoo on a different level
 
Old 10-29-2010, 03:53 PM
justin
 
Default Portage-tree not found anymore

On 29/10/10 17:43, Fabian Groffen wrote:
> On 29-10-2010 17:38:37 +0200, justin wrote:
>> Hi all,
>>
>> Today I synced and bumped portage to 2.2.01.17086. Now I get this:
>>
>> # emerge --sync
>> !!! Repository name or alias 'gentoo_prefix', defined for repository
>> 'gentoo', overrides existing alias or repository.
>> !!! main-repo not set in DEFAULT and PORTDIR is empty.
>> !!! Location not set for repository gentoo
>> !!! Location not set for repository gentoo_prefix
>> WARNING: One or more repositories have missing repo_name entries:
>
> Interesting. It seems it finds more repos to start with. Do you have
> PORTDIR_OVERLAY set?
>
>
>
>

I had, but I removed it w/o success.


http://dev.gentoo.org/~jlec/paste/emerge.info.bes
 
Old 10-30-2010, 02:39 PM
"Justin (jlec) Lecher"
 
Default Portage-tree not found anymore

So if I "re"bootstrap portage I can emerge portage as normal only
"Error during set creation: Could not import
'portage.sets.security.NewAffectedSet' for section 'security'"
appears. But once I emerge portage again it is broken. What is going on?
Any change in the recent ebuilds?
 
Old 10-30-2010, 02:44 PM
Fabian Groffen
 
Default Portage-tree not found anymore

On 30-10-2010 16:39:01 +0200, Justin (jlec) Lecher wrote:
> So if I "re"bootstrap portage I can emerge portage as normal only
> "Error during set creation: Could not import
> 'portage.sets.security.NewAffectedSet' for section 'security'"
> appears. But once I emerge portage again it is broken. What is going on?
> Any change in the recent ebuilds?

Well, sort of yeah. Most probably your bootstrap portage is 15333,
while the portage you emerge is 17133 or something.


--
Fabian Groffen
Gentoo on a different level
 
Old 10-30-2010, 02:45 PM
Fabian Groffen
 
Default Portage-tree not found anymore

On 30-10-2010 16:44:39 +0200, Fabian Groffen wrote:
> On 30-10-2010 16:39:01 +0200, Justin (jlec) Lecher wrote:
> > So if I "re"bootstrap portage I can emerge portage as normal only
> > "Error during set creation: Could not import
> > 'portage.sets.security.NewAffectedSet' for section 'security'"
> > appears. But once I emerge portage again it is broken. What is going on?
> > Any change in the recent ebuilds?
>
> Well, sort of yeah. Most probably your bootstrap portage is 15333,
> while the portage you emerge is 17133 or something.

ok, I will commit that 17133 now, since it is the equivalent of
2.2.0_alpha2


--
Fabian Groffen
Gentoo on a different level
 
Old 10-30-2010, 02:54 PM
"Justin (jlec) Lecher"
 
Default Portage-tree not found anymore

On 30/10/10 16:45, Fabian Groffen wrote:
> On 30-10-2010 16:44:39 +0200, Fabian Groffen wrote:
>> On 30-10-2010 16:39:01 +0200, Justin (jlec) Lecher wrote:
>>> So if I "re"bootstrap portage I can emerge portage as normal only
>>> "Error during set creation: Could not import
>>> 'portage.sets.security.NewAffectedSet' for section 'security'"
>>> appears. But once I emerge portage again it is broken. What is going on?
>>> Any change in the recent ebuilds?
>>
>> Well, sort of yeah. Most probably your bootstrap portage is 15333,
>> while the portage you emerge is 17133 or something.
>
> ok, I will commit that 17133 now, since it is the equivalent of
> 2.2.0_alpha2
>
>

ld is segfaulting when emerging portage. This leads to a problem in
prerm and postrm phase, which makes portage unusable.
 
Old 10-30-2010, 03:01 PM
Fabian Groffen
 
Default Portage-tree not found anymore

On 30-10-2010 16:54:10 +0200, Justin (jlec) Lecher wrote:
> >> Well, sort of yeah. Most probably your bootstrap portage is 15333,
> >> while the portage you emerge is 17133 or something.
> >
> > ok, I will commit that 17133 now, since it is the equivalent of
> > 2.2.0_alpha2
>
> ld is segfaulting when emerging portage. This leads to a problem in
> prerm and postrm phase, which makes portage unusable.

woah, why is ld segfaulting, how, and does this happen more often?


--
Fabian Groffen
Gentoo on a different level
 
Old 10-30-2010, 05:21 PM
"Justin (jlec) Lecher"
 
Default Portage-tree not found anymore

On 30/10/10 17:01, Fabian Groffen wrote:
> On 30-10-2010 16:54:10 +0200, Justin (jlec) Lecher wrote:
>>>> Well, sort of yeah. Most probably your bootstrap portage is 15333,
>>>> while the portage you emerge is 17133 or something.
>>>
>>> ok, I will commit that 17133 now, since it is the equivalent of
>>> 2.2.0_alpha2
>>
>> ld is segfaulting when emerging portage. This leads to a problem in
>> prerm and postrm phase, which makes portage unusable.
>
> woah, why is ld segfaulting, how, and does this happen more often?
>
>

No it is just with that version of portage. And I see no output, it is
only visible in dmesg.
 
Old 10-30-2010, 05:25 PM
"Justin (jlec) Lecher"
 
Default Portage-tree not found anymore

On 30/10/10 17:01, Fabian Groffen wrote:
> On 30-10-2010 16:54:10 +0200, Justin (jlec) Lecher wrote:
>>>> Well, sort of yeah. Most probably your bootstrap portage is 15333,
>>>> while the portage you emerge is 17133 or something.
>>>
>>> ok, I will commit that 17133 now, since it is the equivalent of
>>> 2.2.0_alpha2
>>
>> ld is segfaulting when emerging portage. This leads to a problem in
>> prerm and postrm phase, which makes portage unusable.
>
> woah, why is ld segfaulting, how, and does this happen more often?
>
>

so 17133 doesn't make ld segf but isn't working either. How can I deeply
debug emerge?
 

Thread Tools




All times are GMT. The time now is 08:38 AM.

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