Summary: | emerge --regen removes metadata cache of overlays located in /usr/portage/local/<overlay> | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Vlastimil Babka (Caster) (RETIRED) <caster> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 307597 |
Description
Vlastimil Babka (Caster) (RETIRED)
2010-01-29 15:23:11 UTC
Do you have anything in /etc/portage/modules? Is there any cache in /usr/portage/local/<overlay>/metadata/cache/? Do the removed cache entries regenerate if you do something to trigger metadata access, such as by running `repoman manifest` in the overlay? (In reply to comment #1) > Do you have anything in /etc/portage/modules? Just commented out stuff, shouldn't matter right? #portdbapi.auxdbmodule = cache.metadata_overlay.database #portdbapi.auxdbmodule = cache.sqlite.database > Is there any cache in /usr/portage/local/<overlay>/metadata/cache/? No, just empty /usr/portage/local/<overlay>/metadata/ > Do the removed cache entries regenerate if you do something to trigger metadata > access, such as by running `repoman manifest` in the overlay? Yes. Thanks, your patch is in svn r15295. This is fixed in 2.1.8 and 2.2_rc64. |