orion8 ~ # emerge -auDN world These are the packages that would be merged, in order: Calculating world dependencies |depend /usr/portage/eclass/qt4.eclass: line 130: syntax error near unexpected token `(' /usr/portage/eclass/qt4.eclass: line 130: ` eerror "(1) In order to compile ${CATEGORY}/${PN} first you need to build"' * * ERROR: app-crypt/qca-2.0.0-r2 failed. * Call stack: * ebuild.sh, line 1651: Called source '/usr/portage/local/layman/kde/app-crypt/qca/qca-2.0.0-r2.ebuild' * qca-2.0.0-r2.ebuild, line 6: Called inherit 'eutils' 'multilib' 'qt4' * ebuild.sh, line 1190: Called die * The specific snippet of code: * qa_source "$location" || die "died sourcing $location in inherit()" * The die message: * died sourcing /usr/portage/eclass/qt4.eclass in inherit() * * If you need support, post the topmost build error, and the call stack if relevant. * CVS History has a commit reflecting it: --- PASTE --- PASTE --- PASTE --- Revision 1.33 - (view) (download) (annotate) - [select for diffs] Sat Jan 5 20:24:32 2008 UTC (6 hours, 37 minutes ago) by swegener Branch: MAIN Changes since 1.32: +2 -2 lines Diff to previous 1.32 fix quoting eclass/qt4.eclass: line 130: syntax error near unexpected token `(' eclass/qt4.eclass: line 130: ` eerror "(1) In order to compile ${CATEGORY}/${PN} first you need to build"' --- PASTE --- PASTE --- PASTE --- Was broken here: --- PASTE --- PASTE --- PASTE --- Revision 1.29 - (view) (download) (annotate) - [select for diffs] Fri Dec 14 00:31:05 2007 UTC (3 weeks, 2 days ago) by troll Branch: MAIN Changes since 1.28: +79 -19 lines Diff to previous 1.28 qt4.eclass enhancements (see #201772) --- PASTE --- PASTE --- PASTE --- Please fix ASAP
it's not fixed in commit 1.34 ? seems to be okay here now.
(In reply to comment #1) > it's not fixed in commit 1.34 ? seems to be okay here now. Well, I don't see 1.34 anywhere... you didn't commit! The last commit there is: - die "Install x1-libs/qt-core with USE=\"ssl\"" + die "Install x11-libs/qt-core with USE=\"ssl\""
I don't have any uncomitted changes here and I can't reproduce the error. Can you show me a diff of what's broken in the eclass?
Seems to be some caching issue. I was able to reproduce exactly twice on both my desktop and notebook and since then it's gone. Commit history proves that I'm not the only one to see this, yet sorry for making that much noise about it. /me would close it as WORKSFORME now
So....everything is fixed now....right?
Hit me with something heavy if it isn't fixed, but since no one else is complaining...I'm going with that assumption.
