public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Loupy <il.loupy@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] fsck + emerge => crash
Date: Wed, 18 Nov 2009 09:12:32 +0100	[thread overview]
Message-ID: <a3933ff30911180012l292b08c5y78fee65fb914e959@mail.gmail.com> (raw)
In-Reply-To: <200911162321.47246.volkerarmin@googlemail.com>

Hi all,

2009/11/16 Albert Hopkins <marduk@letterboxes.org>:
> My advice would have been to do periodic backups.  But I guess it's too
> late for that.
Eeeeek, backups: She needs backup because she can't hang with the big dogs.
Well now I learned a lesson.

> For the encoding error, that character qualifies as latin1 (รข) so maybe
> it's an issue where your system (or python) encoding got out of wack.
> You may be able to fix it easily changing that, but my guess is along
> the way you'll find little errors here and there with other things
> (that's why backups are so handy).
I will try this first, but I think you are with the little errors.

2009/11/16 Mick <michaelkintzios@gmail.com>:
> I assume that you ran fsck from a LiveCD?  May want to use the same to rebuild
> your toolchain.
As for the toolchain: is python part of it?

> Have a look here: <http://www.gentoo.org/proj/en/portage/doc/manually-fixing-
> portage.xml> in case it helps.
That's where I first looked for advice, but the procedure doesn't help
me fixing this issue over here. I think it would be nice if one sets
up an article how to rebuild the current system.

2009/11/16 Volker Armin Hemmann <volkerarmin@googlemail.com>:
> probably that files endet in LOST+FOUND. You also can get them from a portage
> tarfile
Well, I found some of the files, but not all, so I will have to
remerge at least the ones I didn't find.

> best thing you can do - remove the directories affected and re-emerge the stuff.
Jip, that's what I heading for now. The funny thing is, that the
system as whole runs charming, just emerge seems to be broken.

-
Will report soon which way I gone.

Stay tuned!
~Loupy



      reply	other threads:[~2009-11-18  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 19:01 [gentoo-user] fsck + emerge => crash Loupy
2009-11-16 21:16 ` Albert Hopkins
2009-11-16 22:13   ` Mick
2009-11-16 22:21 ` Volker Armin Hemmann
2009-11-18  8:12   ` Loupy [this message]

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=a3933ff30911180012l292b08c5y78fee65fb914e959@mail.gmail.com \
    --to=il.loupy@googlemail.com \
    --cc=gentoo-user@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