I have a need for Python 3.5+ in EPEL7 (newest versions of Mailman 3
require it), so I tried rebuilding the Python 3.6 RPM as a
parallel-installable package by taking advantage of our %python3_other_*
macros. There's a lot of packages that need to be built in the right order
to get to a full Python 3.6 build, and even much more packages that need
changes to use those macros.
I finally got to complete the build and its dependencies, and I uploaded
the packages here:
In that directory there's also a "build-order.txt" file that lists which
packages should be rebuild, in which order, and with which options.
I understand I may not be alone in needing a more recent Python than 3.4 in
EPEL, that's why I post this message. I have also posted it to epel-devel:
What do you think? Do we want to test and "adopt" these packages with the
infra tag soonish, or wait for them to land in EPEL7 proper (but I don't
know if or when that'll happen).
I am Alex, and I want to start contributing to the Fedora Project.
My strongest skills are related to system administration. I worked, and work with Red Hat and SUSE family operating systems. I have working experience with VMware ESXI and different HP enterprise products (switches, servers, and storage systems). I am also currently finishing the CCNA certification. Next year, I'm planning to take the RHCSA and RHCE.
As a developer, I have written Bash and Python scripts. In my free time I also develop in C#.
I've been working in this field for 3 years now. My current position is of Devops engineer at TSS-Yonder.
As learning opportunities go, I would like to learn Ansible. I am also up for any challenges.
My IRC handle is: aso
For Fedora Atomic we release content every two weeks. A lot of ducks
have to be in a row in order to do this and often times behind the
scenes work is time sensitive. I really need access to releng/infra
so that I can be more efficient in doing this. I'd like to be able to:
- restart failed disk image build in koji
- re-kick off daily runs if they fail for some reason (make a .1 of a daily run)
- merge pull requests for other team members after I review them
- perform two week atomic releases
- I realize this one is hard because of signing keys but seriously
would be nice to be able to do this one myself
- If signing keys are a problem then we should just automate the
signing of the checksums for the atomic runs so that the
checksums are already signed by the time we do the release.
- push access to infra repo
- I often get patches reviewed on the list and then no one merges
the patches for me because they assume I have access and that I'm
going to do it myself. Then I bug someone to merge it for me,
then they forget to run the ansible playbook that is needed to
apply the change. I probably have to ping/wait 5+ times for every
change I need.
- manipulate ostree repos
- occasionally we have to reset refs, sync content from one repo
to another or otherwise manipulate the repo. Waiting on someone
to do this for me every time is quite painful. I do want people
to review changes that I propose but waiting more than 2 days is
not something I want to have to do.
- investigate failures by having access to infrastructure and logs
- fedimg fails often and I have to wait someone to investigate every time
- koji builders can sometimes have random failures. Being able to
investigate myself would be useful.
I have read over the following docs:
I know of the SOPs and have contributed to at least one of them:
I have helped debug a lot of issues with composes and general infra
inconsistencies over the past year. I have spent much time in the releng
/admin channels and have even helped others who are new to the channel.
I have attended releng/infra meetings somewhat regularly over the past
I am not asking for permissions so that I can willy nilly do what I please.
I'd try to get proposed changes reviewed and announce any actions I performed
on list. I just want to add a little more sanity to my day-to-day.
I have an outstanding ticket open for adding myself to the releng group:
Not sure if there is an equivalent process for adding people to Infra.
I can't remember if I ever sent one of these in the past so I'm going to send it again.
Hello everyone! My name is Dusty Mabe and I help manage/release Fedora Atomic Host on
a bi-weekly cadence. You've probably seen patches/FBRs/issues from me on the lists/issue
trackers. I'm continuously learning more about Infra and contributing to help us prepare
for and manage changes for Atomic Host users. Before working on Fedora and on Atomic Host
I was a consultant for a few years in NYC and before that I worked on the linux platform
for a Telecommunications company.
If you see me in IRC say hey!
P.S If you haven't tried out Fedora Atomic Host you should give it a go! To learn more you
can run through the lab here: https://dustymabe.com/2017/08/29/atomic-host-101-lab-part-0-preparation/