jerry schreef: > Holly Bostick wrote: > >> >> However, it's hard to imagine that the US pool might not be >> current. >> >> [General question] What else might prevent a sync from actually >> updating the local tree correctly? >> >> Ummmm.... unless it actually has, and the problem is Portage not >> knowing it somehow.... >> >> Would you do an >> >> ls /usr/portage/sys-kernel/gentoo-sources/ >> >> and post the output? >> >> I'm just wondering if the ebuilds are physically there or not. >> > > backup jerry # ls /usr/portage/sys-kernel/gentoo-sources/ ChangeLog > gentoo-sources-2.6.15-r3.ebuild Manifest > gentoo-sources-2.6.15-r4.ebuild files > gentoo-sources-2.6.15-r5.ebuild gentoo-sources-2.4.31-r1.ebuild > gentoo-sources-2.6.15-r6.ebuild gentoo-sources-2.4.32-r2.ebuild > gentoo-sources-2.6.15-r7.ebuild gentoo-sources-2.6.14-r7.ebuild > gentoo-sources-2.6.15.ebuild gentoo-sources-2.6.15-r1.ebuild > metadata.xml gentoo-sources-2.6.15-r2.ebuild >
Well, wouldja look at that! So the ebuilds *are* there, but Portage is just not offering them. Have you: 1) checked /etc/portage/package.mask (maybe you masked them and forgot)? 2) checked your Portage version (maybe you need an upgrade)? 3) tried emerging one of the invisible versions explicitly (emerge -av =sys-kernel/gentoo-sources-2.6.15-r7)? Even an error or failure might tell us more about what's going on than we know now. HTH; talk to you after the gcc upgrade is done. Holly -- gentoo-user@gentoo.org mailing list
