Good Morning Everyone,
The Atomic CI pipeline running at:
is running on Fedora 27 but greenwave hasn't been instructed to gate based on
So I would like to make the following change to greenwave's policy and run the
greenwave playbook that should rebuild the containers with the new policy.
@@ -136,6 +136,7 @@ data:
+ - fedora-27
There was a bit of a severe bug introduced with Bodhi 3.5.1 that I would
like to create a 3.5.2 release to address. Patrick has already hotfixed
production so the issue is technically not present there, but we also
technically now have a non-reproducible deployment (since there isn't an
RPM with the fix yet). For cleanliness, I'd like to make and deploy a
3.5.2 with that patch, though I could see an argument to wait for the
freeze to lift if that is preferrable. The patch is actually quite small.
My name is Leonardo Rossetti, nickname Leo, I am currently located in São
Paulo - Brazil (GMT-3) and my irc username in freenode is "lrossetti".
I have been working as a software engineer for the last 10 years with a
focus on automation and backend services (with a particular heavy usage in
My most recent work is an open source project that enables mobile ci/cd on
top of openshift and jenkins.
I am currently employed by Red Hat but I am joining as an individual and
not on behalf of my employer.
I've been using fedora for a while now (former debian and slackware user)
so I started looking on how to contribute it back to fedora and that's how
I found about the fedora infrastructure community.
I would like to work on this issue if possible:
https://pagure.io/fedora-infrastructure/issue/6505 (I am already familiar
I would like to learn more about fedora's infrastructure and its system
environment with a low level flavor if possible (I began to study linux
kernel modules development a few months ago).
I can currently work around 20 hours a week since I would be using my free
time to work on any issues - Looking forward to meet a mentor :)
 - https://github.com/aerogear/aerogear-digger
Last Friday, pungi got updated on compose-x86-01, but that requires fedmsg-1.1.0 (there's currently 1.0.1 on that box) because of json encoding issues.
+1 to run "dnf update --refresh fedmsg" on compose-x86-01?
Our cert for whatcanidoforfedora.org expired.
I've renewed the cert and deployed it. I had to run the proxy playbook
with -t whatcanidoforfedora.org, which caused an httpd reload on
proxies to see the new cert.
Retroactive +1's please.