View previous topic :: View next topic |
Author |
Message |
queen Veteran
Joined: 19 Jul 2005 Posts: 1642
|
Posted: Fri Aug 03, 2012 7:33 pm Post subject: [SOLVED] eix-update fails |
|
|
I ran eix-sync but after sync eix-update fails.
Code: |
Running eix-update
Reading Portage settings ..
Building database (/var/cache/eix/portage.eix) ..
[0] "gentoo" /usr/portage/ (cache: metadata-md5-or-flat)
Reading category 156|156 (100%) Finished
[1] "" /usr/local/portage (cache: parse|ebuild*#metadata-md5#metadata-flat#assign)
Reading category 156|156 (100%) EMPTY!
Applying masks ..
Calculating hash tables ..
Writing database file /var/cache/eix/portage.eix ..
void update(const char*, CacheTable&, PortageSettings&, bool, const std::vector<RepoName>&, const std::vector<std::basic_string<char> >&, Statusline&): Can't open the database file '/var/cache/eix/portage.eix' for writing (mode = 'wb')
* eix-update failed
* Time statistics:
109 seconds for syncing
5 seconds for eix-update
115 seconds total
|
I tried various things but it didn't help. I ran Code: | emerge -C eix; emerge eix |
Code: | ls -la /var/cache/eix*
-rw------- 1 root root 2609359 Jul 25 23:24 /var/cache/eix.previous
/var/cache/eix:
total 10874
drwxrwxr-x 2 portage portage 152 Aug 3 21:36 .
drwxr-xr-x 11 root root 320 Jul 26 00:05 ..
-rw-r--r-- 1 root root 0 Aug 3 21:36 .keep_app-portage_eix-0
-rw-rw-r-- 1 queen users 5559311 Jul 26 02:05 portage.eix
-rw-rw-r-- 1 queen users 5559311 Jul 26 02:05 previous.eix
|
I run all the commands as root and usually after eix-sync, eix-update runs automatically.
The following one works:
Code: | eix-update -o /tmp/eix
|
But the correct eix-update should update in /var/cache/eix.
I also tried Code: | chmod 666 /var/cache/eix.previous;eix-update
Reading Portage settings ..
Building database (/var/cache/eix/portage.eix) ..
[0] "gentoo" /usr/portage/ (cache: metadata-md5-or-flat)
Reading category 156|156 (100%) Finished
[1] "" /usr/local/portage (cache: parse|ebuild*#metadata-md5#metadata-flat#assign)
Reading category 156|156 (100%) EMPTY!
Applying masks ..
Calculating hash tables ..
Writing database file /var/cache/eix/portage.eix ..
void update(const char*, CacheTable&, PortageSettings&, bool, const std::vector<RepoName>&, const std::vector<std::basic_string<char> >&, Statusline&): Can't open the database file '/var/cache/eix/portage.eix' for writing (mode = 'wb')
|
Code: | ls -la /var/cache/eix/portage.eix
-rw-rw-r-- 1 queein users 5559311 Jul 26 02:05 /var/cache/eix/portage.eix |
Any ideas what can be done?
Last edited by queen on Fri Aug 03, 2012 8:06 pm; edited 1 time in total |
|
Back to top |
|
|
VinzC Watchman
Joined: 17 Apr 2004 Posts: 5098 Location: Dark side of the mood
|
Posted: Fri Aug 03, 2012 7:47 pm Post subject: |
|
|
ls -l /var/cache/eix*: | -rw-rw-r-- 1 portage portage 2614964 21 jui 18:57 /var/cache/eix |
Weird. _________________ Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
Back to top |
|
|
queen Veteran
Joined: 19 Jul 2005 Posts: 1642
|
Posted: Fri Aug 03, 2012 8:05 pm Post subject: |
|
|
VinzC wrote: | ls -l /var/cache/eix*: | -rw-rw-r-- 1 portage portage 2614964 21 jui 18:57 /var/cache/eix |
Weird. |
Yes, I don't know where it came from. But I managed to solve it after some manipulations. I didn't know in the begining it should be portage portage.
So this is what I ran:
Code: |
emerge =app-portage/eix-0.23.10
eix-update //but here I got the same error. So then I ran
mv /var/cache/eix/ /var/cache/eix.old
emerge -u eix
eix-update |
and now all is well. Once I ran mv and upgraded eix again it created the right permissions.
Now I have
Code: | ls -l /var/cache/eix*
/var/cache/eix:
total 5537
-rw-rw-r-- 1 portage portage 5660776 Aug 3 22:26 portage.eix
/var/cache/eix.old:
total 10874
-rw-rw-rw- 1 queen users 5559311 Jul 26 02:05 portage.eix
-rw-rw-rw- 1 queen users 5559311 Jul 26 02:05 previous.eix |
Now I can safely remove /var/cache/eix.old |
|
Back to top |
|
|
kernelOfTruth Watchman
Joined: 20 Dec 2005 Posts: 6111 Location: Vienna, Austria; Germany; hello world :)
|
|
Back to top |
|
|
jlpoole Guru
Joined: 01 Nov 2005 Posts: 483 Location: Salem, OR
|
Posted: Sun Oct 14, 2018 5:13 pm Post subject: |
|
|
I'm doing a fresh install on a new Dell Inspiron using Sakaki's EFI Install Guide and ran into the same problem. I ended up doing the following as root:
Code: | mv /var/cache/eix /var/cache/eix.old
mkdir /var/cache/eix
chgrp portage /var/cache/eix
chmod 775 /var/cache/eix
eix-update
|
Above is a recreation of what I did, it's not exactly as I did; I found /var/cache/eix/portage.eix did not have group write permissions, once I changed that file (I think I performed a "touch /var/cache/eix/portage.eix") to allow group portage to write to it, eix-update then worked.
I thought I'd rely to this topic to document that whatever causes this problem occurred in a fresh Gentoo install/configuration as of October 13, 2018. |
|
Back to top |
|
|
|