Hyprlock emerge fails: cmake_install is not scriptable

[setan]

Hello,

i wanted to upgrade my hyprlock, but the emerge failed during install phase:

Code: Select all

[0/2] /usr/bin/cmake -P /var/tmp/portage/gui-apps/hyprlock-0.3.0/work/hyprlock-0.3.0_build/CMakeFiles/VerifyGlobs.cmake
[0/1] cd /var/tmp/portage/gui-apps/hyprlock-0.3.0/work/hyprlock-0.3.0_build && /usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "RelWithDebInfo"
-- Installing: /var/tmp/portage/gui-apps/hyprlock-0.3.0/image/usr/bin/hyprlock
CMake Error at cmake_install.cmake:64 (install):
  install command is not scriptable

i have checked the source and cmake_install_src is the command that fails it.

Does anyone know if this should be this way or why the install fails?

EDIT: more details:

Code: Select all

 * Messages for package gui-apps/hyprlock-0.3.0:

 * ERROR: gui-apps/hyprlock-0.3.0::guru failed (install phase):
 *   ninja -v -j8 -l8 install failed
 * 
 * Call stack:
 *     ebuild.sh, line  136:  Called src_install
 *   environment, line 2139:  Called cmake_src_install
 *   environment, line 1053:  Called cmake_build 'install'
 *   environment, line  857:  Called eninja 'install'
 *   environment, line 1328:  Called die
 * The specific snippet of code:
 *       "$@" || die -n "${*} failed"

[pietinger]

Moved from Kernel & Hardware to Unsupported Software.

[fedeliallalinea]

Try this patch, in the next version problem seems solved.

[setan]

> Moved from Kernel & Hardware to Unsupported Software.

Sorry... I meant to put this in Pottage but this still was wrong :d

> Try this patch, in the next version problem seems solved.

How do I apply patches to ebuilds?

Also, how do you know if the next version will solve this?
From what I gather the link that you posted points to a file that is no longer in the repo.

[fedeliallalinea]

How do I apply patches to ebuilds?

With /etc/portage/patches

Also, how do you know if the next version will solve this?

Because upstream is already patched

From what I gather the link that you posted points to a file that is no longer in the repo.

The patch was removed because is patched directly on the latest code

[setan]

Damn, patching is really well done. All's fixed now!

> Because upstream is already patched

I see.

I am kind of new to software development.
From what I gather they will realize a hotfix in 0.3.1.
Do you think this makes sense?