Summary: | mono move to dev-lang broke portage emerge -uDav world "Depgraph creation failed. " | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fabian Sturm <f> |
Component: | New packages | Assignee: | dotnet project <dotnet> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Fabian Sturm
2005-03-13 15:11:48 UTC
mcatalog is not in portage. You are probably using my overlay, which I've said over and over again, if using my overlay, don't report bugs about it. (: This is fixed in my latest overlay tarball. Marking INVALID, those are in an overlay and not portage for reason. If this is a problem other than the fact you're using a stale overlay, feel free to re-open. Hi! You are right I guess I should have contacted you beforehand but anyways the problem does not come from a stale overlay, at least I guess. I updated and reemrged both mono and mcatalog and both install fine but an emerge -uDav still produces the error message from above. It somehow seems that due to the automatic move an entry was left over which associates mcatalog with dev-dotnet/mono even so dev-dotnet/mono does not appear anywhere in the ebuilds. So in my opinoin the bug is in portage. Okay I agree it is arguable if portage should be able to handle moves which affects packages in overlays but still I need a fix :) Hope anyone can help, sincerely Fabian Have you tried unmerging and emerging mcatalog again? Does "find /usr/local/portage -nname '*.ebuild' | xargs grep dev-dotnet/mono" show anything left over with incorrect deps? Hmm strange, you were right some other packages still contained dev-dotnet/mono. It's still a mistery to me why it complained about mcatalog-0.1 which was definitively okay. But now it works again. So it's fixed for me (invalid as you suggested since not in portage) Thanks for your help and time! Fabian |