devel

devel@lists.centos.org

9 participants
4597 discussions

[Storage-SIG] - missing package python3-pyxattr in all the gluster-11 repos
by kAja Ziegler 08 Jan '25

08 Jan '25

Hello developers and maintainers, I want to report, that the package python3-pyxattr-0.7.2-4.el9s.*.rpm is missing in all the gluster-11 repos. Due to missing dependency then the glusterfs-server package cannot be installed. Repositories for gluster-9 and gluster-10 contain such package. With best regards, -- Karel Ziegler e-mail: ziegleka(a)gmail.com

3 2

2025-01-08 - CentOS Public Board Meeting
by Thomas Oulevey 06 Jan '25

06 Jan '25

Hi Everyone, Our next board meeting will take place at 21:00 UTC next Wednesday `date -d "2025-01-08 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/H1P1F3dLyg 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

December 2024 News
by Shaun McCance 20 Dec '24

20 Dec '24

Hi all, For your holiday reading, the December newsletter is now available: https://blog.centos.org/2024/12/december-2024-news/ Cheers, Shaun

1 0

December Board Meeting Recap
by Shaun McCance 19 Dec '24

19 Dec '24

The recording of the December CentOS Board meeting is now available. Recording: https://youtu.be/8ficzt0l-xo Minutes: https://hackmd.io/@centosboard/S1ta-46Xkx Recap: https://blog.centos.org/2024/12/centos-board-meeting-recap-december-2024/ The recording has timestamps so you can skip to the parts that interest you. Here are a few highlights of the meeting: * Firefox is not in CentOS Stream 10. We discussed ways of getting web browsers, and documenting them. * The board discussed disabling GitLab Duo on CentOS repositories. * The community architect provided an update on CentOS Connect and the efforts to revamp the web and docs. * The board discussed encouraging SIGs to use GitLab by default. Thanks, Shaun

1 0

Proposal to default to GitLab for SIG packaging
by Davide Cavalca 16 Dec '24

16 Dec '24

In the last Board meeting we discussed the future of git.centos.org, and whether it would make sense to encourage SIGs to move over to GitLab, as we already have a group at gitlab.com/centos and that's where CentOS Stream development is happening (under gitlab.com/redhat/centos-stream) GitLab also provides features (notably, CI integration via Pipelines and an improved code review flow) that some SIGs would like to use and would benefit from. To this end, I have filed https://git.centos.org/centos/board/issue/129 to summarize the discussion and decide the next steps. We'd welcome any comments and feedback on this. To be clear, there are no plans to sunset git.centos.org at this time. Cheers Davide

6 7

CentOS bootc images - Where should they go
by Troy Dawson 08 Dec '24

08 Dec '24

The CentOS Alternative Images SIG has recently been asked about making CentOS bootc images.[1] Investigation is showing that we should be able to. But that leads to the next question. After we build them, where would they go? (A) Initial thoughts are someplace in the CentOS SIG infrastructure. But there currently isn't anything setup for serving containers. It's also not the first place people would look. I was thinking of having them on quay.io. But if we do publish our bootc/container images on quay.io, where? (B) centos:<some-name> ? That would mean that the SIG's would have access to that account. I also don't know what we would have for <some-name>. We would have to have something different for each SIG. (C) centos-sig:<some-name> ? The SIG's would still have to share authentication in some manner. I still don't know what to do for the names. (D) centos-<sig-name>:<some-name> The SIG's would have their own authentication. The sig's would have control of their own naming convention. centos-altimages:stream10-bootc centos-altimages:stream10-bootc-kde centos-isa:stream9-bootc-baseline centos-isa:stream9-bootc-optimized There are some drawbacks for this. Someone would have to know the SIG name to find the image. Possibly other things. I personally am leaning towards (D). But I could be persuaded towards the others. And it's possible I haven't even thought of the correct solution. Ideas / thoughts / comments welcomed and wanted. Troy [1] - https://pagure.io/centos-sig-alt-images/sig/issue/10

6 6

centos-release-nfv-openvswitch broken
by kfox1111＠gmail.com 05 Dec '24

05 Dec '24

$ podman run -it --rm quay.io/centos/centos:stream9 [root@5a60bfec416f /]# yum install -y centos-release-nfv-openvswitch <snip> [root@5a60bfec416f /]# yum list CentOS Stream 9 - NFV OpenvSwitch 916 B/s | 3.0 kB 00:03 Errors during downloading metadata for repository 'centos-nfv-openvswitch': - Downloading successful, but checksum doesn't match. Calculated: a0898eb5ec407553a28821d486e5635b512ea30dd5a170ac76843e8139908887d7773e08d76346e069cebf2e24730648ecdc10595ba5aa6173884fef3d76f4e9(sha512) Expected: 19f066708fc1f00703fa6514d39edebc74fd3aaff9488a2e1fc2599485fdb8775b8af2a912913a2131f6529fe92d60efa1051a4e14fe32eb01d357a1e51c3a86(sha512) Error: Failed to download metadata for repo 'centos-nfv-openvswitch': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

3 2

Re: devel Digest, Vol 237, Issue 3
by Pierre De Jager 25 Nov '24

25 Nov '24

Please unsubscribe me On Mon, Nov 25, 2024 at 5:41 PM <devel-request(a)lists.centos.org> wrote: > Send devel mailing list submissions to > devel(a)lists.centos.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > devel-request(a)lists.centos.org > > You can reach the person managing the list at > devel-owner(a)lists.centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of devel digest..." > > Today's Topics: > > 1. CentOS bootc images - Where should they go (Troy Dawson) > 2. Re: CentOS bootc images - Where should they go (Neal Gompa) > 3. Re: CentOS bootc images - Where should they go (Troy Dawson) > 4. Re: CentOS bootc images - Where should they go (Fabian Arrotin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 25 Nov 2024 07:00:54 -0800 > From: Troy Dawson <tdawson(a)redhat.com> > Subject: [CentOS-devel] CentOS bootc images - Where should they go > To: "The CentOS developers mailing list." <centos-devel(a)centos.org> > Message-ID: > < > CAKndyURTg52b6JwzgjddYDiW-gE9b6-RB30GL7ejz6NxcgBO6w(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="00000000000077ac470627be00b8" > > The CentOS Alternative Images SIG has recently been asked about making > CentOS bootc images.[1] > > Investigation is showing that we should be able to. But that leads to the > next question. After we build them, where would they go? > > (A) Initial thoughts are someplace in the CentOS SIG infrastructure. But > there currently isn't anything setup for serving containers. It's also not > the first place people would look. > > I was thinking of having them on quay.io. > But if we do publish our bootc/container images on quay.io, where? > > (B) centos:<some-name> ? > That would mean that the SIG's would have access to that account. > I also don't know what we would have for <some-name>. > We would have to have something different for each SIG. > > (C) centos-sig:<some-name> ? > The SIG's would still have to share authentication in some manner. > I still don't know what to do for the names. > > (D) centos-<sig-name>:<some-name> > The SIG's would have their own authentication. > The sig's would have control of their own naming convention. > centos-altimages:stream10-bootc > centos-altimages:stream10-bootc-kde > centos-isa:stream9-bootc-baseline > centos-isa:stream9-bootc-optimized > There are some drawbacks for this. Someone would have to know the SIG name > to find the image. Possibly other things. > > I personally am leaning towards (D). But I could be persuaded towards the > others. And it's possible I haven't even thought of the correct solution. > > Ideas / thoughts / comments welcomed and wanted. > > Troy > > [1] - https://pagure.io/centos-sig-alt-images/sig/issue/10 >

1 0

2024-11-13 - CentOS Public Board Meeting
by Thomas Oulevey 07 Nov '24

07 Nov '24

Hi Everyone, Our next board meeting will take place at 21:00 UTC next Wednesday `date -d "2024-11-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/SJDtP3cZJe 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

