devel December 2023

devel@lists.centos.org

9 participants
6 discussions

freeIPA rpm packages issue
by lejeczek 03 Jan '24

03 Jan '24

Hi guys. To let @devel & freeIPA know - if one uses freeIPA -> $ dnf update -y Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64 1.7 kB/s | 2.5 kB 00:01 Error: Problem: cannot install the best update candidate for package ipa-selinux-4.11.0-3.el9.noarch - nothing provides selinux-policy >= 38.1.28-1.el9 needed by ipa-selinux-4.11.0-4.el9.noarch from appstream - nothing provides selinux-policy-base >= 38.1.28-1.el9 needed by ipa-selinux-4.11.0-4.el9.noarch from appstream (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) regards, L.

3 3

no ARM / AARCH ?
by lejeczek 13 Dec '23

13 Dec '23

Hi guys. I've never paid much attention towards it - were ARM parts of Qemu always absents in Centos and if yes then: a( why? (Fedora seems to include those) b) is there anything in repos to emulate it? many thanks, L.

3 2

2023-12-13 - CentOS Public Board Meeting
by Thomas Oulevey 11 Dec '23

11 Dec '23

Hi Everyone, Our next board meeting will take place at 21:00 UTC on next Wednesday: `date -d "2023-12-13 21: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 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/BJSN0HE8T 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, -- Thomas 'alphacc' Oulevey CentOS Board of Directors Secretary alphacc(a)centosproject.org

1 0

reporting to Redhat's Jira
by lejeczek 08 Dec '23

08 Dec '23

Hi guys. Where should bug reports go to theses days? I've been using Redhat's Jira for a while and inasmuch I can file against Centos, when I go RHEL and -> Centos as a product I get a pop-on windows but no matter how I fiddle with it, when I click _Create_ that pop-up only flashes, no errors nor warnings, but won't create a BZ. It that an incorrect way/place or something else is at play there or perhaps Jira suffers from some issues - would anybody know? thanks, L.

4 6

FOSDEM, Distros Devroom, and CentOS Connect
by Shaun McCance 04 Dec '23

04 Dec '23

Hi folks, In case you missed it, the Distributions Devroom will be back at FOSDEM 2024. The CFP deadline is TOMORROW: https://blog.centos.org/2023/12/distributions-devroom-fosdem-2024/ Are you doing something cool that would be interesting to people working on the various distros? You should submit a proposal. Also remember that we're hosting CentOS Connect the two days before FOSDEM. The CFP for that is open a bit longer, until December 18. Please submit proposals for anything related to CentOS or the wider Enterprise Linux ecosystem. We also have a half day for meetups. If you'd like to host a meetup around a team or project, submit that in the CFP system as well. https://connect.centos.org/ Thanks, Shaun

1 0

mdadm: --update=resync not understood for 1.x metadata
by Strahil Nikolov 04 Dec '23

04 Dec '23

Hi All, Recently I had to update a host that uses raid1 for /boot and /boot/efi and I noticed that my resync service is failing with "mdadm: --update=resync not understood for 1.x metadata”. Does anyone know why 'mdadm-4.2-rc2.el8.x86_64.rpm’ supports it but 'mdadm-4.2-13.el8.x86_64’ not ? Why the version is not properly bumped if such drastic change is intentional ? Best Regards, Strahil Nikolov

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel December 2023