| View previous topic :: View next topic |
| Author |
Message |
CiA10386
n00b
Joined: 06 Aug 2006
Posts: 6
|
 Posted: Sun Jun 22, 2008 5:04 pm Post subject: Package Database Woes [SOLVED] |
 |
|
While extremely tired this morning, I accidentally booted VMWare Server using my physical disk and it screwed a lot of things up.
Eventually, in order to solve things, I wound up issuing 'emerge -e world.' After a subsequent boot from shutdown the next morning, I wound up hitting an error whilst attempting to mount my filesystem root that required manual repair with fsck and I wound up having to wipe an entire inode and having to clone/wipe some other blocks. I describe all this because I'm not sure exactly what or how this happened, but now, whenever I attempt to use emerge for anything, at all, I get a series of messages like the following for pretty much every package in my world file:
| Code: |
Parse Error reading PROVIDE and USE in '/var/db/pkg/www-servers/apache-2.2.9'
Exception: insecure string pickle
Parse Error reading PROVIDE and USE in '/var/db/pkg/www-apache/mod_perl-2.0.3-r2'
Exception: insecure string pickle
|
A sample of what the related USE params looks like:
| Code: |
cat /var/db/pkg/www-servers/apache-2.2.9/USE
amd64 apache2_modules_actions apache2_modules_alias apache2_modules_auth_basic apache2_modules_authn_alias apache2_modules_authn_anon apache2_modules_authn_dbm apache2_modules_authn_default apache2_modules_authn_file apache2_modules_authz_dbm apache2_modules_authz_default apache2_modules_authz_groupfile apache2_modules_authz_host apache2_modules_authz_owner apache2_modules_authz_user apache2_modules_autoindex apache2_modules_cache apache2_modules_dav apache2_modules_dav_fs apache2_modules_dav_lock apache2_modules_deflate apache2_modules_dir apache2_modules_disk_cache apache2_modules_env apache2_modules_expires apache2_modules_ext_filter apache2_modules_file_cache apache2_modules_filter apache2_modules_headers apache2_modules_include apache2_modules_info apache2_modules_log_config apache2_modules_logio apache2_modules_mem_cache apache2_modules_mime apache2_modules_mime_magic apache2_modules_negotiation apache2_modules_rewrite apache2_modules_setenvif apache2_modules_speling apache2_modules_status apache2_modules_unique_id apache2_modules_userdir apache2_modules_usertrack apache2_modules_vhost_alias elibc_glibc kernel_linux ldap ssl threads userland_GNU
|
| Code: |
cat /var/db/pkg/www-apache/mod_perl-2.0.3-r2/USE
amd64 elibc_glibc kernel_linux userland_GNU
|
It may be useful for me to note that neither has a PROVIDE file in my system.
I have no idea what to do because more serious operations like 'emerge --unmerge <package>' or 'emerge <package>' or even 'emerge --pretend <package>' all fail on the aforementioned exception ("insecure string pickle")
EDIT: I attempted to 'emerge --sync' and while everything went normally, including an update of the portage cache, right after the update of the cache, the thing began issuing the same errors.
EDIT2: If I just nuked the database and 'emerge -e world' again, would that be safe?
Last edited by CiA10386 on Mon Jun 23, 2008 1:36 am; edited 1 time in total |
|
| Back to top |
|
 |
CiA10386
n00b
Joined: 06 Aug 2006
Posts: 6
|
| Posted: Mon Jun 23, 2008 1:35 am Post subject: |
|
|
| For the curious user, I have no idea how it was all screwed up, but removing /var/cache/edb/vdb_metadata.pickle and then running 'emerge --metadata && emerge --regen' and it was somehow all fixed! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
