[PATCH] Add f30-flatpak to the list of tags we sync
by Owen Taylor
From: "Owen W. Taylor" <otaylor(a)fishsoup.net>
We're now building Fedora 30 Flatpaks based on the F30 runtime, so
we need to populate the f30-flatpak tag based on the contents of
Pagure.
---
roles/bodhi2/backend/files/koji-sync-listener.py | 2 +-
roles/bodhi2/backend/tasks/main.yml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/roles/bodhi2/backend/files/koji-sync-listener.py b/roles/bodhi2/backend/files/koji-sync-listener.py
index 5d65cc164..1ea07ad53 100644
--- a/roles/bodhi2/backend/files/koji-sync-listener.py
+++ b/roles/bodhi2/backend/files/koji-sync-listener.py
@@ -23,7 +23,7 @@ def handle(content):
sys.stdout.flush()
# XXX If you modify this taglist. Please also modify the other copy in
# bodhi2/backend/tasks/main.yml
- taglist = 'f31 f31-container f31-modular f30 f30-container f30-modular f29 f29-container f29-flatpak f29-modular epel7 dist-6E-epel module-package-list modular'
+ taglist = 'f31 f31-container f31-modular f30 f30-container f30-flatpak f30-modular f29 f29-container f29-flatpak f29-modular epel7 dist-6E-epel module-package-list modular'
cmd = [
'/usr/local/bin/owner-sync-pagure',
'--package', package,
diff --git a/roles/bodhi2/backend/tasks/main.yml b/roles/bodhi2/backend/tasks/main.yml
index 8867d11da..13014d08e 100644
--- a/roles/bodhi2/backend/tasks/main.yml
+++ b/roles/bodhi2/backend/tasks/main.yml
@@ -65,7 +65,7 @@
# bodhi2/backend/files/koji-sync-listener.py
# This cronjob runs only once a day. The listener script runs reactively.
cron: name="owner-sync" minute="15" hour="4" user="root"
- job="/usr/local/bin/lock-wrapper owner-sync '/usr/local/bin/owner-sync-pagure f31 f31-container f31-modular f30 f30-container f30-modular f29 f29-container f29-flatpak f29-modular epel7 dist-6E-epel module-package-list modular'"
+ job="/usr/local/bin/lock-wrapper owner-sync '/usr/local/bin/owner-sync-pagure f31 f31-container f31-modular f30 f30-container f30-flatpak f30-modular f29 f29-container f29-flatpak f29-modular epel7 dist-6E-epel module-package-list modular'"
cron_file=update-koji-owner
when: env == "production"
tags:
--
2.21.0
4 years, 10 months
state of koji work
by Kevin Fenzi
Greetings.
Since I am out on PTO all next week, I thought I would share a status of
where we are with koji so others could continue the work in my absense.
We have a number of things that need updates on koji builders.
* mock 1.4.15+ is needed for dynamic buildrequires
* createrepo_c 0.14.1-2+ is needed for epel8/fedora non modular builds
against modules
* koji build with backported patches for:
** seperate srpm repos with buildroot source repos
** bare mode repo merging needed for epel8/fedora buildroot
** dynamic buildrequires (along with newer mock)
* oz and imagefactory have gone python3 in f31/rawhide, and oz isn't
installable in f30 anymore.
So, I have built a koji in rawhide with all the patches we need.
I have then built in f29/f30-infra tags all the stuff we need:
koji with patches
createrepo_c
oz
imagefactory
A sticking point for updating has been that our armv7 builders are stuck
on f27 due to a kernel (or perhaps userspace?) bug that causes then to
pause when doing kernel/glibc/other builds. pbrobinson and pwhalen are
trying to isolate this and fix it, but until then it looks like we can
move them to fedora 29 + a specific older kernel. I have setup a
kickstart that installs this kernel and set ansible to disallow
dnf-automatic updating the kernel on them.
I've been testing with buildvm-armv7-22 in prod, and
buildvm-armv7-01.stg in staging, and so far they have survived several
kernel builds.
I have updated all of staging with the above packages.
What still needs doing next week:
* reinstall all the prod armv7 builders with the f29 kickstart and
confirm they don't blow up.
* promote createrepo_c, koji, oz, imagefactory builds from f29-infra-stg
to f29-infra, and epel7-infra-stg to epel7-infra
* update koji hubs and all builders to above packages.
* watch for problems with oz/imagefactory/createrepo_c/koji and fix or
revert.
* profit
After I get back we can look at moving to f30, but for now f29 should
work. Hopefully by then we will have figured out the armv7 issue and be
able to move them to the latest kernel.
I might have time later tonight/tomorrow to work further on this, but
not sure I will. If so, I'll update this thread. If not, it will have to
wait until I get back from vacation, or someone else will need to move
it forward next week.
Thanks,
kevin
4 years, 11 months