devel

devel@lists.centos.org

3 participants
4613 discussions

How to compile modular SRPMs for CentOS 8?
by Nico Kadel-Garcia 15 Apr '22

15 Apr '22

I admit to disliking "modularity" for RPMs, especially because there are various modularity RPMs I'd like to compile for python 3.9 compatibility. ansible-core requires at least python 3.8, but there are a stack of dependencies for ansible-core which have never been provided for python 3.9, such as python39-sphinx and python39-pytest.. Can anyone offer me suggestions or guidance on how to build those? The SRPMs for python3-pytest and others seem to support modularity, but I'd like to use "mock" locally to test them out.

6 11

Kernel topics at the 13-Apr CentOS Stream office Hours
by Brian Stinson 14 Apr '22

14 Apr '22

Hi Folks, For this month's office hours we're going to have some folks from the Kernel team at Red Hat to chat about kernel maintainer workflows, contributing to the kernel, and cover questions you may have about using or building against the kernel in your SIG. Office Hours are on Wednesday, 13-Apr at 17UTC https://centos.org/community/calendar/#centos-stream-office-hours-meetopens… See you there! --Brian

3 2

[REPORT] Automotive SIG
by Jeffrey Osier-Mixon 13 Apr '22

13 Apr '22

January 2022 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - acting chair _____________________________________ Membership update This SIG does not have a formal membership process. The mailing list currently has 89 subscribers representing at least 12 companies, 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 SIG now provides a new distribution: Automotive Stream Distribution (AutoSD), a CentOS Stream derivative designed specifically around the needs of an automotive OS, and transparently the upstream project for Red Hat's eventual in-vehicle OS product. AutoSD has been downloaded and used by several 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. _____________________________________ Health report and general activity narrative. The SIG has had two public meetings per month, one formal and one informal "office hours", each with 25-40 attendees, with visible participation from 7-10 separate organizations. This SIG is intended to be a community effort with contributions and shared benefits from all participants. Several Red Hat employees made the first contributions to the project as well as the infrastructure required to build and test it. We now occupy a gitlab repository building software regularly using CI, with build instructions provided. Sample images are present and downloadable along with customization and build instructions. This is a high-level summary of current activity: - The work is migrating to a CentOS namespace within GitLab in order to cement our intention as a community project: https://gitlab.com/centos/automotive - CI/CD infrastructure is in place - Downloadable images are available: https://autosd.sig.centos.org/ - Documentation has been greatly expanded with both community and corporate contributions: https://sigs.centos.org/automotive/ - Documentation now includes detailed contribution guidelines: https://sigs.centos.org/automotive/contributing/contributing-to-auto-sig-re… - Ongoing discussions within the meetings have centered around supported hardware and expectations for documentation - A new meetings page contains recordings of all meetings: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings - Synchronous communications have moved from IRC to Matrix thanks to some help from Fedora: https://app.element.io/#/room/#centos-automotive-sig:fedoraproject.org _____________________________________ 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 0

Please update images on VagrantCloud
by Mike DePaulo 08 Apr '22

08 Apr '22

