Re-emerging kcontrol after a profile change to 10.0 in the following rebuild of xcb-dependend ebuilds just threw the error described below. emerge --info and the compilation output will follow. Reproducible: Always Steps to Reproduce: Only the first time: 1. eselect profile set 7 # default/linux/amd64/10.0/desktop 2. emerge -auDNtv world 3. revdep-rebuild 4. emerge @preserved-rebuild # should fail with kcontrol 5. revdep-rebuild # just to check that nothing is left to rebuild 6. reboot # in case of a changed environment To reproduce a second time: 7. emerge @preserved-rebuild # the leftover package(s) that failed the first time. including kcontrol Actual Results: kcontrol fails to compile with the following error (roughly translated by me): Fontmap.cpp: In function »bool parseLine(const char*, QString&, QString&, bool&)«: Fontmap.cpp:68: Error: Illegal conversion from »const char*« to »char*« Fontmap.cpp: In function »void addEntry(QStringList&, const QString&, const QString&, const QString&)«: Fontmap.cpp:199: Warning: It is recommended, to set explicit curly braces, to avoid ambiguous »else« Fontmap.cpp: In function »QString locateFile(const char*, const char*, int)«: Fontmap.cpp:256: Warning: It is recommended, to set explicit curly braces, to avoid ambiguous »else« Expected Results: kcontrol should install, just like the last time. The strange thing is, that that exact kcontrol is already installed. I just changed the profile to the new »default/linux/amd64/10.0/desktop« one and this recompilation was the result of an »emerge @preserved-rebuild« that was required for the new »xcb« (X C-language bindings) of that profile. Is the new profile perhaps not yet ready for general use? Or what went wrong this time. Mind you that I have of course retried it, did revdep-rebuild twice, everything else is up-to-date, I rebooted the system (in case of environment changes), etc. How could we fix this bug? Apart from me patching the code that did compile the last time, which would be very weird in my eyes. ^^
Created attachment 204481 [details] »emerge --info« output
Created attachment 204482 [details] kde-base/kcontrol-3.5.10 — complete build log
Oh, I might have found the problem: The ebuild is from the »acorn« overlay! I’m sorry for overlooking that!! If acorn bugs are not handled trough this site, then feel free to close the bug. :)
Closing the bug per last comment. If you can reproduce the error with the ebuild in the main tree, feel free to reopen the bug.
(In reply to comment #4) LOL, I was just in the process of closing the bug myself, as you beat me to it. My comment was: I just removed the acorn overlay, and now portage’s kcontrol emerged fine. Case closed. :) (But it’s good to have it here, in case others have the same problem.)
