I had been running gentoo-sources-2.4.20-r6 with alsa. I then installed vanilla-sources-2.4.22 and unmerged gentoo-sources. However alsa-driver kept wanting gentoo-sources installed, even after re-emerging vanilla-sources. Some conversations in #gentoo-dev told me that vanilla-sources doesn't satisfy the virtual/linux-sources dependency of alsa-driver. Reproducible: Always Steps to Reproduce:
This might be another symptom of Bug 21603. I'll let kernel nerfherders decide.
Looks like something horribly wrong with portage <tm> to me. Remerge portage and let those auto-dep-fix-tree-thing scripts do some cleaning. Try then. [Blurb] Vanilla-sources pulls the kernel eclass which has a PROVIDES="virtual/kernel-sources" thing, so I see no reason why it would fail. And the slot is equal to the kernel version, so there shouldn't be any problems there. ... [/Blurb]
I've re-emerged portage and have "fixpackages" in my features, but it didn't do the auto-fix thing. How does one manually call it?
fixpackages = for stuff in $portage_root/packages, I believe? dep-clean is what you want, I think... Or not? It shows packages which are not in portage, missing, or unneeded, blar, blar...?
OK I ran dep-clean and it listed a bunch of stuff, but afterwards it still wants gentoo-sources. I can attach the output of dep-clean if you'd like.
Stick PROVIDE="virtual/linux-sources" in the ebuild, and remerge. If that fails, something is mega-wrong<tm> and I'll add manual PROVIDEs to all the ebuilds.
Nope that didn't fix it either. Have a look at Bug 21603 and let me know if you think this is another symptom of that problem.
Did you see a ">>> adding virtual/..............." line at the end? If so, your tree looks semi-corrupted. Manual editing in /var/cache/edb/virtuals... might help. If not, something is wrong with portage. Bug 21603 looks somewhat similar, but I don't see why it happens when merging from one type of kernel to another. Check /var/cache/edb/virtuals.
That virtuals file has this line in it: virtual/linux-sources sys-kernel/gentoo-sources sys-kernel/vanilla-sources I took out the sys-kernel/gentoo-sources portion and that stopped the problem. It looks like a bug in how portage deals with that file. Should gentoo-sources have been removed from that file when I unmerged it?
Yes it should. Bouncing bug to portage folks.
I noticed this problem when messing around with the development-sources too - it still alleged that my kernel was gentoo-sources-2.4.20-r5. It doesn't update the /usr/src/linux symlink either when you emerge gentoo-sources-2.4.20-r6 - it still points at -r5. Is that supposed to happen?!
*** This bug has been marked as a duplicate of 1891 ***
