From f22af41f0fabca4e3fd62b6c9085fe0f65ef8266 Mon Sep 17 00:00:00 2001
From: Adam Williamson <awilliam@redhat.com>
Date: Wed, 23 Aug 2023 16:12:57 -0700
Subject: [PATCH] ostree: avoid rebasing from F39+ to <F39

Now F39 has branched from Rawhide, we can tweak the rebase logic
to never rebase from F39+ to <F39, and avoid
https://github.com/fedora-silverblue/issue-tracker/issues/470 .

Signed-off-by: Adam Williamson <awilliam@redhat.com>
---
 tests/rpmostree_rebase.pm | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/tests/rpmostree_rebase.pm b/tests/rpmostree_rebase.pm
index d00de387..16791b25 100644
--- a/tests/rpmostree_rebase.pm
+++ b/tests/rpmostree_rebase.pm
@@ -33,12 +33,21 @@ sub run {
     my $rebase;
     my $target;
     if ($current =~ "iot") {
-        $rebase = $current =~ "stable" ? "devel" : "stable";
+        # previously we did this:
+        #$rebase = $current =~ "stable" ? "devel" : "stable";
+        # but we cannot rebase from F39+ to <F39:
+        # https://github.com/fedora-silverblue/issue-tracker/issues/470
+        #  so let's make sure we don't do that. This can be reverted
+        # when F39 is stable
+        $rebase = $current =~ "devel" ? "rawhide" : "devel";
         $target = "fedora/${rebase}/${arch}/iot";
     }
     elsif ($current =~ "silverblue") {
         my $relnum = get_release_number;
         $rebase = $relnum - 1;
+        # avoid rebasing 39 > 38 due to
+        # https://github.com/fedora-silverblue/issue-tracker/issues/470
+        $rebase = "40" if ($rebase eq "38");
         # on update tests, just rebase to the 'official' ref for the
         # release, as opposed to the custom ref we used when building;
         # this should be more reliable than a different release