Summary: | corrupt metadata causes 'masked by missing keyword' | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Lars Bröcker <Lars.Broecker> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | output of emerge -puDd world |
Description
Lars Bröcker
2006-08-28 14:31:18 UTC
Please attach emerge ouput for the same command with --debug enabled. Also, please post the output of the following command: portageq metadata / ebuild x11-proto/xf86driproto-2.0.3 KEYWORDS Created attachment 95330 [details]
output of emerge -puDd world
belsazar tmp # portageq metadata / ebuild x11-proto/xf86driproto-2.0.3 KEYWORDS belsazar tmp # No output from this command Apparently something has gone wrong with your cache. Do you have anything in /etc/portage/modules? Maybe this will fix it: rm -rf /var/cache/edb/dep emerge --metadata If that doesn't help then please post the output of this command: cat $(portageq portdir)/metadata/cache/x11-proto/xf86driproto-2.0.3 Hmm, I don't even have a directory /etc/portage/modules The two commands sadly did not help, output from emerge -puD world stays the same. Here is the output of the last command belsazar / # cat $(portageq portdir)/metadata/cache/x11-proto/xf86driproto-2.0.3 0>��Y%tDWrsD%tʈ'=>D�=>3'L�DYTDL�0Gbx''DAJC'EDc''D��'3D'B▒Bm'��DQD�tk`Z'��DQD�rk`�j B[Bj wIC' j B[Bj vICH'▒�DmDbelsazar / # That does not look that good to me. What was it supposed to look like? The metadata in your portage tree is somehow corrupt. I'm not sure what caused that you should probably run fsck on the filesystem. Assuming that the filesystem is reliable, emerge --sync should fix it. Well, i ran fsck on the filesystem yesterday. No errors reported, so i think it is okay. But emerge --sync did not remove the problem. Thanks for your time and attention, though. Do you per chance have any other ideas? (In reply to comment #8) > emerge --sync did not remove the problem. Thanks for your time and Is the content of metadata/cache/x11-proto/xf86driproto-2.0.3 still the same? Maybe it has the same mtime and files size as the correct file. In that case, rsync won't transfer it automatically. You can remove the file and then rsync should download the correct version. You may want to remove your entire portage tree in order to make sure that all corrupt files have been purged. I deleted metadata/cache/x11-proto/xf86driproto-2.0.3 and it seems to have worked. Other files seem to have been corrupted, too. How do I remove the complete tree for resyncing? Is deleting everything beneath metadata/cache sufficient? Remove everthying except the packages/ and distfiles/ directories (if you have binary packages and source files stored there and you want to keep them). I followed your advice, got another of those strange cache problems, did on top of that rm -rf /var/cache/edb/dep emerge --metadata and now it seems to work again. Thank you very much for your help! I think this bug can be closed Regards, Lars I guess this was just some random corruption. |