Hi, Could you please update/add the images on VagrantCloud? Your project has already built and uploaded the images, but to cloud.centos.org rather than VagrantCloud. Vagrant has an issue if we try to use cloud.centos.org manual URLs instead of VagrantCloud. VagrantCloud (https://app.vagrantup.com/centos) has: - 8 Stream from 2021-02-10, but the latest manual URL image is 2022-01-25 - 8 from 2020-12-04, but the latest manual URL image is 2021-06-03 - 9 Stream isn't on VagrantCloud at all, but the latest manual URL image is 2022-03-30 The latest images available via for manual URLs: - https://cloud.centos.org/centos/8-stream/x86_64/images/ - https://cloud.centos.org/centos/8/x86_64/images/ - https://cloud.centos.org/centos/9-stream/x86_64/images/ - Mike -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat <https://www.redhat.com/> IM: mikedep333 GPG: 51745404 <https://www.redhat.com/>

1 0

[Openssl]incorrect CVE mentioned in openssl changelog
by Akshar Kanak 08 Apr '22

08 Apr '22

Dear team in latest openssl openssl-1.0.2k-25.el7_9.x86_64 , looks like there is an issue with change logs . rpm -qi --changelog openssl-1.0.2k-25.el7_9.x86_64 shows me " * Wed Mar 23 2022 Dmitry Belyavskiy <dbelyavs(a)redhat.com> - 1:1.0.2k-25 - Fixes CVE-2022-2078 Infinite loop in BN_mod_sqrt() reachable when parsing certificates - Related: rhbz#2067160 " The CVE number should be CVE-2022-0778 . Right ? reference : https://bugzilla.redhat.com/show_bug.cgi?id=2062202 Thanks and regards Akshar

2 1

CPE Weekly Update – Week of April 4th – 8th
by Michal Konecny 08 Apr '22

08 Apr '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/) If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-4th-8th/ # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative ----------------------- 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.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I&R-06-04-2022.pdf Update ------ ### Fedora Infra * Started F36 final freeze * Completed mass update/reboot last week before freeze * Hit fun koji bug that made it write our signed with mode 600 so it didn’t sync. Found and fixed all files and patched koji. * Had issue with s390x z/vm instances, but they are now back online (many thanks dhorak!) * Internal mail MX changed, blocking emails from fedoraproject.org -> redhat.com. Updated to new one and slowly caught up. * Completed ansible upgrade. Only thing left to fix is fedora-messaging callback. ### CentOS Infra including CentOS CI * Issues with Jenkins openshift sync plugins * Duffy onboarding with Nils and Pedro * Bussiness as usual, mirror tickets and koji tag requests .. ### Release Engineering * F36 releng final freeze * Retirement of FTI (Fails To Install) packages in F36 * Lots of stalled epel package requests * F37 changes are landing in our tracker ## CentOS Stream Goal of this Initiative ----------------------- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates ------- * Planning completed yesterday, focusing on: * 8 + 9 workflow parity * Build imports from c8s koji to c9s koji * Deploying sync2gitlab service * CVE checker service deployment * Testing making github actions running in test suite ## CentOS Duffy CI Goal of this Initiative ----------------------- Duffy is a system within CentOS CI Infra which allows tenants to provision and access bare metal resources of multiple architectures for the purposes of CI testing. We need to add the ability to checkout VMs in CentOS CI in Duffy. We have OpenNebula hypervisor available, and have started developing playbooks which can be used to create VMs using the OpenNebula API, but due to the current state of how Duffy is deployed, we are blocked with new dev work to add the VM checkout functionality. Updates ------- * Tests and fixes for cicoclient * Deployment preparation with Fabian, Pedro and Mark * Work on the Ansible role for Duffy * Meetings, meetings(, meetings!) ## Bodhi Goal of this Initiative ----------------------- This initiative is to separate Bodhi into multiple sub packages, fix integration and unit tests in CI, fix dependency management and automate part of the release process. Read ARC team findings in detail at: https://fedora-arc.readthedocs.io/en/latest/bodhi/index.html Updates ------- * Bodhi 6.0 will be deployed to production a couple of weeks after the Fedora release * E-mail about what’s new in Bodhi 6.0 sent to devel-announce * Wrapping up dependency management ## EPEL Goal of this initiative ----------------------- 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). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more. Updates ------- * EPEL9 up to 2247 source packages (increase of 33 from last week) * Rebuilt hwinfo epel8 package to be compatible with unannounced libx86emu soname bump * qt6 on its way to epel9 testing, which will allow more applications * Other notable new epel9 packages: * uwsgi * akmods * Notable mailing list discussions: * [Slowing down the stalled request process](https://lists.fedoraproject.org/archives/list/epel-devel@lists.fed… * [Dependency policy for packages in less common RHEL channels (HighAvailability, ResilientStorage, etc.)](https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedor…) * [EPEL8 packages needing care and feeding](https://lists.fedoraproject.org/archives/list/epel-devel@lists.fed… Kindest regards, CPE Team

1 0

Experimentation with the centos namespace on gitlab
by Brian Stinson 07 Apr '22

07 Apr '22

Hi Folks! We had a thread a few weeks ago about the usage of the “centos” namespace on gitlab: https://lists.centos.org/pipermail/centos-devel/2022-February/120216.html The authentication angle is progressing up to the point that we would like to open up the opportunity for a couple of SIGs to onboard with gitlab and help us round the edges. The idea being to open this up to all the SIGs interested in a few weeks once we have clearer documentations and guidelines around the usage of GitLab. We are currently working on that set of best-practices that SIGs which would like to use the centos namespace on gitlab will need to agree and follow. If you are interested, please let us know (just not everyone at once!) :) Thanks, Brian

6 5

Re: [CentOS-devel] [CentOS] ansible upgrade
by Leon Fauster 06 Apr '22

06 Apr '22

Am 23.02.22 um 13:47 schrieb Fabian Arrotin: > On 22/02/2022 22:37, Leon Fauster via CentOS wrote: >> Am 21.02.22 um 16:24 schrieb Fabian Arrotin: >>> On 21/02/2022 15:49, Leon Fauster via CentOS wrote: >>>> Hey all, back from vacation and seeing ansible 2.12 in the repos now. >>>> Anything to be aware of when upgrading from 2.9 to 2.12 in CS8? >>>> >>> >>> You'd be lucky if it works directly , as there were some semantic >>> changes in ansible, so you'll probably have to review all the >>> changes, and if ansible-core just has the modules (it's a stripped >>> down version of ansible, as you're supposed to download the >>> collections yourself) , and use FQCN (Fully Qualified Collection >>> Names) for modules ... >>> >>> FWIW, CentOS Infra still on ansible 2.9.27 from our own configuration >>> management SIG and ansible-core excluded in yum/dnf to ensure that >>> our automation still runs fine (until we have time to test/convert >>> all our roles/tasks/playbooks to run on ansible 5 - aka ansible-core >>> 2.12.x) >>> >> >> Thanks Fabian for the insights. I was planning such tests for May but >> that seems to be to late now. >> >> I remember that someone wanted to provide a meta package that pull >> additional ansible collections to give a similar experience like 2.9? >> Maybe more an EPEL question ... >> >> -- >> Leon > > There is indeed a an effort to have an ansible meta-package that would > pull both ansible-core and would contain collections (see > https://fedoraproject.org/wiki/Changes/Ansible5) > > I already had a look myself to see how to rebuild/provide it through > configmanagement SIG eventually, as we now have ansible-core availble > Some packages for ansible 5.x are already built on > koji.fedoraproject.org (see > https://koji.fedoraproject.org/koji/packageinfo?packageID=13842) but not > yet available for epel8, due to lack of ansible-core in RHEL 8 (for now, > but coming as it's in 8-stream, so in advance) > > Other introduced problem with ansible-core is the dep on python 3.8, > meaning that while we had ara (Ansible Records Ansible dashboard) > available in configmanagement SIG, it needs to be using same python > interpreter version for the callback, and previous one was built > against/for python 3.6 (like ansible 2.9.x) , so quite some changes ... > Moved this from #centos to #centos-devel: I am using an "ansible community package" (5.5.0) for testing internally now and noticed following behaviour: "yum update" obsoletes "ansible-2.9.27-1.el8.noarch" and installs ansible-core-2.12.2-2.el8.x86_64. A second "yum update" updates to ansible-core-2.12.3-1.el8.x86_64. We have the "ansible community package" as "ansible" in the repos. When doing a "yum install ansible" then dnf downgrades ansible-core to 2.12.2-2.el8. That is caused by the "Obsoletes: ansible" statement in that version but it is changed now to a "Conflicts: ansible < 2.10.0" in the newer version of ansible-core "2.12.3-1.el8.x86_64". IMO - the cs8 compose should remove the intermediate package ansible-core-2.12.2-2.el8.x86_64 to allow installing newer "ansible community package" rpms ... if it comes from the internal or in the future from the EPEL repo is irrelevant. test # rpm -q ansible-core ansible-core-2.12.3-1.el8.x86_64 test # yum install ansible Last metadata expiration check: 0:27:35 ago on Mon Apr 4 16:54:41 2022. Dependencies resolved. ================================================================================================================== Package Architecture Version Repository Size ================================================================================================================== Downgrading: ansible-core x86_64 2.12.2-2.el8 appstream 2.4 M Transaction Summary ================================================================================================================== Downgrade 1 Package Total download size: 2.4 M Is this ok [y/N]: ^COperation aborted. test # yum --exclude ansible-core-2.12.2-2.el8.x86_64 install ansible Last metadata expiration check: 0:27:49 ago on Mon Apr 4 16:54:41 2022. Dependencies resolved. ================================================================================================================== Package Architecture Version Repository Size ================================================================================================================== Installing: ansible noarch 5.5.0-1.el8 is-ws-tools 42 M Transaction Summary ================================================================================================================== Install 1 Package Total download size: 42 M Installed size: 305 M Is this ok [y/N]: Operation aborted. -- Leon

2 1

CentOS Hyperscale SIG Quarterly Report for 2022Q1
by Davide Cavalca 05 Apr '22

05 Apr '22

Hello, I've published our quarterly update for the Hyperscale SIG activities on the CentOS Blog: https://blog.centos.org/2022/04/centos-hyperscale-sig-quarterly-report-for-… Cheers Davide

3 2

9 - ? - all *release* packages
by lejeczek 05 Apr '22

05 Apr '22

Hi guys Why are *release* packages are still absent in 9? We (admins/users) read docs - take recently mentioned here Hyperscale SIG - do dns this *release* do dnf that *release* - dnf install centos-hyperscale-release - but, those are nowhere to be found or.. have I gone blind? If this all is delayed deliberately - may I ask why? many thanks, L.

4 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel