SEO

jef wrote:

> OK, I've launched emerge --update --deep world and here is the content of
> /var/log/emerge.log
>[cut]
> 1206482106: === (1 of 229) Compiling/Merging (dev-libs/nspr-4.6.8::/usr/
> portage/dev-libs/nspr/nspr-4.6.8.ebuild)

Well, it seems you've not updated your system for a *long* time. This is
most likely the source of your problems. You'll have to do some manual work
to sort things out.

> 1206482113: *** terminating.
> ****************************************
>
> and of '/var/log/portage/dev-libs:nspr-4.6.8:20080325-215506.log'.
>[cut]
> it seems that a lot of files are missing

First of all, updating your system on a regular basis (eg, once every 2/3
days or once a week), by using "emerge --sync" and "emerge -uD world" is
the way to go to avoid problems like this.

That said, let's see what we can do. The following are general instructions.
There isn't much to do, except trying to upgrade as many packages as
possible skipping those that fail, in the hope that those can be installed
later.

The general procedure is as follows: do an "emerge -uDvNt world" and let it
run until some package fails. When this happens, write down the name of the
failing package and resume the process skipping the offending package
using "emerge --resume --skipfirst". When there are no more packages to
build, try re-emerging those that had previously failed, one by one.

Depending on your situation, there are some critical packages you may want
to emerge before anything else, like for instance portage, python (which
portage is written in), linux-headers, glibc, gcc.

As a very general advice, if emerge wants to upgrade portage, do that first
(emerge portage), followed by linux-headers and glibc (emerge linux-headers
&& emerge glibc). Then go with the generic procedure described above.

However, be prepared to have some trouble during the process. You can post
your results here and ask for help, of course.

Regards

Le Wed, 26 Mar 2008 22:56:50 +0100, pk a écritÂ*:

> There may be, however, another path, but this requires that you have
> another working (and preferably up-to-date) gentoo system. If that is
> the case, you can issue the following command on that system:
>
> # quickpkg linux-headers gcc glibc portage
>
What if I try this on my system ? It can't be worse, anyway

> While doing this, write down the version of gcc it packages. After this,
[cut]
> copy, you should have recreated the same directory structure under
> /usr/portage/packages. Now, issue this command:
>
> # emerge -K linux-headers gcc glibc portage
>
> This will install the packages using the binary tarballs you previously
> built and transferred here. That shouldn't really need to compile
> anything, just unpack the .tgz.
[cut]
> If you get this far, then you can try emerging something and see whether
> that works.
>
> Sorry, can't be of more help.

You've done a lot, and I won't blame you for my mistakes . After the
first, I should have asked for help, but I think I got it worse, trying
to repair by myself .
If nothing works, I'll try to reinstall from stage3 .
thanks again
regards,
jf

"jef" <cestpasjihef@intnet.mu> a écrit dans le message de
news:47eac6e8$0$26182$426a74cc@news.free.fr...
> Le Wed, 26 Mar 2008 22:56:50 +0100, pk a écrit :
>
>> There may be, however, another path, but this requires that you have
>> another working (and preferably up-to-date) gentoo system. If that is
>> the case, you can issue the following command on that system:
>>
>> # quickpkg linux-headers gcc glibc portage
>>
> What if I try this on my system ? It can't be worse, anyway
>

Oups, sorry for that ! It's 2 o'clock here

regards,
jf

jef wrote:

> Le Wed, 26 Mar 2008 22:56:50 +0100, pk a écritÂ*:
>
>> There may be, however, another path, but this requires that you have
>> another working (and preferably up-to-date) gentoo system. If that is
>> the case, you can issue the following command on that system:
>>
>> # quickpkg linux-headers gcc glibc portage
>>
> What if I try this on my system ? It can't be worse, anyway

No, but the whole point of quickpg is creating a tarball of a working
package, taken from a working system. If you did that on your same system,
you would end up creating tarballs of broken packages, and reinstalling
them would be useless, as that would just recreate your (broken)
environment.

> You've done a lot, and I won't blame you for my mistakes . After the
> first, I should have asked for help, but I think I got it worse, trying
> to repair by myself .
> If nothing works, I'll try to reinstall from stage3 .

Just another note. You said you want to keep some settings for some
applications. My advice in case you reinstall, is to backup your whole home
directory (if it's not already on a dedicated partition) and the
whole /etc. I don't know VDR and where it stores its configuration, but I
guess it's either somewhere in /etc or somewhere in your home directory
(for instance in ~/.vdr or something like that). After the reinstall,
reemerge VDR and then restore your home directory and the relevant files
from /etc (which should be apparent by their names), and see whether things
work like before (they should).

"pk" <pk@pk.invalid> wrote in message news:fsfnhi$ff$1@aioe.org...
> Just another note. You said you want to keep some settings for some
> applications. My advice in case you reinstall, is to backup your whole
> home
> directory (if it's not already on a dedicated partition) and the
> whole /etc. I don't know VDR and where it stores its configuration, but I
> guess it's either somewhere in /etc or somewhere in your home directory
> (for instance in ~/.vdr or something like that). After the reinstall,
> reemerge VDR and then restore your home directory and the relevant files
> from /etc (which should be apparent by their names), and see whether
> things
> work like before (they should).
>
Thanks again . Yes, I'll go for that . It shouldn't be too painful, an
really useful ( at least for my understandind of Gentoo ) ,
my /home is in a dedicated partition . Some applis are a bit tricky to
install but I've always ( .. ok, almost ) succeeded .
I think I'll take the opportunity to try gnome or compiz, instead of kde

regards,
jf