From 22ce1d0d6d2eb6fb779622f2017ae6af080cef85 Mon Sep 17 00:00:00 2001
From: ScottW514 <s.e.wiederhold@gmail.com>
Date: Mon, 31 Aug 2026 16:26:55 -0400
Subject: [PATCH] kas: the debug image gets its own deploy name

forgefirm-image-dev has one deploy slot, so the debug variant was
clobbering the normal dev image (and a dev rebuild clobbered the debug
one back). A distinct IMAGE_BASENAME (forgefirm-image-dev-debug) lets
both coexist in the deploy directory.
---
 kas/forgefirm-glowforge-debug.yml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/kas/forgefirm-glowforge-debug.yml b/kas/forgefirm-glowforge-debug.yml
index 30c1a32..f150851 100644
--- a/kas/forgefirm-glowforge-debug.yml
+++ b/kas/forgefirm-glowforge-debug.yml
@@ -30,3 +30,7 @@ local_conf_header:
     FORGEFIRM_KERNEL_DEBUG = "1"
     FORGEFIRM_VERSION_STRING:pn-forgefirm-image-dev = "${DATETIME} (dev-debug)"
     FORGEFIRM_VERSION_STRING[vardepsexclude] += "DATETIME"
+    # A distinct deploy basename so the debug image does not share the dev
+    # image's single deploy slot and clobber it. It lands as
+    # forgefirm-image-dev-debug-glowforge.rootfs-*.wic.gz beside the others.
+    IMAGE_BASENAME:pn-forgefirm-image-dev = "forgefirm-image-dev-debug"