Summary: | there are no ebuilds to satisfy gcc with 2.0.51_preX | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Martin Holzer (RETIRED) <mholzer> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | fmccor |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge -dp gcc
tar file of all /var/db/pkg/sys-devel/gcc* (at jstubbs's request) |
Description
Martin Holzer (RETIRED)
2004-06-12 14:41:35 UTC
What version of python are you running? c2200 portage # emerge -p python These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-lang/python-2.3.3-r1 Created attachment 33164 [details]
emerge -dp gcc
[20:52:21] <sVrmARTY-> c2200 distfiles # python -c 'import portage; print portage.virts["sys-apps/texinfo"]' [20:52:22] <sVrmARTY-> ['sys-devel/gcc'] [20:54:24] <sVrmARTY-> # more /var/db/pkg/sys-apps/texinfo-4.5/PROVIDE [20:54:27] <sVrmARTY-> empty I can't see why this is happening. portage.virts is only ever touched in dovartree and is simply virts=mysettings.getvirtuals("/"). getvirtuals only does a map_dictlist_vals which seems clean. only other possibility is pkgsplit which seems clean as well. Nick? Marius? Checked the virtuals file for corruption ? i get this on base system (with -dev stuff) and a mostly clean chroot this system had never file system corruption. any ideas ? I can't reproduce it as well. Can you archive /var/db/pkg,/var/cache/edb and /etc/portage if you have and upload them somewhere? there was an old version of gcc, which wasn't removed by now. c2200 gcc # emerge unmerge gcc -p >>> These are the packages that I would unmerge: sys-devel/gcc selected: 2.95.3-r8 2.95.3-r5 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. c2200 gcc # emerge unmerge =gcc-2.95.3-r5 here's the new result c2200 portage # emerge info Portage 2.0.51_pre12 (default-1.0, gcc-2.95.3, glibc-2.2.5-r9,glibc-2.2.5-r2, 2.6.7) c2200 portage # emerge -p gcc These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] sys-devel/gcc-2.95.3-r8 c2200 portage # thx a lot guys Created attachment 34685 [details]
tar file of all /var/db/pkg/sys-devel/gcc* (at jstubbs's request)
At jason stubbs's request, attached file is a tar file of
/var/db/pkg/sys-devel/gcc*
System shows similar failure to the one reported here with portage-2.0.51_pre12
And, an 'emerge -C' for gcc-2.5.3-r[5,7] made the symptom go away. Curious. |