Re: [gentoo-user] fsck + emerge = crash
Hi all, 2009/11/16 Albert Hopkins mar...@letterboxes.org: My advice would have been to do periodic backups. But I guess it's too late for that. Ek, 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 michaelkintz...@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 volkerar...@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
[gentoo-user] fsck + emerge = crash
Hey all, I got a power here, which after I had to run fsck... well there where some troubled Inodes and I choosed yes to repair them. So far so good, system booted well, but now I cannot emerge anything at all. emerge --info tells me as normal user: emerge: incomplete set configuration, missing set(s): world and system This usually means that '/usr/share/portage/config/sets.conf' is missing or corrupt. as su I get a bunch of these messages: Parse Error reading PROVIDE and USE in '/var/db/pkg/kde-base/libkdeedu-3.5.10' Exception: 'ascii' codec can't decode byte 0xe2 in position 19: ordinal not in range(128) Parse Error reading PROVIDE and USE in '/var/db/pkg/x11-plugins/pidgin-otr-3.2.0' Exception: 'ascii' codec can't decode byte 0xe2 in position 19: ordinal not in range(128) Traceback (most recent call last): File /usr/bin/emerge, line 42, in module retval = emerge_main() File /usr/lib/portage/pym/_emerge/main.py, line 1059, in emerge_main if portage._global_updates(trees, mtimedb[updates]): File /usr/lib/portage/pym/portage/__init__.py, line 8855, in _global_updates vardb.update_ents(myupd, onUpdate=onUpdate) File /usr/lib/portage/pym/portage/dbapi/__init__.py, line 227, in update_ents metadata = dict(zip(update_keys, aux_get(cpv, update_keys))) File /usr/lib/portage/pym/portage/dbapi/vartree.py, line 1212, in aux_get pkg_data = self._aux_cache[packages].get(mycpv) File /usr/lib/portage/pym/portage/dbapi/vartree.py, line 1118, in _aux_cache self._aux_cache_init() File /usr/lib/portage/pym/portage/dbapi/vartree.py, line 1146, in _aux_cache_init (self._aux_cache_filename, str(e)), noiselevel=-1) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 19: ordinal not in range(128) emerge --regen tells me the same... well, what would you advice me to do? Regards, Loupy
Re: [gentoo-user] fsck + emerge = crash
On Mon, 2009-11-16 at 20:01 +0100, Loupy wrote: Hey all, I got a power here, which after I had to run fsck... well there where some troubled Inodes and I choosed yes to repair them. So far so good, system booted well, but now I cannot emerge anything at all. [...] well, what would you advice me to do? My advice would have been to do periodic backups. But I guess it's too late for that. 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). -a
Re: [gentoo-user] fsck + emerge = crash
On Monday 16 November 2009 21:16:29 Albert Hopkins wrote: On Mon, 2009-11-16 at 20:01 +0100, Loupy wrote: Hey all, I got a power here, which after I had to run fsck... well there where some troubled Inodes and I choosed yes to repair them. So far so good, system booted well, but now I cannot emerge anything at all. [...] well, what would you advice me to do? My advice would have been to do periodic backups. But I guess it's too late for that. 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 assume that you ran fsck from a LiveCD? May want to use the same to rebuild your toolchain. Have a look here: http://www.gentoo.org/proj/en/portage/doc/manually-fixing- portage.xml in case it helps. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] fsck + emerge = crash
On Montag 16 November 2009, Loupy wrote: Hey all, I got a power here, which after I had to run fsck... well there where some troubled Inodes and I choosed yes to repair them. So far so good, system booted well, but now I cannot emerge anything at all. emerge --info tells me as normal user: emerge: incomplete set configuration, missing set(s): world and system This usually means that '/usr/share/portage/config/sets.conf' is missing or corrupt. probably that files endet in LOST+FOUND. You also can get them from a portage tarfile as su I get a bunch of these messages: Parse Error reading PROVIDE and USE in '/var/db/pkg/kde-base/libkdeedu-3.5.10' Exception: 'ascii' codec can't decode byte 0xe2 in position 19: ordinal not in range(128) best thing you can do - remove the directories affected and re-emerge the stuff.