[FYI] : all CBS koji builders now reinstalled on el9
by Fabian Arrotin 05 Nov '24

05 Nov '24

Sending this ticket for awareness : In the last days, I had time to disable some koji builders (https://cbs.centos.org/koji/hosts) , reinstall/migrate these from el8 to el9, and enable these builders back in the available pool. It finished today [1] and so all builders, all architectures are now running el9.4 . Only the kojihub infra is still running on el8 but that will be migrated later (kojihub itself doesn't have any impact on build infrastructure). The main reason why we updated was to ensure we'd be running a newer kernel for the systemd-nspawn isolation, that was causing troubles when running on top of el8 (kernel 4.18) , especially when relying on likcapi calls from within the chroot'ed build env. For more details and workaround (not needed anymore) that we used to allow building CentOS Stream 10 pkgs for SIGs, see [2] At the same time, what triggered also the reinstall was also the need to re-balance workload across different hardware/chassis [3] : the x86_64 kojid builders are in fact running on some un-warrantied (and older) machines and I wanted to reconfigure similar machines dedicated previously for some other things (including CI / on-premises openshift cluster / etc) to ensure that we'd still have some x86_64 builders running behind https://cbs.centos.org, should we encounter a whole chassis hardware failure . Same for some small services used by koji builders themselves (like small cache/proxy to retrieve external content, like gitlab.com - now spread across two distinct hardware with ucarp and floating ip address[es] for ha purposes) You'll see that we have now more x86_64 builders, and that some tasks (like createrepo, rebuildSRPM, etc) are exclusively targeted on these hosts, freeing some cpu cycles from aarch64/ppc64le/s390x builders, that will be only used for specific rpmbuild tasks. Also worth knowing that I was able (due to decommissioned cores/memory that was used for centos stream 8/centos linux 7) to extend/tune number of cores/available memory on reinstalled aarch64 and ppc64le koji builders, hopefully helping to build faster your SIGs packages for these architectures. Nothing is required from you, SIGs builders, as the whole migration happened transparently , without any downtime, so just enjoy more compute capacity / redundancy for https://cbs.centos.org (and let's hope that we'll not suffer from hardware failure in the future) [1] https://pagure.io/centos-infra/issue/1505 [2] https://pagure.io/centos-infra/issue/1474 [3] https://pagure.io/centos-infra/issue/1528 -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

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