devel July 2023

devel@lists.centos.org

14 participants
19 discussions

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

[Feedback request] CentOS website theme readability
by Alain Reguera Delgado 17 Aug '24

17 Aug '24

Hi, The website theme is being updated to improve content responsiveness and readability, on both large and small screen devices. Your feedback would be very helpful to detect usability issues and consolidate a design that works well for you. Here is an example page you can use for testing: https://www.dev.centos.org/about/governance/sigs/#functional-sig-responsibi… Is the content of this page readable for you? If possible, provide feedback from both large and small screen devices. Thanks! -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

3 5

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

[REPORT] Quarterly Report - CentOS Automotive SIG
by Jeffrey Osier-Mixon 17 Aug '23

17 Aug '23

January 2023 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - chair _____________________________________ Membership update This SIG does not have a formal membership process. The mailing list currently has 106 subscribers representing at least 32 organizations, though not all subscribers use corporate emails and some are participating as individuals. _____________________________________ Releases in the most recent quarter (or most recent release, if none in that quarter) The Automotive SIG produces three types of artifacts: - AutoSD, a streaming distribution of CentOS designed for in-vehicle automotive use cases. - An Automotive SIG RPM repository that allows the community to expand the content of AutoSD or experiment with some of its parts. - Sample images, built using OSBuild, which provide examples of how to assemble production images based on AutoSD, customized for some hardware, including container images, based on CoreOS/ostree technologies. AutoSD, or Automotive Stream Distribution, is a streaming distribution for automotive in-vehicle software development based on CentOS Stream. It is transparently the upstream project for Red Hat's eventual in-vehicle OS product. AutoSD has been downloaded and used by many organizations who have commented or asked for help, so we know it is getting some traction though of course we don't have exact metrics on usage. In Q4 2022, we released a version of AutoSD compatible with the emerging SOAFEE specification. SOAFEE (https://soafee.io) is an initiative driven by Arm for the purpose of developing a reference specification for Arm-based software-defined vehicles (SDVs) consisting of an operating system, container orchestration strategy, and application layer. In addition, we introduced a very lightweight container runtime based on podman and systemd that does not include Kubernetes, as the latter represented a significant performance hit on all relevant hardware. We presented at the Arm Developer Summit in November on these topics. In the coming quarter, we plan to tighten up documentation, begin a process for accepting and supporting hardware enablement contributions, and continue to develop AutoSD toward the SOAFEE specification while also contributing to that specification within the SOAFEE community. _____________________________________ Health report and general activity narrative The SIG typically has 1 public meeting per month with 25-40 attendees, with visible participation from 7-10 separate organizations. We have largely given up on a separate office hours meeting due to attendance. This SIG is intended to be a community effort with contributions and shared benefits from all participants. All formal meetings are recorded and posted on this page: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings Several Red Hat employees made the initial contributions to the project as well as the infrastructure required to build and test it. We occupy a gitlab repository in the CentOS namespace building software regularly using CI, with build instructions provided on the documentation page at https://sigs.centos.org/automotive/ . Sample images are present and downloadable along with customization and build instructions. _____________________________________ Issues for the board to address, if any None, keep up the excellent work :) Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 1

Re: [CentOS-devel] [t_functional sig] Tests management with TMT
by Miroslav Vadkerti 25 Jul '23

25 Jul '23

Hi Carlos, On Tue, Jul 25, 2023 at 12:15 PM Frantisek Lachman <flachman(a)redhat.com> wrote: > > > ---------- Forwarded message --------- > From: Carlos Rodriguez-Fernandez <carlosrodrifernandez(a)gmail.com> > Date: Tue, Jul 25, 2023 at 4:53 AM > Subject: [CentOS-devel] [t_functional sig] Tests management with TMT > To: <centos-devel(a)centos.org> > > > Hi, > > Is there any interest or already a plan to convert the test management > of the t_functional tests to TMT (https://github.com/teemtee/tmt)? > Note that the conversion might not be even needed, tmt now serves well as a wrapper over various testing frameworks, many people use it like that. > I see that packit.dev and tmt is where fedora is trying to go instead of > zuul ci, > This might be a confusion, note that these systems are on different levels: * Packit is on the level of upstream project GitHub / GitLab contributions * Zuul CI for Fedora <https://fedora.softwarefactory-project.io/zuul/builds?job_name=rpm-tmt-test> and Zuul CI for CentOS Stream <https://centos.softwarefactory-project.io/zuul/t/centos/builds?job_name=rpm…> are on the level of dist-git contributions All these run tmt tests which can be defined basically in any git repository (remote or local). > and also I saw the email from the cloud sig about adopting > packit.dev. I was wondering how it will impact t_functional. > Can you point me to that email please? > I have been playing with it and seems like a good tool for the job. > Glad to hear that :) Best regards, /M > > Regards, > Carlos. > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > -- Miroslav Vadkerti :: Senior Principal QE :: Testing Farm / Linux QE IRC mvadkert #tft #tmt #osci :: Mobile +420 773 944 252 Remote Czech Republic :: Red Hat Czech s.r.o

2 1

[t_functional sig] Tests management with TMT
by Carlos Rodriguez-Fernandez 25 Jul '23

25 Jul '23

Hi, Is there any interest or already a plan to convert the test management of the t_functional tests to TMT (https://github.com/teemtee/tmt)? I see that packit.dev and tmt is where fedora is trying to go instead of zuul ci, and also I saw the email from the cloud sig about adopting packit.dev. I was wondering how it will impact t_functional. I have been playing with it and seems like a good tool for the job. Regards, Carlos.

1 0

9-stream kmods: btrfs missing for 5.14.0-340
by Anthony Alba 24 Jul '23

24 Jul '23

Hi all, A new bunch of kmods has landed for the c9s kernel release 5.14.0-340 but btrfs seems to be missing. Thanks Anthony Alba

2 1

CentOS Cloud SIG meeting minutes (2023-07-13)
by Joel Capitao 17 Jul '23

17 Jul '23

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2023-07-13) ====================================================== Meeting started by jcapitao[m] at 15:00:10 UTC. The full logs are available athttps://www.centos.org/minutes/2023/July/centos-meeting.2023-07-13-15.00.… . Meeting summary --------------- * roll call (jcapitao[m], 15:00:28) * OKD/SCOS (jcapitao[m], 15:05:46) * the build infra was moved from operate-first.cloud to massopen.cloud (jcapitao[m], 15:06:11) * ACTION: lorbus to send out email to centos-devel promoting the packit.dev RFE for CBS support (lorbus, 15:11:26) * LINK: https://copr.fedorainfracloud.org/coprs/g/OKD/okd/package/cri-o/ (amoralej, 15:22:48) Meeting ended at 15:30:32 UTC. Action Items ------------ * lorbus to send out email to centos-devel promoting the packit.dev RFE for CBS support Action Items, by person ----------------------- * lorbus * lorbus to send out email to centos-devel promoting the packit.dev RFE for CBS support * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * lorbus (28) * amoralej (23) * jcapitao[m] (22) * centguard (6) * karolinku12 (1) * spotz__ (1) * karolinku[m] (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Re: [CentOS-devel] Making the redhat selinux-policy repository publicly available
by Daan De Meyer 14 Jul '23

14 Jul '23

> To get just the latest repository content, steps described by Troy should work. Additionally, most of the upstream work is done in Fedora and anyway every new commit should go to Fedora first, RHEL content is mostly a subset of Fedora, there are very few differences. Yes, but the differences might be crucial so it'd be great if we could look at the repository containing the actual policy used in centos as well. Cheers, Daan On Wed, 12 Jul 2023 at 16:16, Zdenek Pytela <zpytela(a)redhat.com> wrote: > > > > On Tue, Jul 11, 2023 at 10:37 PM Troy Dawson <tdawson(a)redhat.com> wrote: >> >> On Tue, Jul 11, 2023 at 12:50 PM Neal Gompa <ngompa13(a)gmail.com> wrote: >>> >>> On Tue, Jul 11, 2023 at 9:31 AM Troy Dawson <tdawson(a)redhat.com> wrote: >>> > >>> > On Tue, Jul 11, 2023 at 4:28 AM Daan De Meyer <daan.j.demeyer(a)gmail.com> wrote: >>> >> >>> >> Hi, >>> >> >>> >> It seems that the selinux-policy rpm is built from >>> >> git@gitlab.cee.redhat.com:SELinux/selinux-policy.git which seems to be >>> >> a redhat internal repository. More specifically, if I try to checkout >>> >> the commit listed in the selinux-policy spec >>> >> (https://gitlab.com/redhat/centos-stream/rpms/selinux-policy/-/blob/c9s/seli…) >>> >> in the fedora-selinux repository cloned from github, I get an error >>> >> saying that the commit does not exist. It would be great if the >>> >> repository containing this commit was publicly available and open for >>> >> external contributors just like all the other packages in CentOS >>> >> Stream. Is it possible to make this happen? >>> > >>> > >>> > I'm not the selinux-policy maintainer, so I can't comment on where they work on the selinux-policy source code. >>> > >>> > But this is how I get the sources, if that is what you are ultimately looking for. >>> > >>> > centpkg clone selinux-policy >>> > cd selinux-policy >>> > centpkg sources >>> > or if you want to know where they really are >>> > centpkg -v sources >>> > This shows it to be coming from >>> > https://sources.stream.centos.org/sources/rpms/selinux-policy/selinux-polic… >>> > >>> > The sources information is found in the sources file >>> > https://gitlab.com/redhat/centos-stream/rpms/selinux-policy/-/blob/c9s/sour… >>> > >>> > I know this isn't exactly what you asked for, but I hope it still helps. >>> > >>> >>> I think the idea is that having the Git repository in a public >>> location would allow the CentOS Hyperscale SIG to contribute to the >>> SELinux policy in a meaningful way. >> >> >> Ah, ok. That makes sense. >> As I said, I'm not the maintainer so I don't know why it's where it is. So I'll step out of the conversation. > > > Hi, > > I am one of the selinux-policy maintainers. Currently, repository for Fedora is at github.com and RHEL sources are in an internal repo. We have already discussed moving centos stream sources to some of the public repositories, but it did not happen. Currently we are discussing it again, there are a few options how to do so. > > To get just the latest repository content, steps described by Troy should work. Additionally, most of the upstream work is done in Fedora and anyway every new commit should go to Fedora first, RHEL content is mostly a subset of Fedora, there are very few differences. > > -- > > Zdenek Pytela > Security SELinux team > _______________________________________________ > selinux mailing list -- selinux(a)lists.fedoraproject.org > To unsubscribe send an email to selinux-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/selinux@lists.fedoraproject.o… > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

1 0

Upcoming CentOS Connect at Fedora Flock
by Amy Marrich 12 Jul '23

12 Jul '23

Hi everyone, For those who are not aware, the next CentOS Connect will be held in conjunction with Fedora Flock which is being held August 2-4[0] in Cork, IE. While the CFP is closed, there is still time to register[1] to attend and the Schedule[2] is really coming together with a wide range of topics not just during Connect but the tracks as well. Amy 0 - https://flocktofedora.org 1 - https://www.eventbrite.co.uk/e/flock-2023-tickets-671047008667 2 - https://flock2023.sched.com/ *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 <https://www.redhat.com/>

1 0

[Storage SIG] Problems installing ceph + qemu-kvm in C9S
by Alfredo Moralejo Alonso 12 Jul '23

12 Jul '23

Hi, After the update of liburing in centos stream 9, we are having issues to install ceph and qemu-kvm together: # dnf install ceph qemu-kvm Last metadata expiration check: 0:01:00 ago on Mon Jul 10 14:02:55 2023. Error: Problem: cannot install both liburing-2.3-2.el9.x86_64 and liburing-0.7-7.el9.x86_64 - package qemu-kvm-core-17:8.0.0-6.el9.x86_64 requires liburing.so.2()(64bit), but none of the providers can be installed - package qemu-kvm-core-17:8.0.0-6.el9.x86_64 requires liburing.so.2(LIBURING_2.0)(64bit), but none of the providers can be installed - package ceph-osd-2:17.2.3-2.el9s.x86_64 requires liburing.so.1()(64bit), but none of the providers can be installed - package ceph-osd-2:17.2.3-2.el9s.x86_64 requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed - package qemu-kvm-17:8.0.0-6.el9.x86_64 requires qemu-kvm-core = 17:8.0.0-6.el9, but none of the providers can be installed - package ceph-2:17.2.3-2.el9s.x86_64 requires ceph-osd = 2:17.2.3-2.el9s, but none of the providers can be installed - cannot install the best candidate for the job Any help from storage sig will be appreciated. Best regards, Alfredo

4 4

Making the redhat selinux-policy repository publicly available
by Daan De Meyer 11 Jul '23

11 Jul '23

Hi, It seems that the selinux-policy rpm is built from git@gitlab.cee.redhat.com:SELinux/selinux-policy.git which seems to be a redhat internal repository. More specifically, if I try to checkout the commit listed in the selinux-policy spec (https://gitlab.com/redhat/centos-stream/rpms/selinux-policy/-/blob/c9s/seli…) in the fedora-selinux repository cloned from github, I get an error saying that the commit does not exist. It would be great if the repository containing this commit was publicly available and open for external contributors just like all the other packages in CentOS Stream. Is it possible to make this happen? Cheers, Daan De Meyer

3 3

2023-07-12 - CentOS Public Board Meeting
by Thomas Oulevey 10 Jul '23

10 Jul '23

Hi Everyone, Our next board meeting will take place at 20:00 UTC on Wednesday: `date -d "2023-07-12 20:00 UTC"` If you would like to attend please send me an email to alphacc(a)centosproject.org ( please do not reply to @centos-devel or use another email address) and you will receive a link to a Zoom meeting room with a passcode, 1 hour before the meeting takes place. The agenda can be checked at (work in progress) : https://hackmd.io/@centosboard/HyP-UuFt2 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. Sorry for the late announcement. thanks, -- Thomas 'alphacc' Oulevey CentOS Board of Directors Secretary alphacc(a)centosproject.org

1 0

Help with reproducing tests locally
by Carlos Rodriguez-Fernandez 08 Jul '23

08 Jul '23

Hi All, I've been trying to reproduce the centos tests locally. Thank to Aleksandra and arrfab for the help on IRC to understand the whole process conceptually. I successfully ran https://github.com/CentOS/sig-core-t_functional on a clean centos stream 9 vm. The tests passed. I'm running into issues trying to run individual playbooks against a clean centos stream 9 vm from the zuul-jobs and jobs repositories from here: https://gitlab.com/redhat/centos-stream/ci-cd/zuul The errors I find are mainly related to dependencies, e.g., missing users, or packages, which makes me think there are steps I need to do before. Is there any documentation for contributors about the zuul CI tests, to be able to test individual playbooks locally? If there is none, I could contribute with some in a Readme.md, but I would still need some basic guidance to get at least some of them working locally. Any help is appreciated. Regards, Carlos.

1 1

[ISA SIG] Meeting notes 2023-07-07
by Florian Weimer 07 Jul '23

07 Jul '23

We met for the first time today. Florian briefly summarized the status of the CentOS 9 Stream rebuilds with x86-64-v2 and x86-64-v3. For details, please see: [CentOS-devel] ISA SIG rebuild status <https://lists.centos.org/pipermail/centos-devel/2023-June/143007.html> Since then, Troy has added consumption documentation describing how to consume the builds: Convert CentOS Stream 9 to ISA <https://sigs.centos.org/isa/consuming/centosstream9/#convert-centos-stream-…> Currently, there are no plans to keep the package set up-to-date with regards to CentOS 9 Stream. Troy plans to create centos-release-isa package which, upon installation, creates the unusual repository configuration. This will be an explicit download, not part of CentOS Extras, out of concern that people might try to install it accidentally otherwise. Ali raised the matter of zlib-ng (see the previous mailing list thread). Florian thinks that zlib-ng in compat mode is something to explore. This work should happen in Fedora first, targeting Fedora 40. Florian to send email to relevant parties. Troy and Florian are going to explore creating two container images for each rebuild variant, so that people have a more familiar starting point for some quick experiments. We plan to reconvene on July 21st, at 16:00 UTC (date and time still tentative; it's the alternate slot for the bi-weekly Fedora ELN meeting). Please drop me a line if you want to be added to the meeting invitation. Update of the CentOS calendar is still pending: <https://github.com/CentOS/Calendar/pull/62> (We will likely keep using Google Meet instead of IRC, though.) Thanks, Florian

1 0

[Storage-SIG] cephadm package is old
by Luis Domingues 07 Jul '23

07 Jul '23

Hi. During an installation, I saw that almost all ceph packages for ceph pacific are in the last version, v16.2.13 except for cephadm. The last version is v16.2.7. Is any reason for that? Or is it just a mistake? Thanks Luis Domingues Proton AG

2 1

Build for main CentOS Stream repos with subpackages in a SIG repo
by Sandro Bonazzola 04 Jul '23

04 Jul '23

Hi, is it possible to have a build from https://kojihub.stream.centos.org/koji/ having subpackages that are not going to be shipped in main CentOS Stream repos being somehow filtered to ship those subpackages into a SIG repo? I'm asking specifically about qemu-kvm sub packages we'd like to have in CentOS AutoSD SIG but that are not going to be shipped in main CentOS Stream repos as not relevant/supported in RHEL (qemu-kvm-ui-dbus, BZ# *2207940* <https://bugzilla.redhat.com/show_bug.cgi?id=2207940>). I would like to avoid having to rebuild the same qemu-kvm build within the SIG each time a new release lands in CentOS Stream just to get a subpackage. Is this possible? Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1

t_functional tests :: github checks broken, and the fix.
by Carlos Rodriguez-Fernandez 03 Jul '23

03 Jul '23

Hi Fabian Arrotin, I submitted a PR with a set of tests for libbpf-tools: https://github.com/CentOS/sig-core-t_functional/pull/88 The PR is failing because the python package duffy does not work with pydantic >= 2.0. I provided a commit in my PR that fixes that issue by pinpointing the version to the latest pydantic 1.x version (1.10.10 from 2023-06-30). That commit may need to be cherry picked first to then see if my PR passes the checks. Thank you, Carlos.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel July 2023