From 79a32b324d1793ca4a9484b6f0950755cb8e8218 Mon Sep 17 00:00:00 2001
From: Gunnar Wolf <gwolf@gwolf.org>
Date: Thu, 23 Aug 2018 09:15:18 -0500
Subject: [PATCH] Fix the chroot step introduced in my previous commit

${ROOT?} does not make sense within a chroot, was causing the build to fail
---
 raspi3.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/raspi3.yaml b/raspi3.yaml
index 3ba7880..3c71e85 100644
--- a/raspi3.yaml
+++ b/raspi3.yaml
@@ -128,7 +128,7 @@ steps:
   # the partition labeled raspiroot instead of forcing it to mmcblk0p2
   - chroot: root-fs
     shell: |
-      sed -i 's/.dev.mmcblk0p2/LABEL=raspiroot/' ${ROOT?}/boot/firmware/cmdline.txt
+      sed -i 's/.dev.mmcblk0p2/LABEL=raspiroot/' /boot/firmware/cmdline.txt
 
   # TODO(https://github.com/larswirzenius/vmdb2/issues/24): remove once vmdb
   # clears /etc/resolv.conf on its own.