From 40b4dcd0523b4753d57b91d29ecd72b90625d95c Mon Sep 17 00:00:00 2001 From: vasilito Date: Fri, 24 Jul 2026 09:46:20 +0900 Subject: [PATCH] build-redbear.sh: fix set -e abort when any fork is dirty MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The stash loop ended with '[ any_dirty = 0 ] && echo ...' as the function's last command — when a fork IS dirty (any_dirty=1), the compound returns 1 and set -e kills the build silently right after the stash phase. Only visible with REDBEAR_ALLOW_DIRTY=1 (the dirty gate refuses earlier otherwise). Now an explicit if + return 0. --- local/scripts/build-redbear.sh | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/local/scripts/build-redbear.sh b/local/scripts/build-redbear.sh index e0a2cbe840..da3f09f9be 100755 --- a/local/scripts/build-redbear.sh +++ b/local/scripts/build-redbear.sh @@ -175,7 +175,10 @@ redbear_stash_all_dirty_forks() { exit 1 } done - [ "$any_dirty" = "0" ] && echo " (all fork sources clean)" + if [ "$any_dirty" = "0" ]; then + echo " (all fork sources clean)" + fi + return 0 } redbear_unstash_all_forks() {