devel

devel@lists.centos.org

4 participants
4640 discussions

Planned service outage : Stream 9 koji build infra
by Fabian Arrotin 20 Sep '22

20 Sep '22

Due to an underlying storage migration (migrating from local NFS host to centralized Netapp filer), we'll have to freeze the dedicated CentOS Stream koji infrastructure (externally known as https://kojihub.stream.centos.org) At the same time we'll migrate the lookaside cache server (aka https://sources.stream.centos.org) from local iscsi target volume to new iscsi lun served also from new Netapp filer. Impacted services: - kojihub and builders for CentOS Stream (https://kojihub.stream.centos.org) - lookaside cache server (https://sources.stream.centos.org) That also means that external services pointing to kojihub (like for cbs.centos.org for SIGs/tag using directly upstream koji as buildroot[s]) will be impacted , so take that into account. Migration is scheduled for """"Friday September 30th, 11:00 am UTC time"""". You can convert to local time with $(date -d '2022-09-30 11:00 UTC') The expected "downtime" is estimated to (maximum) 4h , time needed to : - freeze koji infra and builders - freeze lookaside cache server - (final) data sync between old and new storage volumes - storage volume swap - validate service[s] and have these available again You can also join us in either #centos-devel or #centos-stream irc channels on irc.libera.chat if you encounter any issue. Thanks for your understanding and patience. on behalf of the CentOS Stream Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

August board meeting recording and office hours
by Shaun McCance 17 Sep '22

17 Sep '22

Hi folks, I've uploaded the recording of last week's board meeting: https://youtu.be/MkB7atd82KU If you'd like to discuss any issues with the board, we'll have an open board office hours this Thursday, September 22, at 14:00 UTC. https://meet.google.com/buz-dvqw-cgk Email me directly if you need dial-in info instead. Thanks, Shaun

1 0

CPE Weekly Update – Week 37 2022
by Lenka Segura 16 Sep '22

16 Sep '22

Hi everyone, You can find this week's CPE (Community Platform Engineering) weekly report here: https://communityblog.fedoraproject.org/cpe-weekly-update-week-37-2022/ If you want to keep receiving weekly reports by email, 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. Cheers, CPE Team

1 0

libknet1- in more than one repo
by lejeczek 09 Sep '22

09 Sep '22

Hi guys. that most certainly should not be, right? -> $ dnf list libknet1 Last metadata expiration check: 0:00:37 ago on Fri 09 Sep 2022 10:44:07 BST. Installed Packages libknet1.x86_64 1.24-2.el8 @ha Available Packages libknet1.i686 1.24-2.el8 ha libknet1.i686 1.24-2.el8 powertools but in case it should then the problem is: -> $ dnf update ... Error: Problem 1: package libknet1-compress-bzip2-plugin-1.24-3.el8.x86_64 requires libknet1(x86-64) = 1.22-1.el8, but none of the providers can be installed - cannot install both libknet1-1.22-1.el8.x86_64 and libknet1-1.24-2.el8.x86_64 - cannot install the best update candidate for package libknet1-compress-bzip2-plugin-1.24-2.el8.x86_64 - cannot install the best update candidate for package libknet1-1.24-2.el8.x86_64 many thanks, L.

4 5

CPE Weekly Update - Week 36 2022
by Michal Konecny 09 Sep '22

09 Sep '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-36-2022/. If you want to receive weekly reports by emails 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

1 0

CentOS Cloud SIG meeting minutes (2022-08-09)
by Joel Capitao 08 Sep '22

08 Sep '22

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2022-09-08) ====================================================== Meeting started by jcapitao at 15:03:36 UTC. The full logs are available athttps://www.centos.org/minutes/2022/September/centos-meeting.2022-09-08-1… . Meeting summary --------------- * roll call (jcapitao, 15:03:45) * OKD/SCOS (CentOS Stream CoreOS 9) update (jcapitao, 15:07:46) * LINK: https://github.com/okd-project/okd-coreos-pipeline contains Tekton definitions for building the OS, the other repos are mostly concerned with building the container images deployed on top (lorbus, 15:18:41) * ACTION: lorbus to send an email on centos-devel ML to announce his nomination as co-chair (jcapitao, 15:39:37) Meeting ended at 15:49:37 UTC. Action Items ------------ * lorbus to send an email on centos-devel ML to announce his nomination as co-chair Action Items, by person ----------------------- * lorbus * lorbus to send an email on centos-devel ML to announce his nomination as co-chair * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jcapitao (39) * lorbus (31) * davdunc[m (21) * spotz (13) * centguard (6) * davide (3) * davdunc (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

