As you can read here, the Fedora Join SIG is experimenting a new way
to help people become part of the community.
This workflow includes also a temporary FAS group if required or asked
by the newcomer. Since this overlaps with the current "wikiedit"
system, we were wondering if it'd make sense to retire it and send
newcomers to the Fedora Join channels instead where they can speak to
community members and take their time learning/exploring the community
and it's projects.
It'll be one less responsibility for the infra team, and it'll help us
channel folks to the new workflow.
Please let us know if this sounds OK and we'll edit the wiki page here
We'll send out more posts announcing the new workflow to the community
this week. If you have the cycles, please hang out in the Fedora Join
There are problems with the vcglib package
vcglib review request:
$ kinit mufti11(a)FEDORAPROJECT.ORG
Password for mufti11(a)FEDORAPROJECT.ORG:
$ fedpkg clone vcglib
Cloning into 'vcglib'...
No such repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Failed to execute command.
Did i something wrong ?
There is work in progress to migrate our applications from the current
message bus 'fedmsg' to the AMPG based 'fedora-messaging'.
Attached are a couple of patches that prepare our ansible scripts for this.
Please review those patches and comment, thanks !
In the interest of helping to modernize the infrastructure Fedora runs
on, I'm working on introducing Pagure into EPEL8. This will hopefully
allow us to upgrade our Pagure instances to use RHEL 8 instead of RHEL
7, and notably, make the transition (mostly) complete for moving all
Python software Fedora runs to Python 3.
I've done an early build locally to determine what's needed to make
this possible. The following report from DNF indicates the missing
packages that need to be added to EPEL 8 before I can introduce Pagure
Problem 1: conflicting requests
- nothing provides python3-jenkins needed by pagure-ci-5.8-1.el8.noarch
Problem 2: conflicting requests
- nothing provides gitolite3 needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(binaryornot) needed by
- nothing provides python3.6dist(celery) needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(flask-wtf) needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(redis) needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(straight.plugin) needed by
- nothing provides python3.6dist(wtforms) needed by pagure-5.8-1.el8.noarch
- nothing provides python3.6dist(pygit2) >= 0.26.0 needed by
Problem 3: conflicting requests
- nothing provides python3-trololio needed by pagure-ev-5.8-1.el8.noarch
One of the reasons I'd like to have this done sooner rather than later
is so that we can drop Python 2 support from Pagure with version 6.0.
I think it's quite reasonable to say that version 6.0 isn't going to
happen until we can get our Pagure servers running on EL8 using Python
So now, I need some help making this happen. I already own trololio,
and I'm going to make that available in EPEL 8 ASAP. Can anyone help
with some of the other dependencies here?
Thanks in advance,
真実はいつも一つ！/ Always, there's only one truth!
>> I want to approve the review request of vimvi-qt, but this is my first
>> offical review 8-(
> You need to set fedora-review+ flag. Click on "Show advanced fields" near
> the top of the bug, and flags should be visible in a drop-down menu on
> the right.
| I still don't find it 8-(
| Mufti, it's weird that your screenshot shows that you can set the
| fedora-review flag to ? but not to +. Maybe file a ticket with
| infra---possibly Bugzilla didn't sync with FAS properly or something?
Can you help me ?
Travelling yesterday saw a delay in sending this weeks CPE email
blast, but nevertheless, here it is!
Hope everyone has been having a great weekend and if you have any
comments or feedback, please let me know- it is always welcome :)
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Our goal is to keep
core servers and services running and maintained, build releases, and
other strategic tasks that need more dedicated time than volunteers
For better communication, we will be giving weekly reports to the
CentOS and Fedora communities about the general tasks and work being
done. Also for better communication between our groups we have
created #redhat-cpe on Freenode IRC! Please feel free to catch us
there, a mail has landed on both the CentOS and Fedora devel lists
with context here.
This document is currently built from individual reports rolled into a
google document which we edit and copy into a final document. We are
aware that this causes problems with some email readers, and are
working on a method to make this less problematic.
High Level Project Updates:
Bodhi 5.0 has been deployed in production
We received some feedback about the changes in the UI and are looking
at how we can address them.
We are working on documenting on how packagers will use Bodhi for
multi-builds updates in rawhide:
A 5.1 release is scheduled, likely some time next week, to address
some of the issues encountered and fixed in the 5.0 release.
Our team came across some test reliability issues last week & these
are impeding progress on the 83x patch.
Some more debugging/discussions around RCMs pushes that seem to be
either very slow or hanging but the team is looking into some
Some progress was also made on the 83x patch however and we managed to
fix one unreliable test.
Blocking issue was fixed (https://pagure.io/fedora-infrastructure/issue/8253)
jlanda hitting permission error in communishift
Benson Muite is now working on OIDC authentication
An article will be posted to Magazine instead - keep an eye out!
GDPR policies are still being looked into so stay tuned for updates
soon. This unfortunately takes some time given the legal perspective
The team is busy working on 8.1
Comps were produced and in git repo for next compose (pungi)
Transmodrify tool rewritten to match the mbs/rpm needs
Analyzing what RH hasn’t pushed and so that is needed
Builds started and are being working on for x86_64, ppc64le, aarch64
and armhfp architectures
Dealing with hardware issues on storage box , so opening tickets with
vendor and internal IT to play MITM and try to get this solved
Dealing with RCM having still issues to push to git.centos.org for
some identified packages (reproducible) so now waiting on Repospanner
maintainer to come with a fix and an ETA for new release that would
Trying to provision some EC2 instances and working with Fedora to get
proper access to be able to have proper AWS access for CentOS (also
Working on various PR for cbs-content-control and/or issues with mash
on https://cbs.centos.org (now resolved)
EPEL 8 modularity
EPEL8 module builds are working in staging & composes should be closed
There are now tags added to staging in koji
Bodhi configs have been updated
Pungi configs for epel8-playground are updated
Bug about zchunk update for EPEL-7 was fixed
Multiple small PRs were merged where people were being sent to Fedora
docs after F31 came out & below are all fixed:
Community Platform Engineering Team
Red Hat EMEA
You are kindly invited to the meeting:
Fedora Infrastructure on 2019-11-14 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 was contacted by someone working on openSUSE's Open Build System
(OBS). They are using download.fedoraproject.org and some layout change
concerning noarch breaks their workflow. The problem is, that the
redirect service of download.fedoraproject.org based on the mirrorlist
servers returns a 200 and 'error: invalid path'. See
So this problem is unrelated to the new mirrorlist implementation. The
old code did the same. Error message and a 200 return code.
I think changing the return code to 404 is the correct thing to do, but
I wanted to check if anybody sees any problems with this behaviour
change of the mirrorlist server.
Now that https://pagure.io/releng/pull-request/8940 got merged we can
migrate nagios from fedmsg to fedora-messaging.
The attached patches are for switching nagios to fedora-messaging,
please review and merge if they look sane to you.