Infra & RelEng Update – Week 46 2023

[lenkaseg (Lenka Segura)]

Originally published at: Infra & RelEng Update – Week 46 2023 – Fedora Community Blog

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contain updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.

We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

Week: 13 – 17 Nov 2023

Infrastructure & Release Engineering

Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
Planning board

Fedora Infra

• Fix ssh connection to compose-x86-01.stg.iad2.fedoraproject.org
• Publish rpmautospec-core to PyPI
• Fix IPA replica installation

CentOS Infra including CentOS CI

• Refresh our el9 deployment servers with updated 9.3 tree
• Rack new servers/equipment
• Fix: gitlab-runner failing with Permission denied

Release Engineering

• Add Onyx to scripts/update_ostree_refs.sh
• Add gtk2 and gtk3 support in multilib conf
• Update IoT signing keys
• F40: KDE: Drop X11 from the KDE Desktop Environment

CPE Initiatives

EPEL

Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).

Updates

• Added python-build to EPEL 9 for Ansible DevTools team
• Rebuilt nextcloud-client in EPEL 9 for RHEL 9.3 Qt update

ARC Investigations

The ARC (which is a subset of the CPE team) investigates possible initiatives that CPE might take on.

Updates

• Dist-Git decoupling & ecosystem mapping
  • Bodhi investigation documented
  • Pagure investigation documented
  • fedpkg investigation documented
  • monitor-gating investigation documented
  • You can follow your work here:
    • Hackmd.io document used for notes
    • Tickets for investigation

List of new releases of apps maintained by CPE

• Patch update of MD API from 3.1.3 to 3.1.4 on 2023-11-15
• Patch update of Bodhi from 2.1.1 to 2.1.2 on 2023-11-14

[decathorpe (Fabio Valentini)]

@lenkaseg

Dist-Git decoupling & ecosystem mapping

Thanks, that is an interesting read. Looking through those docs, it seems the investigation was done in a “forge-agnostic” way? I really appreciate that, given that there still appear to be roadblocks for using GitLab.

<opinion>
Speaking for myself - if we need to move away from pagure due to its maintenance status, I would really like us to move to another fully open source forge, like forgejo. It appears that Alma Linux is using Gitea as their dist-git backend, so using forgejo (a Gitea soft fork) should be possible, right?
</opinion>

[kevin (Kevin Fenzi)]

@lenkaseg

Dist-Git decoupling & ecosystem mapping

Thanks, that is an interesting read. Looking through those docs, it seems the investigation was done in a “forge-agnostic” way? I really appreciate that, given that there still appear to be roadblocks for using GitLab.

yeah, the idea was to at least identify our integration points and
possibly make them more agnostic to make moving to really anything
easier.

<opinion>
Speaking for myself - if we need to move away from pagure due to its maintenance status, I would really like us to move to another fully open source forge, like forgejo. It appears that Alma Linux is using Gitea as their dist-git backend, so using forgejo (a Gitea soft fork) should be possible, right?
</opinion>

Yeah, this is likely a discussion for early next year.

I personally find forgejo pretty interesting…