devel

devel@lists.centos.org

16 participants
4590 discussions

Proposal: CentOS Public Board Meetings
by Rich Bowen 07 Jan '23

07 Jan '23

In January of 2021, the CentOS Board of Directors opened our monthly meetings to all SIG chairs, in a first step towards more transparent governance. We wanted to see how the larger audience changed the meeting dynamics, if at all, as well as welcoming a broader pool of voices. We are now ready for the second part of this process. Starting in the August meeting, we will be inviting the entire CentOS community to attend these meetings. Due to the nature of the Internet, we won’t be simply publishing the meeting URL, as this often leads to disruptive behavior in meetings, as I am sure many of you have experienced. Rather, in the week before the meeting, we’ll send, to this list, a way to request an invitation to the meeting. In this way, we hope to limit the incidence of such disruptions, while also making the meeting available to anyone who wishes to attend. We will be working on the rules of engagement for these meetings, but they will be, at minimum: * 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/redactions, 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. Because there will seldom be time for Q&A during the meeting itself, we plan to add a post-meeting IRC office hours session for followup questions. This will probably be scheduled for a week after the board meeting, to allow time to publish meeting minutes We welcome your comments about the above proposal, and thank you all for your patience as we implement these changes to our governance process.

8 27

GTK 2 removal from RHEL 10+
by Tomáš Popela 06 Jan '23

06 Jan '23

Hi everyone, I'm actually resending this again, as I've sent it here at the same time as to fedora-devel ( https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…), but it probably never reached centos-devel as I'm not able to find it in archives. This is an early heads-up about GTK 2 removal from RHEL 10+ (the gtk2 package was marked as unwanted in ELN with https://github.com/minimization/content-resolver-input/commit/b6d44e496f46b…). The toolkit served us gratefully, but it starts to show its age with regards to modern technologies such as Wayland, HiDPI screens, HDR and others. In RHEL 10 the GTK 3 and GTK 4 will still continue to be available for everyone to use. Regards, Tom Popela -- Tomáš Popela Desktop and Desktop Applications Subsystems Product Owner Display Systems Red Hat

1 0

Infra SIG Meeting Minutes (2022-12-14) & Next Meeting Details (2023-01-11)
by Aoife Moloney 05 Jan '23

05 Jan '23

Sorry for the long title, I will work on that :) Below are the meeting minutes from the Infra SIGs last session in December 2022. It's a bit late being sent due to some illness & holidays at the end of December, but we hope you all enjoyed some time off over the end of last year and the New Year too! ## 2022-12-14 ### TO-DOs * Schedule an upgrade for koji builders in CentOS Stream to move from 1.30 -> 1.31 & announce outage window. We will formally agree to the date(s) for this work at the next infra meeting * Review the policy file for build & tag structure - this is in the release notes for koji so this will need to be reviewed and amended to match what is happening in the infrastructure. https://docs.pagure.org/koji/release_notes/release_notes_1.31/#system-chang… ### In Flight * Investigate ways to optimize the downloading experience for end users such as: * Tuning our cloudfront APIs like cache expiry & regional-level items, eg composes.centos.stream.org is fronted by cloudfront and the textfiles are not cached (compose id, tree info, etc) so we would like to tune this flow * Review of the policies we are using at cloudfront ### Done * mirror.stream.centos.org has been migrated to cloudfront setup* cbs.centos.org has been upgraded to koji 1.31 ## Next Meeting Agenda (2023-01-1) * Discuss the possibility of Power 10 building for CentOS Stream* Stream koji upgrade 1.30 -> 1.31 date planning ### Meeting Time & joining details: * Wednesday 11th Jan @ 12:30pm Ireland Time (I never seem to write time zones correctly so I am just using mine :) ) * Google Meet: meet.google.com/sgb-ubrz-vzz or Join by phone ‪(IE) +353 1 571 1000‬ PIN: ‪360 311 061 1805‬# Kindest regards, Aoife - on behalf of the CentOS Infra SIG -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA <https://www.redhat.com> Communications House Cork Road Waterford <https://www.redhat.com>

1 0

CentOS Hyperscale SIG meetup @ Connect/FOSDEM 2023
by Davide Cavalca 05 Jan '23

05 Jan '23

Hello, The CentOS Hyperscale SIG will be holding an in-person meetup on on February 2nd, 2023 at DoubleTree Brussels City Center Hotel. This is the same venue hosting CentOS Connect on February 3rd, and only a short walk from where FOSDEM will be held over the weekend. The meetup is open to everybody interested -- you don't have to be a member of the SIG to attend, and we'd welcome participation from anyone interested in this space. The event will be held from 9am to 5pm in the Birth room at the DoubleTree hotel. While this is an in-person event, we will do our best to setup a conference bridge so that remote participants can attend and interact as well. Please register at https://www.eventbrite.com/e/centos-hyperscale-sig-meetup-connectfosdem-202… to help with the event planning. Cheers Davide

