Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 12181 - ebuild cache entries problem in .45-r5
Summary: ebuild cache entries problem in .45-r5
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Nicholas Jones (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-15 03:16 UTC by Simon Cooper
Modified: 2011-10-30 22:18 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Cooper 2002-12-15 03:16:22 UTC
For about half the packages, whenever I do an emerge -p on them i get:
These are the packages that I would merge, in order.

Calculating dependencies \portage: aux_get(): (1) couldn't open cache entry for
app-editors/vim-core-6.1-r3
(likely caused by syntax error or corruption in the app-editors/vim-core-6.1-r3
ebuild.)


!!! all ebuilds that could satisfy "app-editors/vim-core" have been masked.
!!!    (dependency required by "app-editors/vim-6.1-r17" [ebuild])

!!! Error calculating dependancies. Please correct.

This only started when i upgraded to -r5, there is nothing obviously wrong with
the ebuilds in question, and this cache entry problem causes the ebuilds to be
masked cos there isnt a cache telling portage it shoudnt be masked
Comment 1 Martin Holzer (RETIRED) gentoo-dev 2002-12-15 06:11:15 UTC
do you have /var/cache/edb/dep/ ?
where's the cache
Comment 2 Simon Cooper 2002-12-15 07:09:40 UTC
/var/cache/edb/dep is all there, there are some entries missing (eg
app-editors/vim-core-6.1-r3), those are missing. Where should it get the cache
files from?
Comment 3 Nicholas Jones (RETIRED) gentoo-dev 2002-12-15 07:17:56 UTC
Portage is complaining that it can't generate the cache for vim-core-6.1-r3.
It says there is probably corruption in the vim-core ebuild. You can delete
it an rsync and see if that fixes it. You could also source the ebuild to
see if bash can give you some help as to the problem.
Comment 4 Nicholas Jones (RETIRED) gentoo-dev 2002-12-18 02:59:12 UTC
no new info