unmerging linux-headers and broken system

fuorviato · 02-20-2014, 09:10 AM

I adjusted the permissions on /dev/shm and python merged

Let's hope the rest will go on without problems. So far sa good

i92guboj · 02-20-2014, 10:08 AM

Now that everything is going on again, I'll take one second to let you know that your locales still look wrong. That's probably due to not having configured /etc/locale.gen correctly. For example, this output shows that you have set en_US@UTF-8, but that locale can't be found.

Code:

>>> Unpacking Python-2.7.5.tar.xz to /var/tmp/portage/dev-lang/python-2.7.5-r3/work
>>> Unpacking python-gentoo-patches-2.7.5-0.tar.xz to /var/tmp/portage/dev-lang/python-2.7.5-r3/work
>>> Source unpacked in /var/tmp/portage/dev-lang/python-2.7.5-r3/work
>>> Preparing source in /var/tmp/portage/dev-lang/python-2.7.5-r3/work/Python-2.7.5 ...
/var/tmp/portage/dev-lang/python-2.7.5-r3/temp/environment: line 1827: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8): No such file or directory
/var/tmp/portage/dev-lang/python-2.7.5-r3/temp/environment: line 1827: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8)

This was happening before as well, in linux-headers.

Code:

>>> Unpacking source...
>>> Unpacking gentoo-headers-base-3.10.tar.xz to /var/tmp/portage/sys-kernel/linux-headers-3.10/work
>>> Unpacking gentoo-headers-3.10-1.tar.xz to /var/tmp/portage/sys-kernel/linux-headers-3.10/work
>>> Source unpacked in /var/tmp/portage/sys-kernel/linux-headers-3.10/work
>>> Preparing source in /var/tmp/portage/sys-kernel/linux-headers-3.10/work/gentoo-headers-base-3.10 ...
/var/tmp/portage/sys-kernel/linux-headers-3.10/temp/environment: line 1226: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8): No such file or directory
/var/tmp/portage/sys-kernel/linux-headers-3.10/temp/environment: line 1226: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8)

You should check your /etc/locale.gen. Mots of the lines there are comments. You need to look at the lines that are NOT STARTING with a '#'. For example, I have these:

Code:

en_US.UTF-8 UTF-8
es_ES.UTF-8 UTF-8

Add, remove, or adjust to your likings, and be sure to run this after that:

Code:

$ locale-gen

That should (re)generate your locales. Then, use eselect to check that the selected locale is one of those you set in /etc/locale.gen.

Code:

$ eselect locale list
$ eselect locale set <x>

After that, to reload the settings in the current set just use:

Code:

$ source /etc/profile

If you have many shells open (in a screen session, in VTs, xterms or wherever) you will need to run this command in all of them to make sure the locale settings are updated accordingly. Or just use a famous method often used in another OS and... reboot

Now, the portage errors about locales should have gone.

fuorviato · 02-21-2014, 02:53 AM

The system set did merge without additional problems. I adjusted the locales (thanks for the hint).
The compiler is set to 4.7.3, so it's time to run

Quote:

emerge -auDvn @world

.
As constant learner. I googled a bit those eportage arguments to understand what the command does.

So far, I got that:

1) a- is for asking
2) u - update
3) D - update also dependencies
4) v - verbose output
5) n - recompile also with new use flags set since last update

Am I right?

I tried to paste the whole command in google but didn't really find exact explanation.
What's written in the man file isn't really clear to me.
Why did you suggest this command?

Thanks

Lukasz

i92guboj · 02-21-2014, 03:09 AM

Quote:

Originally Posted by fuorviato

The system set did merge without additional problems. I adjusted the locales (thanks for the hint).
The compiler is set to 4.7.3, so it's time to run .
As constant learner. I googled a bit those eportage arguments to understand what the command does.

So far, I got that:

1) a- is for asking
2) u - update
3) D - update also dependencies
4) v - verbose output
5) n - recompile also with new use flags set since last update

Am I right?

Yes, you are.

Quote:

I tried to paste the whole command in google but didn't really find exact explanation.
What's written in the man file isn't really clear to me.
Why did you suggest this command?

This will ensure that your packages are up to date, and will recompile anything that needs to be recompiled. There might still be some broken binaries here and there, but since you recompiled @system, they shouldn't pose any serious problem.

Still, I recomend you to run "emerge -va @preserved-rebuild" after the @world update is done. That should take care of most ABI breakage that still remains.

Also, it won't harm if you run "revdep-rebuild" after that. Just to make sure. "revdep-rebuild" is part of the "gentoolkit" package, in case you haven't emerged it yet.

Quote:

Thanks

Lukasz

You are welcome. I am glad that you were able to rescue the system after all. As I warned at the beginning of this thread, it would have been easier just to re-install. But for sure you learnt a couple of things in the way

Oh, almost forgot! You might be interested in checking the "make.conf" man page.

Code:

$ man make.conf

Search for "buildpkg" and "buildsyspkg" in the part about FEATURES, you might want to enable one of those, so if something like this happens again you will have your own binaries, which is better for compatibility and security reasons.

Cheers.

fuorviato · 02-21-2014, 03:40 AM

Quote:

Still, I recomend you to run "emerge -va @preserved-rebuild" after the @world update is done. That should take care of most ABI breakage that still remains.

Already done. However. I read a bit about it - Is that true this is equal to revdep-rebuild? Other users report it as such.

So I have my gentoo finally

For now it's still on vbox but I'm gonna play with it and learn, then install it on my laptop as my primary system.
Actually. I would have switched completely to gentoo but I've got only one computer for now.

You can be sure I'll read the manuals then

.

Almost forgot - A big thumb up for you for guiding me and helping around. Respect

See you around

Ł.

i92guboj · 02-21-2014, 03:55 AM

Quote:

Originally Posted by fuorviato

Already done. However. I read a bit about it - Is that true this is equal to revdep-rebuild? Other users report it as such.

The aim of both is the same. However, while portage saves the data about what needs to be in @preserved-rebuild at build time, when merging stuff, revdep-rebuild on the other side analizes the binaries on-demand, which means it can detect ABI breakage that hasn't been registered by the former method.

This is particularly important in this case, since in first place, some binaries that are on your system now have not been installed using portage (so there's no way that @preserved-rebuild will handle them).

In this case, revdep-rebuild will probably complain that there are some broken binaries in your OS that are not claimed by any installed package. These cannot be fixed, but the output will come in handy if you want to manually remove the crap that remains in your fs (just ask if you need help with that). For example, under /usr/i686-pc-linux-gnu/gcc-bin/ there might be leftovers from the compiled you untar'ed from the stage file. You get the idea...