The packages app is running on Fedora 30, and its dependencies are not
available in Fedora 31+ as I understand it.
This means it has about 7 months before we need to do something about
it, or shut it off.
Do we know if it can run on RHEL 7?
Good Morning Everyone,
This morning as I was trying to build a new distgit-bugzilla-sync build in
staging, I ran into the issue that the build never started.
It seems it was related to openshift not being able to resolve correctly:
Once Clément pointed me to the right direction, I adjusted staging as follow:
and I was able to do a new build.
I would like to apply the same fix to production (ie:
The following packages showed up on the orphan list (for being FTBFS).
We use and should take these over:
Any objections to having infra-sig take them?
(I couldn't figure out how to do this in the pagure web interface tho)
Then at least we need folks to fix them so they build.
Per ticket 8847, moving this cron job to 10pm will let it run and finish before the larger
and longer cron script runs to update the docs site. This will prevent overlap and get
updates out a day sooner in some cases.
Signed-off-by: Kevin Fenzi <kevin(a)scrye.com>
roles/fedora-docs/translation/files/cron-docs-translation-update | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/fedora-docs/translation/files/cron-docs-translation-update b/roles/fedora-docs/translation/files/cron-docs-translation-update
index bf91755..5a0627b 100644
@@ -1,2 +1,2 @@
-0 2 * * * _update_docs_trans /usr/local/bin/lock-wrapper cron-docs-translation-update "/usr/local/bin/docs-translation-update"
+0 22 * * * _update_docs_trans /usr/local/bin/lock-wrapper cron-docs-translation-update "/usr/local/bin/docs-translation-update"
You are kindly invited to the meeting:
Fedora Infrastructure on 2020-04-23 from 15:00:00 to 16:00:00 UTC
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before.
I have been playing a little bit around with the koji-ansible collection
and created a Proof of Concept playbook that creates the main tags for a
release in koji (staging).
I have installed the collection on batcave01 running the following
ansible-galaxy collection install
And the playbook is available under
playbooks/manual/releng/koji-release-tags.yml . For now there is still
very much a lot of things hard coded, but that should give us a good idea
of what we can do with that collection.
Members of the sysadmin-main group can try the playbook by running
For now it is executed on `composer.stg.phx2.fedoraproject.org` and it is
using this host keytab to authenticate with koji.
I ll keep working on this and see if I can turn it in a role that could be
used to create all the tags for each release, in the mean time if you have
ideas or feedback please share them with me :-).
This is for the RDU-CC expansion. We have these "zones" but these are not
subroutes (aka 18.104.22.168 is live and not a network high)
Fedora 6 22.214.171.124/29
Fedora 7 126.96.36.199/29
Fedora 8 188.8.131.52/29
Fedora 9 184.108.40.206/29
Fedora 10 220.127.116.11/29
Fedora 11 18.104.22.168/29
diff --git a/roles/batcave/files/allows b/roles/batcave/files/allows
index 793718f..850c5e0 100644
@@ -98,6 +98,31 @@ require ip 22.214.171.124
require ip 126.96.36.199
# rdu2 community cage machines
+# this doesn't sit on network boundaries and from no longer exists in 2.4
+require ip 188.8.131.52
+require ip 184.108.40.206
+require ip 220.127.116.11
+require ip 18.104.22.168
+require ip 22.214.171.124
+require ip 126.96.36.199
+require ip 188.8.131.52
+require ip 184.108.40.206
+require ip 220.127.116.11
+require ip 18.104.22.168
+require ip 22.214.171.124
+require ip 126.96.36.199
+require ip 188.8.131.52
+require ip 184.108.40.206
+require ip 220.127.116.11
+require ip 18.104.22.168
+require ip 22.214.171.124
+require ip 126.96.36.199
+require ip 188.8.131.52
+require ip 184.108.40.206
+require ip 220.127.116.11
+require ip 18.104.22.168
+require ip 22.214.171.124
+require ip 126.96.36.199
require ip 188.8.131.52
require ip 184.108.40.206
require ip 220.127.116.11
@@ -114,6 +139,14 @@ require ip 18.104.22.168
require ip 22.214.171.124
require ip 126.96.36.199
require ip 188.8.131.52
+require ip 184.108.40.206
+require ip 220.127.116.11
+require ip 18.104.22.168
+require ip 22.214.171.124
+require ip 126.96.36.199
+require ip 188.8.131.52
+require ip 184.108.40.206
+require ip 220.127.116.11
# ec2 instances
Stephen J Smoogen.