devel November 2025

devel@lists.centos.org

5 participants
8 discussions

Discussion: Thoughts of new sig - CentOS Rollup
by Troy Dawson 11 Dec '25

11 Dec '25

I have heard several times from different people and SIGs that they would like a Rollup (Snapshot) of their SIG's stuff, along with the corresponding CentOS Stream and EPEL release. So, I'd like to start a discussion about the possibility of creating a SIG that would rollup all of the "stuff" (images, repos, packages, documentation, etc...) from all the CentOS SIGs, along with the the corresponding CentOS Stream and EPEL releases, once a quarter. We could put all of that in AWS space, and leave it there for a period of time. Some people I talked to said a year, some said for the remainder of the corresponding Stream life. There are several details that would need to be worked out, but I'm sending this email out to start the discussion about the feasibility and desire for such a SIG. Troy

2 3

[Infra] - Planned outage : cbs.centos.org (Nov 18th)
by Fabian Arrotin 19 Nov '25

19 Nov '25

Due to a (announced now) DC move, we'll have to migrate the existing CentOS CBS Koji build infrastructure (https://cbs.centos.org) to new DC and so new hosts Migration is scheduled for """"Tuesday November 18th, 8:00 am UTC time"""". You can convert to local time with $(date -d '2025-11-18 08:00 UTC') We don't have a full estimate about the needed time but we'll proceed like this : - disable all builders on actual CBS infra - wait for some remaining build tasks to finish (ideally you'd stop in advance for that day any automated workflow to not submit builds) - shutdown cbs kojihub in rdu2 - backup/import latest postgresql into new cbs kojihub in rdu3 - synchronize last time kojishare volume from rdu2 => rdu3 (last time it took ~70min) - verify service can start (still all kojid builders disabled) - reconfigure hub to add new aws/rdu3 build hosts - test a simple createrepo (koji regen-repo) task to ensure kojid machines can reach hub and nfs - test a new scratch build from git to test git + lookaside workflow - validate new signing host get notifications on message bus - opening up hub for new requests - builds should proceed as usual Worth knowing that we'll switch the base profile for the all the builders to match a 4:1 ratio (so 4GB RAM / core) and so on-prem (rdu3) and remote aws builders will all (as starting point) be 16 cores/64GB ram. The s390x builder will remain the same (as itself already remote and so not migrating, just attaching remotely to new hub) The biggest change will be for ppc64le architecture, as we'll be switching from IBM Power 9 to Power 10, but these new builders will also us the same 16cores/64GB ram profile Also worth knowing that it's the first (but biggest !) part of the migration. We expect all to work for the SIGs workflow, but some actual machines in RDU2 will then be physically migrated (second week of December, based on actual planning) and then be reinstalled/reconfigured by ansible and so also added to CBS pool and/or other CI needs (like adding back ppc64le as option for duffy.ci.centos.org consumers) The other (tested) infra change we'll use is a caching server that will speed up access to external repositories (like dl.fedoraproject.org for epel and kojihub.stream.centos.org for centos-buildroots for SIGs that opted in for that option, instead of just building against available and release content set on mirror.stream.centos.org) I'm working on preparing all that is needed but all the infra is deployed, and just need to be configured with Ansible and then we'll just orchestrate the main switch. We'll keep you informed about any change or status update on that day. Thanks for your understanding and patience. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 4

November Board Meeting Recap
by Shaun McCance 17 Nov '25

17 Nov '25

The recording of the November CentOS Board meeting is now available. Watch the recording: https://youtu.be/_HUqs-N2M2E Read the minutes: https://gitlab.com/CentOS/Board/tracker/-/blob/master/meetings/2025/2025-11… See this post on the blog: https://blog.centos.org/2025/11/centos-board-meeting-recap-november-2025/ The recording has timestamps so you can skip to the parts that interest you. Here are a few highlights of the meeting: * The Board discussed the AI policy draft, particularly in light of the recent Fedora AI policy. * We briefly talked about docs tooling and the needs of the Automotive docs team. * We talked about upcoming events, including CentOS Connect, the Distros Devroom at FOSDEM, SCaLE, and Flock to Fedora. -- Shaun

1 0

re-building Python on c9 - fails ?
by lejeczek 14 Nov '25

14 Nov '25

Hi guys. I'm trying to rpm rebuild Python with python3.9.spec from default repos. I've done only a few re/builds in my time and this is new to me - I've sroogled but have failed to get better grip of what's (not)happing here. ... 2 re-run tests: test_mmap test_os Total duration: 3 min 40 sec Tests result: FAILURE then FAILURE error: Bad exit status from /var/tmp/rpm-tmp.QX5emT (%check) RPM build errors: line 495: It's not recommended to have unversioned Obsoletes: Obsoletes: python3.9 Bad exit status from /var/tmp/rpm-tmp.QX5emT (%check) Finish: rpmbuild python3.9-3.9.23-2.el9.src.rpm Finish: build phase for python3.9-3.9.23-2.el9.src.rpm ERROR: Exception(/00-REPOs/dnf.repo/repo/el9/x86_64/packages/python3.9-3.9.23-2.el9.src.rpm) Config(centos-stream+epel-9-x86_64) 12 minutes 9 seconds INFO: Results and/or logs in: /00-REPOs/dnf.repo/repo/el9/x86_64/packages INFO: Cleaning up build root ('cleanup_on_failure=True') Start: clean chroot Finish: clean chroot ERROR: Command failed: Would this be .spec file or something not good with build evn? btw. Is there a doc perhaps, explaining "Obsoletes" with regards to rpm build? many thanks, L.

