After executing
++ error_handler_do_retry=
++ interactive_chroot_shell=
++ ‘[’ r = continue ‘]’
++ ‘[’ r = c ‘]’
++ ‘[’ r = s ‘]’
++ ‘[’ r = shell ‘]’
++ ‘[’ r = r ‘]’
++ ignore_error=true
++ interactive_chroot_shell=false
++ error_handler_do_retry=true
++ exception_handler_retry
++ ‘[’ ‘!’ ‘’ = ‘’ ‘]’
++ true ‘INFO: Skipping dist_build_dispatch_before_retry (–retry-before), because empty, ok.’
++ true 'INFO: Retrying last_failed_bash_command…: test -f “${dist_binary_build_folder}/Whonix-Gateway-${dist_build_desktop}-${dist_build_version}.${target_architecture_pretty_name}.raw” ’
++ retry_last_failed_bash_command_exit_code=0
++ test -f ‘“${dist_binary_build_folder}/Whonix-Gateway-${dist_build_desktop}-${dist_build_version}.${target_architecture_pretty_name}.raw”’
++ retry_last_failed_bash_command_exit_code=1
++ true
++ ‘[’ 1 = 0 ‘]’
++ true 'INFO: Retry failed. exit code of last_failed_bash_command: 1 ’
++ last_failed_exit_code=1
++ last_failed_bash_command=‘test -f “${dist_binary_build_folder}/Whonix-Gateway-${dist_build_desktop}-${dist_build_version}.${target_architecture_pretty_name}.raw”’
++ ‘[’ ‘!’ ‘’ = ‘’ ‘]’
++ true ‘INFO: Skipping dist_build_dispatch_after_retry (–retry-after), because empty, ok.’
++ ‘[’ 1 = 0 ‘]’
++ exception_handler_process_shared ‘NONE_(called_by_exception_handler_retry)’
++ last_script=/usr/bin/dm-prepare-release
++ trap_signal_type_previous=ERR
++ ‘[’ ERR = ‘’ ‘]’
++ trap_signal_type_last=‘NONE_(called_by_exception_handler_retry)’
++ dist_build_error_counter=2
+++ benchmarktimeend 1736043381
++++ date +%s
+++ benchmarktimeend=1736043903
+++ benchmark_took_seconds=522
++++ convertsecs 522
++++ local h m s
++++ (( h=522/3600 ))
++++ true
++++ (( m=(522%3600)/60 ))
++++ (( s=522%60 ))
++++ printf ‘%02d:%02d:%02d\n’ 0 8 42
+++ echo 00:08:42
++ benchmark_took_time=00:08:42
++ local first
++ read -r first _
++ process_backtrace_function
++ true ‘INFO: BEGIN: process_backtrace_function’
++ ‘[’ -o xtrace ‘]’
++ set +x
++ true ‘INFO: END : process_backtrace_function’
++ function_trace_function
++ true ‘INFO: BEGIN: function_trace_function’
++ ‘[’ -o xtrace ‘]’
++ set +x
++ true ‘INFO: END : function_trace_function’
++ output_cmd_set
++ ‘[’ -o xtrace ‘]’
++ output_cmd=true
++ true ’
############################################################
ERROR detected in script!: /usr/bin/dm-prepare-release
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.7
dist_build_error_counter: 2
benchmark: 00:08:42
last_failed_exit_code: 1
trap_signal_type_previous: ERR
trap_signal_type_last : NONE_(called_by_exception_handler_retry)
process_backtrace_result:
1: : init
2: : /lib/systemd/systemd --user
3: : /usr/libexec/gnome-terminal-server
4: : bash
5: : /bin/bash /home/anubis/derivative-maker/derivative-maker --flavor whonix-workstation-xfce --target utm --arch arm64 --tb open --repo true --vmsize 25G
6: : /bin/bash ././build-steps.d/5200_prepare-release --flavor whonix-workstation-xfce --target utm --arch arm64 --tb open --repo true --vmsize 25G
7: : /bin/bash /usr/bin/dm-prepare-release --flavor whonix-workstation-xfce --target utm --arch arm64 --tb open --repo true --vmsize 25G
function_trace_result:
main (line number: 659)
main (line number: 652)
libvirt_compress (line number: 194)
exception_handler_general (line number: 194)
exception_handler_process_shared (line number: 194)
exception_handler_retry (line number: 194)
exception_handler_process_shared (line number: 194)
exception_handler_process_shared (line number: 194)
exception_handler_general (line number: 194)
libvirt_compress (line number: 194)
main (line number: 652)
main (line number: 659)
last_failed_bash_command: test -f “${dist_binary_build_folder}/Whonix-Gateway-${dist_build_desktop}-${dist_build_version}.${target_architecture_pretty_name}.raw”
############################################################
’
++ unset error_reason
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = INT ‘]’
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = TERM ‘]’
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = ERR ‘]’
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = ‘NONE_(called_by_exception_handler_retry)’ ‘]’
++ ‘[’ ‘!’ 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=
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = ERR ‘]’
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = ‘NONE_(called_by_exception_handler_retry)’ ‘]’
++ ‘[’ ‘’ = true ‘]’
++ ‘[’ -t 0 ‘]’
++ true ‘INFO: stdin connected to terminal, using interactive error handler.’
++ true 'ERROR: An issue in /usr/bin/dm-prepare-release has been detected!
User Help Message 1/2:
Please READ this message carefully.
Copying/pasting/screenshotting this error message alone will not be insightful, and no help can be provided with it alone as it does not contain comprehensive information by itself. Instead, please scroll up and review the block encapsulated within ### for more detailed information.
For support queries, it is essential to, at minimum, provide the portion of the log located above this message containing the actual error details. In many instances, providing a longer segment or the entire log may be necessary for an effective diagnosis.
Regrettably, assistance cannot be provided without the aforementioned details.
Options:
Choose either option A), B), C) or D).
- A) Press c and press enter to bypass this error and continue with the build. (For Developers Only!) (Strongly discouraged for regular users as it may lead to unstable builds! Please refrain from reporting any issues encountered subsequently!)
- B) Press r and enter to retry.
- C) Press s and enter to initiate a chroot interactive shell. (For Developers Only!)
- D) Press a and enter to abort.
#####’
++ read -p 'Answer? ’ answer
Answer? r
++ error_handler_do_retry=
++ interactive_chroot_shell=
++ ‘[’ r = continue ‘]’
++ ‘[’ r = c ‘]’
++ ‘[’ r = s ‘]’
++ ‘[’ r = shell ‘]’
++ ‘[’ r = r ‘]’
++ ignore_error=true
++ interactive_chroot_shell=false
++ error_handler_do_retry=true
++ exception_handler_retry
++ ‘[’ ‘!’ ‘’ = ‘’ ‘]’
++ true ‘INFO: Skipping dist_build_dispatch_before_retry (–retry-before), because empty, ok.’
++ true 'INFO: Retrying last_failed_bash_command…: test -f “${dist_binary_build_folder}/Whonix-Gateway-${dist_build_desktop}-${dist_build_version}.${target_architecture_pretty_name}.raw” ’
++ retry_last_failed_bash_command_exit_code=0
++ test -f ‘“${dist_binary_build_folder}/Whonix-Gateway-${dist_build_desktop}-${dist_build_version}.${target_architecture_pretty_name}.raw”’
++ retry_last_failed_bash_command_exit_code=1
++ true
++ ‘[’ 1 = 0 ‘]’
++ true 'INFO: Retry failed. exit code of last_failed_bash_command: 1 ’
++ last_failed_exit_code=1
++ last_failed_bash_command=‘test -f “${dist_binary_build_folder}/Whonix-Gateway-${dist_build_desktop}-${dist_build_version}.${target_architecture_pretty_name}.raw”’
++ ‘[’ ‘!’ ‘’ = ‘’ ‘]’
++ true ‘INFO: Skipping dist_build_dispatch_after_retry (–retry-after), because empty, ok.’
++ ‘[’ 1 = 0 ‘]’
++ exception_handler_process_shared ‘NONE_(called_by_exception_handler_retry)’
++ last_script=/usr/bin/dm-prepare-release
++ trap_signal_type_previous=‘NONE_(called_by_exception_handler_retry)’
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = ‘’ ‘]’
++ trap_signal_type_last=‘NONE_(called_by_exception_handler_retry)’
++ dist_build_error_counter=3
+++ benchmarktimeend 1736043381
++++ date +%s
+++ benchmarktimeend=1736044210
+++ benchmark_took_seconds=829
++++ convertsecs 829
++++ local h m s
++++ (( h=829/3600 ))
++++ true
++++ (( m=(829%3600)/60 ))
++++ (( s=829%60 ))
++++ printf ‘%02d:%02d:%02d\n’ 0 13 49
+++ echo 00:13:49
++ benchmark_took_time=00:13:49
++ local first
++ read -r first _
++ process_backtrace_function
++ true ‘INFO: BEGIN: process_backtrace_function’
++ ‘[’ -o xtrace ‘]’
++ set +x
++ true ‘INFO: END : process_backtrace_function’
++ function_trace_function
++ true ‘INFO: BEGIN: function_trace_function’
++ ‘[’ -o xtrace ‘]’
++ set +x
++ true ‘INFO: END : function_trace_function’
++ output_cmd_set
++ ‘[’ -o xtrace ‘]’
++ output_cmd=true
++ true ’
############################################################
ERROR detected in script!: /usr/bin/dm-prepare-release
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.7
dist_build_error_counter: 3
benchmark: 00:13:49
last_failed_exit_code: 1
trap_signal_type_previous: NONE_(called_by_exception_handler_retry)
trap_signal_type_last : NONE_(called_by_exception_handler_retry)
process_backtrace_result:
1: : init
2: : /lib/systemd/systemd --user
3: : /usr/libexec/gnome-terminal-server
4: : bash
5: : /bin/bash /home/anubis/derivative-maker/derivative-maker --flavor whonix-workstation-xfce --target utm --arch arm64 --tb open --repo true --vmsize 25G
6: : /bin/bash ././build-steps.d/5200_prepare-release --flavor whonix-workstation-xfce --target utm --arch arm64 --tb open --repo true --vmsize 25G
7: : /bin/bash /usr/bin/dm-prepare-release --flavor whonix-workstation-xfce --target utm --arch arm64 --tb open --repo true --vmsize 25G
function_trace_result:
main (line number: 659)
main (line number: 652)
libvirt_compress (line number: 194)
exception_handler_general (line number: 194)
exception_handler_process_shared (line number: 194)
exception_handler_retry (line number: 194)
exception_handler_process_shared (line number: 194)
exception_handler_retry (line number: 194)
exception_handler_process_shared (line number: 194)
main (line number: 659)
main (line number: 652)
libvirt_compress (line number: 194)
exception_handler_general (line number: 194)
exception_handler_process_shared (line number: 194)
exception_handler_process_shared (line number: 194)
exception_handler_retry (line number: 194)
exception_handler_process_shared (line number: 194)
exception_handler_general (line number: 194)
libvirt_compress (line number: 194)
main (line number: 652)
main (line number: 659)
last_failed_bash_command: test -f “${dist_binary_build_folder}/Whonix-Gateway-${dist_build_desktop}-${dist_build_version}.${target_architecture_pretty_name}.raw”
############################################################
’
++ unset error_reason
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = INT ‘]’
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = TERM ‘]’
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = ERR ‘]’
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = ‘NONE_(called_by_exception_handler_retry)’ ‘]’
++ ‘[’ ‘!’ 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=
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = ERR ‘]’
++ ‘[’ ‘NONE_(called_by_exception_handler_retry)’ = ‘NONE_(called_by_exception_handler_retry)’ ‘]’
++ ‘[’ ‘’ = true ‘]’
++ ‘[’ -t 0 ‘]’
++ true ‘INFO: stdin connected to terminal, using interactive error handler.’
++ true 'ERROR: An issue in /usr/bin/dm-prepare-release has been detected!
User Help Message 1/2:
Please READ this message carefully.
Copying/pasting/screenshotting this error message alone will not be insightful, and no help can be provided with it alone as it does not contain comprehensive information by itself. Instead, please scroll up and review the block encapsulated within ### for more detailed information.
For support queries, it is essential to, at minimum, provide the portion of the log located above this message containing the actual error details. In many instances, providing a longer segment or the entire log may be necessary for an effective diagnosis.
Regrettably, assistance cannot be provided without the aforementioned details.
Options:
Choose either option A), B), C) or D).
- A) Press c and press enter to bypass this error and continue with the build. (For Developers Only!) (Strongly discouraged for regular users as it may lead to unstable builds! Please refrain from reporting any issues encountered subsequently!)
- B) Press r and enter to retry.
- C) Press s and enter to initiate a chroot interactive shell. (For Developers Only!)
- D) Press a and enter to abort.
#####’
++ read -p 'Answer? ’ answer
Answer?