Hi all,

So, I just found that we were actually somewhat lucky in that the f28 push worked, because it checked with aarch64 on the primary location and aarch64 happens to be primary for f28.

Can I get +1s to set the primary arch list in Bodhi for f28?

Randy is going to work with releng to get it in the branching/bodhi enablement SOP.

I also needed to update the name of the modular compose.

Patrick

diff --git a/roles/bodhi2/base/templates/production.ini.j2 b/roles/bodhi2/base/templates/production.ini.j2

index a49cfb306..005291f21 100644

--- a/roles/bodhi2/base/templates/production.ini.j2

+++ b/roles/bodhi2/base/templates/production.ini.j2

@@ -260,6 +260,7 @@ base_address = https://bodhi{{env_suffix}}.fedoraproject.org/

# fedora_26_primary_arches = armhfp x86_64

fedora_26_primary_arches = armhfp x86_64

fedora_27_primary_arches = armhfp x86_64

+fedora_28_primary_arches = aarch64 armhfp x86_64

## Email setting

[puiterwijk@workstation base (master * u=)]$ vim^C

[puiterwijk@workstation base (master * u=)]$ cd ..

[puiterwijk@workstation bodhi2 (master * u=)]$ vim backend/files/new-updates-sync

g[puiterwijk@workstation bodhi2 (master * u=)]$ git diff

diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync

index 14f1adb1f..827e8cfcd 100755

--- a/roles/bodhi2/backend/files/new-updates-sync

+++ b/roles/bodhi2/backend/files/new-updates-sync

@@ -39,7 +39,7 @@ RELEASES = {'f28': {'topic': 'fedora',

'version': '28m',

'modules': ['fedora', 'fedora-secondary'],

'repos': {'updates-testing': {

- 'from': 'f28m-updates-testing',

+ 'from': 'f28-modular-updates-testing',

'ostrees': [],

'to': [{'arches': ['x86_64', 'aarch64', 'armhfp', 'source'],

'dest': os.path.join(FEDORADEST, 'testing', '28', 'Modular')},