From: Juergen Rose <rose@rz.uni-potsdam.de>
To: gentoo-user-de@lists.gentoo.org
Subject: Re: [gentoo-user-de] 'emerge sync' funktioniert nicht mehr
Date: Thu, 08 Sep 2005 09:59:06 +0200 [thread overview]
Message-ID: <1126166346.22905.11.camel@cheetah.homenet> (raw)
In-Reply-To: <1126164649.4033.3.camel@desktux.sierra.lan>
Am Donnerstag, den 08.09.2005, 09:30 +0200 schrieb Matthias Nimscholz:
> Am Donnerstag, den 08.09.2005, 08:54 +0200 schrieb Juergen Rose:
> > Am Donnerstag, den 08.09.2005, 08:34 +0200 schrieb Matthias Nimscholz:
> > > Am Mittwoch, den 07.09.2005, 11:26 +0200 schrieb Andreas Prieß:
> > > > rose@rz.uni-potsdam.de wrote:
> > > > > gestern ist mein Rechner, moeglicherweise bei 'emerge sync',
> > > > > abgestuerzt. Seitdem funktioniert emerge nicht mehr:
> > > > >
> > > > > 1.) 'emerge sync' liefert reproduzierbar:
> > > > [...]
> > > > >>>>Updating Portage cache:
> > > > >
> > > > > Traceback (most recent call last):
> > > > > File "/usr/bin/emerge", line 2705, in ?
> > > > > oldcat = portage.catsplit(cp_list[0])[0]
> > > > > IndexError: list index out of range
> > > Nach einem "emerge metadata" hat sich der Rechner aber wieder
> > > gefangen.
> >
> > "emerge metadata" hilft bei mir leider nicht:
> > root@cheetah:/home/ftp/pub/portage/distfiles(293)# emerge metadata
> >
> > Performing Global Updates: /usr/portage/profiles/updates/3Q-2005
> > (Could take a couple of minutes if you have a lot of binary packages.)
> > .='update pass' *='binary update' @='/var/db move'
> > s='/var/db SLOT move' S='binary SLOT move'
> > p='update /etc/portage/package.*'
> > portage: Update type "" not recognized.
> > skipping sync
> > >>> Updating Portage cache:
> > Traceback (most recent call last):
> > File "/usr/bin/emerge", line 2705, in ?
> > oldcat = portage.catsplit(cp_list[0])[0]
> > IndexError: list index out of range
> Mist! Hast Du viele binärpackete in /usr/portage/packages?
> Versuch ein "fixpackages" vorher - sonst bin ich mit meinem Latein am
> Ende.
Ich habe "fixpackages" ausgefuehrt, aber "emerge metadata" liefert immer
noch:
>>> Updating Portage cache:
Traceback (most recent call last):
File "/usr/bin/emerge", line 2705, in ?
oldcat = portage.catsplit(cp_list[0])[0]
IndexError: list index out of range
Gruss, Juergen
--
Juergen Rose <rose@rz.uni-potsdam.de>
FHS Wildau
--
gentoo-user-de@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-08 8:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 5:43 [gentoo-user-de] 'emerge sync' funktioniert nicht mehr rose
2005-09-07 9:26 ` Andreas Prieß
2005-09-08 6:34 ` Matthias Nimscholz
2005-09-08 6:54 ` Juergen Rose
2005-09-08 7:30 ` Matthias Nimscholz
2005-09-08 7:59 ` Juergen Rose [this message]
2005-09-08 8:42 ` Petr Koval
2005-09-08 16:30 ` Florian Wallburg
2005-09-08 17:14 ` Christoph Dahlen
2005-09-08 21:08 ` Petr Koval
2005-09-08 20:38 ` Petr Koval
2005-09-08 7:29 ` Petr Koval
2005-09-08 7:40 ` Petr Koval
2005-09-08 9:31 ` [gentoo-user-de] 'emerge sync' funktioniert nicht mehr ("emerge sync" geloest) Juergen Rose
2005-09-08 9:56 ` Petr Koval
2005-09-08 12:19 ` [gentoo-user-de] 'emerge -vuD system' funktioniert nicht Juergen Rose
2005-09-08 12:41 ` Petr Koval
2005-09-08 13:04 ` Juergen Rose
2005-09-08 12:53 ` Petr Koval
2005-09-08 13:21 ` Juergen Rose
2005-09-08 14:27 ` Petr Koval
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=1126166346.22905.11.camel@cheetah.homenet \
--to=rose@rz.uni-potsdam.de \
--cc=gentoo-user-de@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