Hello Bero,
Thanks for your quick response.
This is expected - our builders don’t run as root, so they don’t have write access to /lib/systemd. You probably want to make sure it extracts to %{buildroot}/lib/systemd/system-sleep/displaylink.sh instead
I am a packager noob… It reminds me when I started to use Mandriva back in 2006 LOL!!
According to the next section it does seem to have %{buildroot}/lib/systemd/system-sleep/displaylink.sh
pm-util
bash %{SOURCE3} displaylink-installer.sh > %{buildroot}%{_prefix}/lib/systemd/system-sleep/displaylink.sh
chmod +x %{buildroot}%{_prefix}/lib/systemd/system-sleep/displaylink.sh
I wonder what you changed in the specs to make it work.
I my case I only changed 2 dependency names, libusbx to libusb1.0_0 and xorg-x11-server-Xorg to x11-server-xorg
Once I run make the packages are created fine, but once I install them I get:
$dnf install displaylink-1.12.0-1.x86_64.rpm
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : displaylink-1.12.0-1.x86_64 1/1
Running scriptlet: displaylink-1.12.0-1.x86_64 1/1
Job for displaylink-driver.service failed because the control process exited with error code.
See “systemctl status displaylink-driver.service” and “journalctl -xeu displaylink-driver.service” for details.
warning: %post(displaylink-1.12.0-1.x86_64) scriptlet failed, exit status 1
journalctl -xeu displaylink-driver.service
░░ A start job for unit displaylink-driver.service has begun execution.
░░
░░ The job identifier is 2689.
Sep 01 14:48:10 localhost modprobe[94759]: modprobe: FATAL: Module evdi not found in directory /lib/modules/5.19.4-desktop-2.mga9
Sep 01 14:48:10 localhost systemd[1]: displaylink-driver.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░
░░ An ExecStartPre= process belonging to unit displaylink-driver.service has exited.
░░ A start job for unit displaylink-driver.service has begun execution.
░░
░░ The job identifier is 2689.
Sep 01 14:48:10 localhost modprobe[94759]: modprobe: FATAL: Module evdi not found in directory /lib/modules/5.19.4-desktop-2.mga9
Sep 01 14:48:10 localhost systemd[1]: displaylink-driver.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░
░░ An ExecStartPre= process belonging to unit displaylink-driver.service has exited.
░░
░░ The process’ exit code is ‘exited’ and its exit status is 1.
Sep 01 14:48:10 localhost systemd[1]: displaylink-driver.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░
░░ The unit displaylink-driver.service has entered the ‘failed’ state with result ‘exit-code’.
Sep 01 14:48:10 localhost systemd[1]: Failed to start DisplayLink Driver Service.
░░ Subject: A start job for unit displaylink-driver.service has failed
░░ Defined-By: systemd
░░
░░ A start job for unit displaylink-driver.service has finished with a failure.
░░
░░ The job identifier is 2689 and the job result is failed.
Regards