devel November 2022

devel@lists.centos.org

28 participants
27 discussions

Few questions on cloud images
by Pino Toscano 06 Jun '23

06 Jun '23

Hello, I have few questions related to the cloud images provides for c8s and c9s, i.e.: - https://cloud.centos.org/centos/8-stream/x86_64/images/ - https://cloud.centos.org/centos/9-stream/x86_64/images/ 1) I see the c9s images are regularly updated, while the c8s images not; is this wanted, or simply a mistake/miss somewhere? If so, will they be kept up-to-date just like the c9s images? 2) are the Vagrant images there officially supported? Let's say you use one, and find a bug; then check on a "classic" installation (baremetal/VM), and the bug isn't there; can users report problems in those cases? 3) would it be possible to have either unversioned or "-latest" symlinks for the latest versions of all the files (i.e. images, checksums, etc)? This way, it will be much easier for users to fetch the latest versions with no need to change URLs frequently. Of course, the assumption is that users of this are always willing to use the latest version. Thanks! -- Pino Toscano

7 14

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

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

Fwd: [CentOS] CentOS 7: Missing Thunderbird Updates
by Chris Schanzle 16 Dec '22

16 Dec '22

[No response on CentOS list, so trying CentOS-devel.] -------- Forwarded Message -------- Subject: [CentOS] CentOS 7: Missing Thunderbird Updates Date: Mon, 21 Nov 2022 15:33:56 -0500 From: Chris Schanzle via CentOS <centos(a)centos.org> Reply-To: Chris Schanzle <christopher.schanzle(a)nist.gov>, CentOS mailing list <centos(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Hi, Looks like CentOS 7 hasn't shipped Thunderbird updates for a while. The latest I see in repos is: Sep 1 15:22 thunderbird-91.13.0-1.el7.centos.x86_64.rpm Perusing through the RHEL announcements, that was from the RHSA-2022:6169-01 on 2022-08-24. Seems none of the 102.x versions have shipped: 2022-09-26 RHSA-2022:6710-01 thunderbird-102.3.0-3.el7_9.x86_64.rpm 2022-10-18 RHSA-2022:6998-01 thunderbird-102.3.0-4.el7_9.x86_64.rpm 2022-10-25 RHSA-2022:7184-01 thunderbird-102.4.0-1.el7_9.x86_64.rpm And for completeness, just announced today: 2022-11-21 RHSA-2022:8555-01 thunderbird-102.5.0-2.el7_9.x86_64.rpm Thanks in advance for efforts to find and clear the blockage!

6 19

dnf-makecache.service failing every few days and dnf-automatic.service samba sssd issues (again).
by Jelle de Jong 06 Dec '22

06 Dec '22

Hello everybody, 1. I got many systems with failing dnf-makecache.service because some mirror/repo is tried once and fails. Is there an option to make dnf more reliable, to try the mirror url a few times and check its availability? man yum.conf does not # cat /etc/yum.conf [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=True best=True skip_if_unavailable=False ExecStart=/usr/bin/dnf makecache --timer 2. I saw in the mailing list the messages about samba sssd dependency issues. I got lots of servers failing my dnf-automatic because of this when can I expect a resolution for this? Kind regards, Jelle

1 2

Meson rebase in RHEL 9.2 (packages might start to FTBFS)
by Tomáš Popela 29 Nov '22

29 Nov '22

Hi everyone, We are going to rebase Meson from 0.58.2 to 0.63.3, see the bug[0] and merge request[1]. Generally this would mean a lot of breakages, but we've changed/downgraded some errors to warnings - see the description in the MR or text inside the SPEC file for more information. We've used the Mass Prebuild[2] tool to identify the possible breakages in RHEL and fix them in advance[3-5]. We will merge the MR and do the builds on Monday, December 5. [0] - https://bugzilla.redhat.com/show_bug.cgi?id=2022729 [1] - https://gitlab.com/redhat/centos-stream/rpms/meson/-/merge_requests/6 [2] - https://gitlab.com/fedora/packager-tools/mass-prebuild [3] - https://bugzilla.redhat.com/show_bug.cgi?id=2140107 - gegl04 [4] - https://bugzilla.redhat.com/show_bug.cgi?id=2140108 - gobject-introspection [5] - https://bugzilla.redhat.com/show_bug.cgi?id=2140541 - shared-mime-info Regards, Tom -- Tomáš Popela Desktop and Desktop Applications Subsystems Product Owner Display Systems Red Hat

3 2

CentOS Connect at FOSDEM
by Shaun McCance 28 Nov '22

28 Nov '22

Hi folks, We're finally ready for the full announcement! Join us in Brussels on Friday, February 3 for CentOS Connect. https://connect.centos.org/ CentOS Connect is a free mini-conference focusing on CentOS Stream, the CentOS SIGs, and the entire Enterprise Linux ecosystem. We're looking forward to seeing people in person again. And if you can't make it to Brussels, we're planning a virtual component as well. The Call for Proposals is now open, until December 14. We're looking for both short and long talks about CentOS Streams, our SIGs, and everything surrounding the CentOS project. See the website for more details and for the submission link. Please spread this information wherever you think people might be interested. And remember to register. Registration is free, but space is limited and we may not be able to accept walkins. Also, we will have a room block at the event hotel, but I don't have the link available yet. I'll update as soon as I have it. Thanks! Shaun McCance CentOS Community Architect Red Hat Open Source Program Office

1 1

firewalld and NEW FreeIPA file "freeipa-4" broken in a rule set
by Günther J. Niederwimmer 26 Nov '22

26 Nov '22

Hello List, Does anyone have any idea why the "NEW" freeipa-4 for firewalld does not work as a "rule", all ports remain closed? with the command firewall-cmd --permanent --zone=external --add-service=freeipa-4 does it open the ports but it doesn't work in a rule statement? firewall-cmd --add-rich-rule='rule family="ipv4" source address="89.XXX.XXX.0/ XX" service name="freeipa-4" log prefix="freeipa-4" level= "info" limit value="1/m" accept' --permanent it is extra in freeipa-4 you should use the NEW freeipa-4 everything else is outdated? Where's the mistake? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer

1 0

CPE Weekly Update for Week 47 of 2022
by Akashdeep Dhar 26 Nov '22

26 Nov '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update-week-47-2022/. If you want to receive weekly reports by email in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team Thanks and regards, Akashdeep Dhar t0xic0der(a)fedoraproject.org akashdeep(a)redhat.com

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel November 2022