When setting things up, we failed to setup the updates sync job to sync new f26 updates. This is needed now that we have enabled bodhi.
So we need to apply the following patch, ansible it out to bodhi-backend01, and then also create empty repos in /mnt/koji/mash/updates for f26-updates and f26-updates-testing.
The f26-updates-testing link will repoint to the first f26-updates-testing bodhi push (later tonight) and the f26-updates one will stay pointed at the empty repo until we are ready to stage 0 day updates.
+1s?
kevin -- diff --git a/roles/bodhi2/backend/files/fedora-updates-push b/roles/bodhi2/backend/files/fedora-updates-push index d8c9227..9b5025d 100755 --- a/roles/bodhi2/backend/files/fedora-updates-push +++ b/roles/bodhi2/backend/files/fedora-updates-push @@ -7,7 +7,7 @@ ATOMICDEST=/mnt/koji/atomic/
OPTIONS="-rlptDvHh --stats --delay-updates $RSYNC_OPTS"
-for rel in 24 25; do +for rel in 24 25 26; do
OUTPUT1=$(rsync $OPTIONS --exclude "repodata/*" \ $SOURCE/f$rel-updates/ $DEST/$rel/ --link-dest $DEST/testing/$rel/) @@ -28,7 +28,7 @@ for rel in 24 25; do fi
done -for rel in 24 25; do +for rel in 24 25 26; do
OUTPUT1=$(rsync $OPTIONS --exclude "repodata/*" \ $SOURCE/f$rel-updates-testing/ $DEST/testing/$rel/)
ok, after talking to Dennis we need something more complex here since we want to sync some of the arches to fedora-secondary and some to fedora.
As a bonus it would be cool if we could just scrap this sync script entirely and replace it with a loopabull script that watches for bodhi being done with things and syncs just exactly those things.
kevin
infrastructure@lists.fedoraproject.org