derivative-maker: missing /usr/libexec/helper-scripts/get_colors.sh

I get an error about a missing
/usr/libexec/helper-scripts/get_colors.sh

I think it was supposed to be sourced from within the usability-misc git submodule directory, but it is looking for it on the host sytem.

Build log required.

I already fixed it by copying the files to the host directory where it was looking for them. I copied everything from packages/kicksecure/helper-scripts/usr/libexec/helper-scripts under the derivative maker directory and that solved it.

EDIT: Forgot to say that I lost the log for it.

I did a little research in trying to find the problem. I can point to where the problem line is. usability-misc/usr/share/usability-misc/build-dist-installer-cli at 789d3bf2a1b99f62609a7e464c8e5c0c7248d1c5 · Kicksecure/usability-misc · GitHub

It was added in commit Make build script for the installer easier to read · Kicksecure/usability-misc@82425df · GitHub
when they moved he helper functions to their own scripts.

Not used during the build process.

dist-installer-cli also isn’t used.

dist-installer-cli-standalone is used. And that does not source /usr/libexec/helper-scripts/get_colors.sh. So this is strange.

Also dist-installer-cli-standalone should only be run for --target virtualbox. So if you did not use that, then this is double strange.

Passing local builds. CI also passing. So without build log, I won’t be able to fix this.

It still won’t build

############################################################
ERROR detected in script!: ././build-steps.d/2100_create-debian-packages

#####
User Help Message 2/2:

Please READ this message carefully.

Copying/pasting/screenshotting this box alone will not be insightful, and no help can be provided with it alone as it may not contain sufficient information by itself.

In many instances, providing a longer segment above this box or the entire log may be necessary for an effective diagnosis.
#####

dist_build_version: 17.2.0.4
dist_build_error_counter: 1
benchmark: 00:00:02
last_failed_exit_code: 1
trap_signal_type_previous: unset
trap_signal_type_last    : ERR

process_backtrace_result:
1: : init
2: : /lib/systemd/systemd --user 
3: : /usr/libexec/gnome-terminal-server 
4: : bash 
5: : /bin/bash ./derivative-maker --flavor whonix-workstation-xfce --target qcow2 --arch amd64 --repo true 
6: : /bin/bash ././build-steps.d/2100_create-debian-packages --flavor whonix-workstation-xfce --target qcow2 --arch amd64 --repo true 

function_trace_result:
main (line number: 429)
build_run_function (line number: 52)
main (line number: 425)
build_run_function (line number: 52)
create-debian-packages (line number: 416)
build_run_function (line number: 52)
create_derivative_distribution_debian_packages (line number: 381)
exception_handler_general (line number: 381)
exception_handler_process_shared (line number: 381)

last_failed_bash_command: "$source_code_folder_dist/packages/kicksecure/genmkfile/usr/bin/genmkfile" deb-pkg
############################################################
'
++ unset error_reason
++ '[' ERR = INT ']'
++ '[' ERR = TERM ']'
++ '[' ERR = ERR ']'
++ '[' '!' 0 = 0 ']'
++ true 'INFO: dist_build_auto_retry set to 0 (--retry-max). No auto retry.'
++ unset dist_build_auto_retry_counter
++ true
++ ignore_error=false
++ answer=
++ '[' ERR = ERR ']'
++ '[' '' = true ']'
++ '[' -t 0 ']'
++ true 'INFO: stdin connected to terminal, using interactive error handler.'
++ true 'ERROR: An issue in ././build-steps.d/2100_create-debian-packages has been detected!

#####

No comment needed.

Tried again today with the build log enabled. It failed, here is the full terminal output: https://termbin.com/td2u

Wait a second, this looks cut off. Does termbin have a max character limit? It’s too big for pastebin too. Where am I supposed to paste this?

Termbin has most of it, but heres the full file on Catbox: https://files.catbox.moe/bv59t6

I am understanding this now and working on a fix.

This is likely fixed in 17.2.0.5-developers-only and above.

No, today i have built from source code and have same problem. So i conclude that have not fixed yet

Using outdated version number?

Did you get a newer source code version?