From 01ea5ed7139296dd5675c7a8715e83272a96ad74 Mon Sep 17 00:00:00 2001 From: Peter Robinson Date: Tue, 28 Apr 2020 11:32:37 +0100 Subject: [PATCH] IoT: Update F-32 for stable ostree branch Signed-off-by: Peter Robinson --- fedora-iot.ks | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fedora-iot.ks b/fedora-iot.ks index e8d53d7..d212313 100644 --- a/fedora-iot.ks +++ b/fedora-iot.ks @@ -19,7 +19,7 @@ autopart --nohome --noswap --type=plain # Equivalent of %include fedora-repo.ks # Pull from the ostree repo that was created during the compose -ostreesetup --nogpg --osname=fedora-iot --remote=fedora-iot --url=https://kojipkgs.fedoraproject.org/compose/iot/repo/ --ref=fedora/devel/${basearch}/iot +ostreesetup --nogpg --osname=fedora-iot --remote=fedora-iot --url=https://kojipkgs.fedoraproject.org/compose/iot/repo/ --ref=fedora/stable/${basearch}/iot reboot @@ -41,14 +41,14 @@ fi # Set the origin to the "main ref", distinct from /updates/ which is where bodhi writes. # We want consumers of this image to track the two week releases. -ostree admin set-origin --index 0 fedora-iot https://dl.fedoraproject.org/iot/repo/ "fedora/devel/${arch}/iot" +ostree admin set-origin --index 0 fedora-iot https://dl.fedoraproject.org/iot/repo/ "fedora/stable/${arch}/iot" # Make sure the ref we're supposedly sitting on (according # to the updated origin) exists. -ostree refs "fedora-iot:fedora/devel/${arch}/iot" --create "fedora-iot:fedora/devel/${arch}/iot" +ostree refs "fedora-iot:fedora/stable/${arch}/iot" --create "fedora-iot:fedora/stable/${arch}/iot" # Remove the old ref so that the commit eventually gets cleaned up. -ostree refs "fedora-iot:fedora/devel/${arch}/iot" --delete +ostree refs "fedora-iot:fedora/stable/${arch}/iot" --delete # delete/add the remote with new options to enable gpg verification # and to point them at the cdn url