public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/edk2] rawhide: drop testonly secboot builds
Date: Fri, 07 Aug 2026 11:55:06 GMT	[thread overview]
Message-ID: <178610370608.1.7076747927068400133.rpms-edk2-bf28c2d07aac@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/edk2
            Branch : rawhide
            Commit : bf28c2d07aaccb32f6fe9aec2ca2f62737ca6906
            Author : Gerd Hoffmann <kraxel@redhat.com>
            Date   : 2026-08-07T11:54:53+00:00
            Stats  : +0/-18 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/edk2/c/bf28c2d07aaccb32f6fe9aec2ca2f62737ca6906?branch=rawhide

            Log:
            drop testonly secboot builds

now that we have proper secure boot support for arm via qemu variable
store it is rather pointless to keep these.

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>

---
diff --git a/edk2-build.fedora b/edk2-build.fedora
index b4ee0e4..dc5bc45 100644
--- a/edk2-build.fedora
+++ b/edk2-build.fedora
@@ -312,20 +312,6 @@ cpy1 = FV/QEMU_EFI.fd  QEMU_EFI.strictnx.fd
 cpy3 = FV/QEMU_EFI.fd  QEMU_EFI-strictnx-pflash.raw
 pad3 = QEMU_EFI-strictnx-pflash.raw  64m
 
-[build.armvirt.aa64.secboot.testonly]
-desc = ArmVirt build for qemu, 64-bit (arm v8), secure boot
-conf = ArmVirtPkg/ArmVirtQemu.dsc
-arch = AARCH64
-opts = ovmf.common
-       armvirt.verbose
-       armvirt.sb.testonly
-pcds = nx.strict
-plat = ArmVirtQemu-AArch64
-dest = Fedora/experimental
-cpy1 = FV/QEMU_EFI.fd  QEMU_EFI.secboot.testonly.fd
-cpy3 = FV/QEMU_EFI.fd  QEMU_EFI-secboot-testonly-pflash.raw
-pad3 = QEMU_EFI-secboot-testonly-pflash.raw  64m
-
 
 #####################################################################
 # standalone efi shell

diff --git a/edk2.spec b/edk2.spec
index 4a9170c..00c8979 100644
--- a/edk2.spec
+++ b/edk2.spec
@@ -552,10 +552,6 @@ cp DBXUpdate-%{DBXDATE}.aa64.bin %{RHELCFG}/aarch64
 %else
 ./edk2-build.py --config edk2-build.fedora %{?silent} --release-date "$RELEASE_DATE" -m armvirt
 ./edk2-build.py --config edk2-build.fedora.platforms %{?silent} -m aa64
-virt-fw-vars --input   Fedora/aarch64/vars-template-pflash.raw \
-             --output  Fedora/experimental/vars-template-secboot-testonly-pflash.raw \
-             --set-dbx DBXUpdate-%{DBXDATE}.aa64.bin \
-             --enroll-redhat --secure-boot --distro-keys rhel
 %if %{qemuvars}
 virt-fw-vars --output-json Fedora/aarch64/vars.blank.json
 virt-fw-vars --output-json Fedora/aarch64/vars.secboot.json \

                 reply	other threads:[~2026-08-07 11:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178610370608.1.7076747927068400133.rpms-edk2-bf28c2d07aac@fedoraproject.org \
    --to=kraxel@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox