[PATCH 1/2] new-updates-sync: it's silverblue now [PATCH 2/2] new-updates-sync: sync the base ref for now until f29
The previous revert somehow made it so that f29 went back to workstation and not silverblue. Fix that. --- roles/bodhi2/backend/files/new-updates-sync | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index 3bcfbea13..57fb457fc 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -28,10 +28,10 @@ RELEASES = {'f29': {'topic': 'fedora', 'ostrees': [{'ref': 'fedora/29/%(arch)s/updates/atomic-host', 'dest': ATOMICDEST, 'arches': ['x86_64', 'ppc64le', 'aarch64']}, - {'ref': 'fedora/29/x86_64/updates/workstation', + {'ref': 'fedora/29/x86_64/updates/silverblue', 'dest': ATOMICDEST}, # Hack around for the fact that ostree on f25 doesn't know links - {'ref': 'fedora/29/x86_64/workstation', + {'ref': 'fedora/29/x86_64/silverblue', 'dest': ATOMICDEST}], 'to': [{'arches': ['x86_64', 'armhfp', 'aarch64', 'source'], 'dest': os.path.join(FEDORADEST, '29', 'Everything')}, @@ -43,7 +43,7 @@ RELEASES = {'f29': {'topic': 'fedora', 'ostrees': [{'ref': 'fedora/29/%(arch)s/testing/atomic-host', 'dest': ATOMICDEST, 'arches': ['x86_64', 'ppc64le', 'aarch64']}, - {'ref': 'fedora/29/x86_64/testing/workstation', + {'ref': 'fedora/29/x86_64/testing/silverblue', 'dest': ATOMICDEST}], 'to': [{'arches': ['x86_64', 'aarch64', 'armhfp', 'source'], 'dest': os.path.join(FEDORADEST, 'testing', '29', 'Everything')},
Until f29 is released lets sync over the base ref so that people who are running beta can get updates or people who want to can rebase. --- roles/bodhi2/backend/files/new-updates-sync | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index 57fb457fc..cbc8b9300 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -28,9 +28,13 @@ RELEASES = {'f29': {'topic': 'fedora', 'ostrees': [{'ref': 'fedora/29/%(arch)s/updates/atomic-host', 'dest': ATOMICDEST, 'arches': ['x86_64', 'ppc64le', 'aarch64']}, + # sync base ref for now until f29 is released + {'ref': 'fedora/29/%(arch)s/atomic-host', + 'dest': ATOMICDEST, + 'arches': ['x86_64', 'ppc64le', 'aarch64']}, {'ref': 'fedora/29/x86_64/updates/silverblue', 'dest': ATOMICDEST}, - # Hack around for the fact that ostree on f25 doesn't know links + # sync base ref for now until f29 is released {'ref': 'fedora/29/x86_64/silverblue', 'dest': ATOMICDEST}], 'to': [{'arches': ['x86_64', 'armhfp', 'aarch64', 'source'],
On 10/01/2018 01:57 PM, Kevin Fenzi wrote:
On 10/01/2018 10:25 AM, Dusty Mabe wrote:
[PATCH 1/2] new-updates-sync: it's silverblue now [PATCH 2/2] new-updates-sync: sync the base ref for now until f29
+1 here.
pushed!
Let me know if you would like me to run the playbook for you.
yes please!
infrastructure@lists.fedoraproject.org