Created attachment 657768 [details] /var/tmp/portage/kde-plasma/kscreenlocker-5.19.5/temp/build.log kde-plasma/kscreenlocker-5.19.5 fails to emerge due to enabled "test" use flag by the src_prepare function. Step to reproduce: No test use flag: equery uses kde-plasma/kscreenlocker [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for kde-plasma/kscreenlocker-5.19.5: U I - - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces + + pam : Add support for PAM (Pluggable Authentication Modules) - DANGEROUS to arbitrarily flip - - test : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently) but inside the ebuild file: ... 63 src_prepare() { 64 ecm_src_prepare 65 use test || cmake_run_in greeter cmake_comment_add_subdirectory autotests 66 } ... and then emerging it: -- Configuring done CMake Error at greeter/autotests/CMakeLists.txt:26 (add_executable): Target "killTest" links to target "Qt5::Test" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? CMake Error at greeter/autotests/CMakeLists.txt:18 (add_executable): Target "authenticatorTest" links to target "Qt5::Test" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing?
> Created attachment 657768 [details] > /var/tmp/portage/kde-plasma/kscreenlocker-5.19.5/temp/build.log > > kde-plasma/kscreenlocker-5.19.5 fails to emerge due to enabled "test" use > flag by the src_prepare function. It's not enabling the test use flag, but it runs something if USE=test is *not* set. Anyway, this is one problem: >/var/tmp/portage/kde-plasma/kscreenlocker-5.19.5/temp/environment: line 2611: cmake_run_in: command not found(In reply to amedeos from comment #0)
Created attachment 657770 [details] emerge --info
Will be fixed after your next sync, thanks for reporting.
I know this is a bug tracker, but I'd like to misuse this comment to thank you for your reliable and _fast_ service. Keep up the good work!
*** Bug 739934 has been marked as a duplicate of this bug. ***
Seems to be fixed now. I was able to emerge kscreenlocker without problems. By the way, the summary is wrong. I've never had a 'cmake_run_in: command not found' error in the logs.
(In reply to Johannes Hirte from comment #6) > Seems to be fixed now. I was able to emerge kscreenlocker without problems. > By the way, the summary is wrong. I've never had a 'cmake_run_in: command > not found' error in the logs. Don't think so. ---------------- -- Configuring done CMake Error at greeter/autotests/CMakeLists.txt:26 (add_executable): Target "killTest" links to target "Qt5::Test" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? CMake Error at greeter/autotests/CMakeLists.txt:18 (add_executable): Target "authenticatorTest" links to target "Qt5::Test" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? -- Generating done CMake Generate step failed. Build files cannot be regenerated correctly. -----------------
If it is not fixed for you then you didn't sync since yesterday or have set some local eclass override.
(In reply to Andreas Sturmlechner from comment #8) > If it is not fixed for you then you didn't sync since yesterday or have set > some local eclass override. You're right.
