devel

devel@lists.centos.org

4 participants
4696 discussions

Community Hardware Pain Points
by Amy Marrich 19 Jun '26

19 Jun '26

At the June CentOS Board meeting, we were asked about pain points with hardware in the community to see what the Community Linux Engineering team might be able to assist with. The board came up with a HSM for secureboot and RISC-V hardware, but we want to know - what does the community as a whole think is a hardware pain point we can work on resolving? Amy *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

3 6

Migrating from pagure.io to gitlab.com/centos/ - any hints
by Troy Dawson 04 Jun '26

04 Jun '26

I know there are at least a few CentOS SIG's that have already migrated their SIG from pagure.io to gitlab. Does anyone have any helpful tips or scripts? I'm mainly concerned about bringing issues over. Troy

2 2

Fwd: Reminder about the sunset of pagure.io
by Troy Dawson 29 May '26

29 May '26

I am forwarding this to centos-devel just incase there are SIG's that aren't on Fedora's devel list. There are still one or two CentOS SIG's that are using pagure.io. If your SIG is one of them, it's time to move. ---------- Forwarded message --------- From: Vít Smolík via devel-announce <devel-announce(a)lists.fedoraproject.org> Date: Fri, May 29, 2026 at 3:46 AM Subject: Reminder about the sunset of pagure.io To: <devel-announce(a)lists.fedoraproject.org> Cc: Vít Smolík <me(a)smoliicek.cz> Hello everyone, we aim to decommision our old forge pagure.io around the Flock conference. We encourage you to migrate all your repositories from Pagure to our new forge[1] or to any other Git hosting service. If you have any questions, you can contact us on Matrix[2] or open a ticket with the Forge team [3]. Discussion and feedback can be held in the Discourse topic[4]. New organisation requests can be filed on the Forge ticket tracker[3] On behalf of the Fedora Infrastructure Team Smolík Vít [1] https://forge.fedoraproject.org [2] https://matrix.to/#/#fedora-forgejo:fedoraproject.org [3] https://forge.fedoraproject.org/forge/forge [4] https://discussion.fedoraproject.org/t/decommissioning-of-pagure-io-anticip…

1 0

python3-pyOpenSSL-25.0.0-1.el10_1.noarch
by listy 29 May '26

29 May '26

Hi guys. Anybody see this/similar?: -> $ dnf update CentOS-10-stream - Ceph Tentacle 25 kB/s | 16 kB 00:00 CentOS Stream 10 - NFV OpenvSwitch 28 kB/s | 16 kB 00:00 MooseFS 10 - x86_64 24 kB/s | 3.0 kB 00:00 Copr repo for openvpn3 owned by dsommers 828 B/s | 1.5 kB 00:01 Mine for Centos 10 326 kB/s | 3.0 kB 00:00 ookla_speedtest-cli 1.9 kB/s | 1.8 kB 00:00 ookla_speedtest-cli-source 1.1 kB/s | 951 B 00:00 Error: Problem: package python3-pyOpenSSL-25.0.0-1.el10_1.noarch from @System requires (python3.12dist(cryptography) < 45~~ with python3.12dist(cryptography) >= 41.0.5), but none of the providers can be installed - cannot install both python3-cryptography-48.0.0-3.el10.x86_64 from baseos and python3-cryptography-43.0.0-4.el10.x86_64 from @System - cannot install both python3-cryptography-48.0.0-3.el10.x86_64 from baseos and python3-cryptography-41.0.7-2.el10.x86_64 from baseos - cannot install both python3-cryptography-48.0.0-3.el10.x86_64 from baseos and python3-cryptography-43.0.0-2.el10.x86_64 from baseos - cannot install both python3-cryptography-48.0.0-3.el10.x86_64 from baseos and python3-cryptography-43.0.0-3.el10.x86_64 from baseos - cannot install both python3-cryptography-48.0.0-3.el10.x86_64 from baseos and python3-cryptography-43.0.0-4.el10.x86_64 from baseos - cannot install the best update candidate for package python3-pyOpenSSL-25.0.0-1.el10_1.noarch - cannot install the best update candidate for package python3-cryptography-43.0.0-4.el10.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

3 2

CentOS Automotive SIG moving to chat
by Jeffrey Osier-Mixon 27 May '26