IPA + dependencies issue - fail to update
by lejeczek 06 Sep '22

06 Sep '22

Hi guys. This issue is almost a month old - could @devel please look into it. Also a personal comment - this does not look too good as this is not the first time IPA when deployed has this very kind of problems - something there where freeIPA team & Centos team(s) co-exists/operate seems broken - it would be great if you guys(everybody involved) could look into it as well. many thanks, L Last metadata expiration check: 0:00:18 ago on Mon 05 Sep 2022 10:17:13 BST. Error: Problem 1: package ipa-server-trust-ad-4.9.8-7.module_el8.6.0+1103+a004f6a8.x86_64 requires libsmbconf.so.0(SMBCONF_0)(64bit), but none of the providers can be installed - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.16.2-1.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.13.3-3.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.4-4.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.5-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.5-2.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.3-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.4-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-3.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-4.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-5.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-8.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.16.1-0.el8.x86_64 - cannot install the best update candidate for package samba-client-libs-4.16.2-1.el8.x86_64 - cannot install the best update candidate for package ipa-server-trust-ad-4.9.8-7.module_el8.6.0+1103+a004f6a8.x86_64 Problem 2: problem with installed package ipa-server-trust-ad-4.9.8-7.module_el8.6.0+1103+a004f6a8.x86_64 - package ipa-server-trust-ad-4.9.8-7.module_el8.6.0+1103+a004f6a8.x86_64 requires libsmbconf.so.0(SMBCONF_0)(64bit), but none of the providers can be installed - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.16.2-1.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.13.3-3.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.4-4.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.5-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.5-2.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.3-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.4-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-3.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-4.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-5.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-8.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.16.1-0.el8.x86_64 - package libsmbclient-4.16.4-1.el8.x86_64 requires libsamba-debug-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libsmbconf.so.0(SMBCONF_0.0.1)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libreplace-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libsamba-security-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libsamba3-util-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libsecrets3-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libcli-smb-common-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libdcerpc-samba-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libmsrpc3-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libgse-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires liblibsmb-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires liblibcli-lsa3-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - cannot install the best update candidate for package libsmbclient-4.16.2-1.el8.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

3 2

Re: [CentOS-devel] [EPEL-devel] Re: [Messaging] RabbitMQ for EPEL 9
by Davide Cavalca 04 Sep '22

04 Sep '22

On Sat, 2022-09-03 at 13:39 -0500, Richard Shaw wrote: > Have you tried building the package yourself yet? When asking for > someone to support an EPEL branch it's not always straightforward. I > tried building the rawhide branch for EPEL 9 and ran into the > following: > > No matching package to install: 'elixir' > No matching package to install: 'erlang >= 23' I breifly looked into this a couple of months ago as someone asked me about it at work. From what I recall, erlang is mostly doable, but elixir is a problem because it pulls in a bunch of other stuff and seems to have a bit of a bootstrapping problem. I'm sure someone familiar with this ecosystem could get it sorted out, but that's not me so I ended up leaving it alone. Cheers Davide

1 0

Opensourcing the CentOS brand creative work, licensing thoughts
by Alain Reguera Delgado 03 Sep '22

03 Sep '22

Dear community, I would like to bring up this topic once again because it is relevant for the well-being of CentOS visual identity, and its future improvements on the long-term. This mail is probably for Red Hat Liaison, considering the legalities involved in relation to CentOS branding matters. Nevertheless, I would like to keep the discussion open to collect the vast majority of opinions possible about it. Considering the CentOS brand is presently a registered trademark of Red Hat, the exact questions are: 1. Related to CentOS brand changes, and design improvements: What does Red Hat allow the CentOS community to do, and not to do? Here, please, consider the legal and not-legal matters. 2. Would it be possible for Red Hat to explicitly set the license under which the CentOS brand (creative/design) work is released, so to grantee its openness inside the CentOS community? If not, please, elaborate why, and share the expected process to follow in order to keep the brand design relevant through time. I deliberately have collected some thoughts[1] about the recent CentOS brand actualization process but am not sure if they are aligned with Red Hat needs and expectations. The goal here would be to make a very clean and simple statement about how much autonomy does the CentOS community have over its own brand. Also, complement the CentOS Trademark Guidelines[2] document with such information, since there isn't mention of it at the moment. [1] https://gitlab.com/areguera/centos-brand [2] https://www.centos.org/legal/trademarks/ Appreciate your comments. Best regards. -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

3 4

CPE Weekly Update - Week 35 2022
by Lenka Segura 02 Sep '22

02 Sep '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-35-2022/cp…. If you want to receive weekly reports by emails 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

1 0

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