1 0

Pruning old/scratch jobs from cbs.centos.org koji storage
by Fabian Arrotin 04 Jan '23

04 Jan '23

Hi all, We recently reviewed our storage consumption and one thing I realized is that, apart from running on out-of-warranty, the nfs share used by cbs.centos.org koji is growing (which is a good sign that people/SIGs are using it) but also with things that shouldn't stay behind, like temporary scratch (test) builds. Problem is that apart from consuming disk space on that nfs storage node, it's also consuming resources on the (older) backup node, also extending the needed time to take backup. I intend (in the following days) to implement through ansible a script itself just based on upstream koji-prune-scratch one (https://pagure.io/koji-tools/blob/master/f/src/bin/koji-prune-scratch) I'd like to start cleaning (deleting) scratch jobs that are (like in that upstream script) more than 7 days (scratch builds aren't proper builds and so are never tagged and so never signed/pushed out to mirrors). -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab@fosstodon.org

1 0

Alt Images SIG meeting minutes (2022/12/22)
by Troy Dawson 22 Dec '22

22 Dec '22

Meeting summary --------------- * Image build systems: livecd and kiwi - Infra ticket to create build targets in CBS https://pagure.io/centos-infra/issue/988 -- Looks like nothing is going to happen until next year. But it looks like it will be done before the ImageBuilder stuff happens. - koji is not importing all the comps stuff needed -- https://pagure.io/koji/issue/3626 -- koji skips environment and category groups when importing the comps files. -- The workaround it to use just regular groups for everything. It's alot more work, but at least it is possible. - Neal's backport of the upstreamed kiwi-live feature to support automatic persistent overlays on live USBs was merged into RHEL 9's dracut and it should be in c9s now: https://kojihub.stream.centos.org/koji/buildinfo?buildID=27844 -- Some anaconda patches/fixes are needed so this doing break installations from livecd's. * Image build systems: ImageBuilder - Infra ticket to create build targets in CBS https://pagure.io/centos-infra/issue/971 -- Not expected to get any movement from infra until next year. * Open Floor - Clarified that meetings are twice a month, on the 2nd and 4th Thursday -- Next meeting will be on January 12, 2023 at the usual time. People Present (lines said) --------------------------- * tdawson (66) * Eighth_Doctor (42) * davide (9) * davdunc[m (8) * salimma (6) * centguard (5) * rcallicotte (5) * michel-slm (0 Minutes and Log --------------- https://www.centos.org/minutes/2022/December/centos-meeting.2022-12-22-19.0… https://www.centos.org/minutes/2022/December/centos-meeting.2022-12-22-19.0… https://www.centos.org/minutes/2022/December/centos-meeting.2022-12-22-19.0…

1 0

Changes to CentOS CI: New OpenShift instance and Updates
by Camila Granella 22 Dec '22

22 Dec '22

*TL;DR: new OpenShift instance is up and running for CentOS CI, migrate your workloads by March 31st, 2023. Test your access to both the Duffy API and the new OpenShift instance by the end of 2022. CentOS CI changes approaching the end of Phase 3. * Hello everyone, We are happy to announce that the new OpenShift instance is up and running (ticket [0]). For the tenants that opted in to continue using CentOS CI, you are being required to *migrate your workload to the new OpenShift instance by the end of Q1CY23*, with the final deadline being *March 31st, 2023*. In order to support you through the migration process, the team has created a quick guide that can be found in [1]. We would also like to request you test your access to both the Duffy API and the new OpenShift instance by the *end of 2022*. Please reach out to us in case it is not working. Here is the link to the new OCP cluster [2]. As a reminder, this new OCP cluster is running in AWS, on top of EC2 instances, so coming with different limitations when compared with “on-premises bare-metal OCP deployments”. One notable change is that it is not possible to expose /dev/kvm and so there is no way for tenants to deploy VMs through OpenShift (like with the kubevirt operator or else). Tenants having a need to use VMs can then request some through Duffy API. Finally, here's a friendly reminder of the CentOS CI changes' current status. According to our previous communications [3], we are approaching the end of the last phase of the changes that have been implemented to CentOS CI. *Phase 3 - Decommission* - Legacy/compatibility API deprecated and requests (even for EC2 instances) will no longer be accepted - All tenants that opted in will be using only EC2 for aarch64/x86_64 and on-premise cloud for ppc64le For a full description of the project phases, you can check [3]. Please, feel free to reach out to us in case you have any questions or concerns. Regards, [0] https://pagure.io/centos-infra/issue/969 [1] https://sigs.centos.org/guide/ci/#migration-to-new-ci-instance [2] https://console-openshift-console.apps.ocp.cloud.ci.centos.org/ [3] https://lists.centos.org/pipermail/ci-users/2022-June/004547.html -- Camila Granella Associate Manager, Software Engineering Red Hat <https://www.redhat.com/> @Red Hat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

2 1

CentOS Connect Schedule
by Shaun McCance 21 Dec '22

21 Dec '22

The full schedule for CentOS Connect at FOSDEM is up with 14 amazing talks. CentOS Connect is a free mini-conference on topics across the Enterprise Linux ecosystem. If you're coming to FOSDEM, come in a day early and join us. Registration is free but strongly recommended. Hope to see you there. https://connect.centos.org/

2 1

FreeIPA / Samba / SSSD - new packages same problems
by lejeczek 21 Dec '22

21 Dec '22

Hi gents. It seems this has been a routine - each time when either sssd or Samba or FreeIPA gets new releases (with freeIPA deployed) there will be 'rpm' conflicts: Problem 1: package sssd-common-pac-2.7.3-5.el8.x86_64 requires libndr.so.2()(64bit), but none of the providers can be installed - package sssd-common-pac-2.7.3-5.el8.x86_64 requires libndr.so.2(NDR_0.0.1)(64bit), but none of the providers can be installed - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.4-2.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.3-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.4-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-3.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-4.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-5.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.15.5-8.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.1-0.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.2-1.el8.x86_64 - cannot install both samba-client-libs-4.17.2-2.el8.x86_64 and samba-client-libs-4.16.4-1.el8.x86_64 - cannot install the best update candidate for package sssd-common-pac-2.7.3-4.el8.x86_64 - cannot install the best update candidate for package samba-client-libs-4.16.4-2.el8.x86_64 Problem 2: package sssd-idp-2.7.3-4.el8.x86_64 requires sssd-common = 2.7.3-4.el8, but none of the providers can be installed - package libsss_autofs-2.7.3-5.el8.x86_64 conflicts with sssd-common < 2.7.3-5.el8 provided by sssd-common-2.7.3-4.el8.x86_64 - cannot install the best update candidate for package sssd-idp-2.7.3-4.el8.x86_64 - cannot install the best update candidate for package libsss_autofs-2.7.3-4.el8.x86_64 Problem 3: package sssd-common-pac-2.7.3-5.el8.x86_64 requires libndr.so.2()(64bit), but none of the providers can be installed - package sssd-common-pac-2.7.3-5.el8.x86_64 requires libndr.so.2(NDR_0.0.1)(64bit), but none of the providers can be installed Or it's just me? many thanks, L.

6 10

dnf stuff has broken dependencies
by Leon Fauster 19 Dec '22

19 Dec '22

FYI: The samba issue is gone but following is still an issue: # LANG=C yum update Last metadata expiration check: 0:00:18 ago on Fri Nov 25 23:48:00 2022. Dependencies resolved. Problem 1: package python3-dnf-plugin-modulesync-4.0.21-14.1.el8.noarch requires python3-dnf-plugins-core = 4.0.21-14.1.el8, but none of the providers can be installed - cannot install both python3-dnf-plugins-core-4.0.21-16.el8.noarch and python3-dnf-plugins-core-4.0.21-14.1.el8.noarch - cannot install the best update candidate for package python3-dnf-plugins-core-4.0.21-14.1.el8.noarch - cannot install the best update candidate for package python3-dnf-plugin-modulesync-4.0.21-14.1.el8.noarch Problem 2: problem with installed package python3-dnf-plugin-modulesync-4.0.21-14.1.el8.noarch - package python3-dnf-plugin-modulesync-4.0.21-14.1.el8.noarch requires python3-dnf-plugins-core = 4.0.21-14.1.el8, but none of the providers can be installed - cannot install both python3-dnf-plugins-core-4.0.21-16.el8.noarch and python3-dnf-plugins-core-4.0.21-14.1.el8.noarch - package dnf-plugins-core-4.0.21-16.el8.noarch requires python3-dnf-plugins-core = 4.0.21-16.el8, but none of the providers can be installed - cannot install the best update candidate for package dnf-plugins-core-4.0.21-14.1.el8.noarch ============================================================================================================================================================================= Package Architecture Version Repository Size ============================================================================================================================================================================= Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): python3-dnf-plugins-core noarch 4.0.21-16.el8 baseos 258 k Skipping packages with broken dependencies: dnf-plugins-core noarch 4.0.21-16.el8 baseos 75 k Transaction Summary ============================================================================================================================================================================= Skip 2 Packages Nothing to do. Complete! -- Leon

2 2

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