2 2

2025-11-12 CentOS Public Board Meeting
by Amy Marrich 11 Nov '25

11 Nov '25

Our next board meeting will take place at 20:00 UTC on Wednesday: `date -d "2025-11-12 20:00 UTC"` If you would like to attend please send me an email to amy(a)redhat.com ( please do not reply to @centos-devel or use another email address) and you will receive a link to a meeting room with a passcode, 1 hour before the meeting takes place. The agenda can be checked at (work in progress) : https://hackmd.io/jH2J9YdfT6yN1SAqDG6MSQ As a reminder we will enforce few rules : * Wait to be recognized by the Chair before speaking * Respect the Chair when told your time to speak is over - this will allow us to remain on agenda, and complete the meetings in the allotted time * In the event that there are Board-confidential topics, these will be put at the end of the meeting, in Executive Session, and guests will be asked to leave. We hope to minimize these items, but they do sometimes happen. The most common scenarios in which this may happen are personnel issues, or information that Red Hat wishes to share with the Board, but is not yet public. * Muting of participants, or, in extreme situations, ejection from the meeting, is at the sole discretion of the Chair. * Meetings will be recorded, and published to YouTube (possibly with edits/redaction, as approved by the Directors). Thus, by joining the meeting you consent to have your presence at the meeting, and anything you say during the meeting, made public. I hope some of you can join. thanks, *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy(a)redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz

1 0

[Infra] - Planned outage : srg.sigs.centos.org (Nov 4th)
by Fabian Arrotin 05 Nov '25

05 Nov '25

Due to a DC move, we'll have to migrate the existing CentOS SIGs lookaside server (aka https://src.sigs.centos.org but still answering on legacy name git.centos.org) to a new server. Migration is scheduled for """"Thursday November 6th, 8:00 am UTC time"""". You can convert to local time with $(date -d '2025-11-06 08:00 UTC') The expected "downtime" is estimated to ~10 minutes (current TTL in DNS) , time needed to : - synchronize lookaside content to new host (last rsync) - verify service and switch DNS to point to new host. Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 0

FOSDEM Distros Devroom CFP
by Shaun McCance 04 Nov '25

04 Nov '25

The Distributions Devroom is returning to FOSDEM for a full day of distribution-related content in Brussels on Sunday, February 1, 2026. The Distros Devroom organizers are happy to share that the call for proposals is now open, and will be accepting proposals until December 5. Read on to learn more about this devroom, what topics we want to see, and how you can submit. ## Important Dates * Now - Call for Participation opens * December 1 - Call for Participation ends * December 5 - Speakers notified * December 12 - Deadline for speakers to confirm * December 15 - Schedule published * February 1 - Distros Devroom at FOSDEM ## Call for Proposals Please submit your talk proposals using the FOSDEM CFP submission page: https://pretalx.fosdem.org/fosdem-2026/cfp Your submission must include the following information: * Proposal title * Session (chose Talk) * Track (choose Distributions from the drop-down menu) * Abstract (as you would like it to appear publicly, 100-250 words) By default, all talks are 25 minutes, incuding time for Q+A. Occasionally, we may provide longer time slots for deep dives that are broadly interesting. If you think your talk should be considered for a longer time slot, explain why in the Submission Notes. ## Themes We're interested in talks on a number of topics, including: * Technologies for package management, automated testing, and release deployment * Long term maintenance and backporting security updates * Evaluating upstream components for secure supply chains * Developments in image-based operating systems and container base images * Delivering multiple-architecture or architecture-agnostic software. * Building commmunity around distributions. * Emerging technologies in the Linux ecosystem. The audience for the Distributions Devroom is primarily contributors and developers of Linux distributions. We may accept a limited amount of content with a focus on end users, but most user-focused content better fits in other devrooms or events. We look forward to new and interesting submissions. ## About the Distributions Devroom Linux distributions are critical digital infrastructure in the 2020s. They remain an important fixture even as our expectations of how they work and support workloads has evolved over the decades. Linux distributions do important work in ensuring various versions of upstream software work well together and can co-exist. They have become the centerpiece of other important infrastructure projects like containers and container orchestration software. The Distributions Devroom provides a unique home for the convergence of several different Linux distribution communities to share ideas and start conversations that matter to all of us. Although there are several different distributions that have different approaches to software packaging, choice of desktop environments, and various use cases, the Distributions Devroom is a historic open forum that is unique to FOSDEM in making a space for all of our communities to share and learn from each other. The Distributions Devroom organizers can be reached at <distributions-devroom(a)lists.fosdem.org>. ## About FOSDEM FOSDEM is a free event for software developers to meet, share ideas and collaborate. Every year, thousands of developers of free and open source software from all over the world gather at the event in Brussels. FOSDEM hosts dozens of developer rooms, where community members run tracks on various topics.

1 0

[Infra] - Planned outage : lists.centos.org (Nov 4th)
by Fabian Arrotin 04 Nov '25

04 Nov '25

Due to a DC move, we'll have to migrate the existing CentOS mail server/mailing list server (aka https://lists.centos.org) to a new server. Migration is scheduled for """"Tuesday November 4th, 8:00 am UTC time"""". You can convert to local time with $(date -d '2025-11-04 08:00 UTC') The expected "downtime" is estimated to ~15 minutes , time needed to : - backup/restore last mysql dump - synchronize mailman3 archives (hyperkitty) - verify service and switch DNS to point to new host. Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel November 2025