27 May '26

Hi folks - we are moving the CentOS Automotive SIG meeting to Matrix chat going forward. Currently it will be at the same time - first Wednesdays of each month at 1400 UTC = 10:00am EDT, 16:00 CEST. The difference is that instead of a call, the meeting will be held on our Matrix channel at https://app.element.io/?updated=1.11.3#/room/#centos-automotive-sig:fedorap… I'll change the meeting invite today. If you have any trouble reaching the channel or need any help, please reach out to myself or Leo. best, Jeffrey "Jefro" Osier-Mixon | josiermi(a)redhat.com Distinguished Community Architect Automotive, Edge, & Hardware Enablement Communities Red Hat Open Source & AI Program Office Book a meeting: https://calendar.app.google/sMBa7Xe8CLSEUdGV9

3 7

2026-05-20 CentOS Public Board Meeting - moved from 05-13
by Amy Marrich 17 May '26

17 May '26

Our next board meeting will take place at 20:00 UTC on Wednesday: `date -d "2026-05-20 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/ZnBYJIdnRYSLJFWZIh6kmw 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

cracks c10 with 6.12.0-225.el10.x86_64
by listy 13 May '26

13 May '26

https://github.com/V4bel/dirtyfrag

2 1

CentOS Stream RPM workflows migrating to Konflux - early feedback welcome
by Sean Ryan 11 May '26

11 May '26

Hi, As many of you are aware, we are migrating CentOS Stream RPM workflows to Konflux and we'd like some early community feedback. For those unfamiliar, Konflux is an open source, cloud-native build system for producing trusted software artefacts - https://konflux-ci.dev/. In our case, it produces the RPM builds that then land in Koji. You can learn more about it and some of the other changes in the past year from the following talk: CentOS Connect talk: https://www.youtube.com/watch?v=1yhTvL_rk-I - This talk by Troy and me covers what changed in the CentOS Stream pipeline over the past year, including additional Konflux-related updates and direction. Updated CentOS Stream docs: https://docs.centos.org/centos-stream-docs/build/ Relevant repos related to Konflux and our pipelines: https://gitlab.com/redhat/centos-stream/rpms/osci-internal-test-package - test RPM package used to validate CentOS Stream/Konflux build flow safely. https://gitlab.com/redhat/centos-stream/konflux-tests/rpmbuild-pipeline - CentOS Stream Konflux RPM pipeline test repo used for pipeline integration and iteration. We've completed the following test build using Konflux: https://kojihub.stream.centos.org/koji/buildinfo?buildID=110177. We'd appreciate you reviewing the build logs and letting us know if you spot any issues or concerns with this new build system. One important thing to note is Koji is not going away; Konflux is about how we produce builds upstream of Koji, and the aim is for the resulting packages to behave the same as they do today. Thanks, Sean

3 7

Re: CentOS Stream RPM workflows migrating to Konflux - early feedback welcome
by Sean Ryan 08 May '26

08 May '26

Hey Alan, Honestly I'm not too sure what way it will work. I will talk to the team about this. I believe Troy or Adam might be able to answer better on this one :D Sean Ryan Software Engineer seryan(a)redhat.com On Fri, 8 May 2026 at 10:43, Alan Pevec <apevec(a)redhat.com> wrote: > Hi Sean, > > As many of you are aware, we are migrating CentOS Stream RPM workflows to >> Konflux and we'd like some early community feedback. >> > > thanks for the update. Will the CentOS SIG Koji > https://cbs.centos.org/koji/ build in that or separate Konflux instance > and will it be also for container and disk images? > > Cheers, > Alan >

3 2

PR pending review on https://gitlab.com/CentOS/promo/centos.org
by Sandro Bonazzola 20 Apr '26

20 Apr '26

Hi, I have a couple of PRs on https://gitlab.com/CentOS/promo/centos.org which are waiting for a review since January. I see there was some recent activity there, so it's not an abandoned repository. Can you please point me to someone who can handle the review there? Thanks, -- Sandro Bonazzola MANAGER, ENGINEERING Red Hat In-Vehicle Operating System Red Hat <https://www.redhat.com/> <https://www.redhat.com/> <https://redhat.com/options> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel