From b986f402cbbc5c0b9efbb3e754933bd5079a2a1c Mon Sep 17 00:00:00 2001 From: Mattia Verga Date: Fri, 9 Feb 2024 17:45:53 +0100 Subject: [PATCH] bodhi: fix config for override inheritance Signed-off-by: Mattia Verga --- roles/bodhi2/base/templates/production.ini.j2 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/roles/bodhi2/base/templates/production.ini.j2 b/roles/bodhi2/base/templates/production.ini.j2 index fe118d7457..e2cf15f19b 100644 --- a/roles/bodhi2/base/templates/production.ini.j2 +++ b/roles/bodhi2/base/templates/production.ini.j2 @@ -623,11 +623,11 @@ buildroot_overrides.expire_after = 1 # You can have releases to extend its buildroot override tags from other releases. # When submitting a Buildroot Override for that Release, the build will be tagged # with the override_tag of its Release AND the override tags of the inherited releases. -# Left Release.name goes lowercase, right Release.names must be specified exactly. +# Left uses Release.setting_prefix, right uses Release.name. # Below is an example, all EPEL-9 builds submitted as buildroot overrides will also # be tagged as EPEL-9N and EPEL-8 overrides. -# epel-9.override-extend = EPEL-9N,EPEL-8 -epel-9.override-extend = EPEL-9N +# epel9.override-extend = EPEL-9N,EPEL-8 +epel9.override-extend = EPEL-9N ##