devel

devel@lists.centos.org

1 participants
4619 discussions

Where can I find updated CentOS artwork?
by Gordon Messmer 29 Jun '23

29 Jun '23

I don't want to reopen https://git.centos.org/centos/Artwork/issue/1 , but I'm not sure where to ask questions about the status of that work. The centos.org sites (www., wiki., and git.) use updated logos, but I can't find any updated artwork described at https://wiki.centos.org/ArtWork or any linked page. It's possible that I'm overlooking it. Any pointers?

4 4

ISA SIG rebuild status
by Florian Weimer 28 Jun '23

28 Jun '23

Last week, the ISA SIG concluded two rebuilds of a snapshot of CentOS 9 Stream with GCC 12, one with -march=x86-64-v2 (same as CentOS 9 Stream), and one with -march=x86-64-v3. The rebuilds are fairly complete. The following things are missing: * All modular content. * LibreOffice and OpenJDK. * Two Rust packages which require a rebase of their bundled rust-bindgen versions for Clang 16 compatibility. (Rust currently does not follow the subarchitecture in CFLAGS anyway.) I classifed most of the initial build failures, and here are some numbers: GCC 12 induced failures GCC 12 exposes latent undefined behavior 2 various issues (mostly -Werror) 18 GCC 12 C++ header inclusion changes 3 subtotal 23 x86-64-v3 test differences 7 general buildroot/time/policy changes 19 grand total 49 (We switch to GCC 12 for auto-vectorization at -O2 using the very-cheap cost model, something that cannot be model with GCC 11 compiler flags. Without that, a forward-looking comparison between -march=x86-64-v2 and -march=x86-64-v3 is not possible.) The x86-64-v3 test differences are mostly due to GCC's -ffp-contract=fast default, which does not match what some package test suites expect. We saw those on other architectures already, and with -march=x86-64-v3, GCC supports FMA, exposing them for the x86_64 architecture as well. Maybe upstream GCC can revisit the default there. The general failures are in some cases literally due to time because test certificates expired, or a hard-coded date in some test is no longer in the future. Disabling SHA-1 broke some tests as well. The rest is just general drift of build dependencies, introducing incompatibilities. FTBFS bugs have been filed in Red Hat Bugzilla as appropriate. We were able to eliminate a bunch of rebuild issues that are specific to the CBS Koji environment and do not show up in other environments. I should probably send out a separate note about that, in case other SIGs want to do mass rebuilds. We are still working out how to best deliver the rebuilt packages for testing. Until then, the packages are available from the Koji buildroot and can be (mostly) installed with “dnf distro-sync” from an existing CentOS 9 Stream system: <https://cbs.centos.org/kojifiles/repos/isa9s-packages-baseline-el9sbase-bui…> <https://cbs.centos.org/kojifiles/repos/isa9s-packages-optimized-el9sopt-bui…> I would like to thank Troy Dawson for shepherding the build process and reviewing and fixing issues, and Brian Stinson for resolving CBS Koji infrastructure issues. Florian

4 5

9-stream repo file for centos-plus(containing thunderbird)?
by Anthony Alba 27 Jun '23

27 Jun '23

Hi list, Which repo file contains the metalink to centos-plus(containing thunderbird). Here is my current list of repo files but none seem to reference centos-plus. Cheers AA # current list of repo files etc/yum.repos.d/centos-addons.repo etc/yum.repos.d/CentOS-Ceph-Pacific.repo etc/yum.repos.d/CentOS-Ceph-Quincy.repo etc/yum.repos.d/CentOS-Gluster-10.repo etc/yum.repos.d/CentOS-Gluster-11.repo etc/yum.repos.d/CentOS-Gluster-9.repo etc/yum.repos.d/centos-kmods.repo etc/yum.repos.d/centos-kmods-userspace.repo etc/yum.repos.d/CentOS-Messaging-rabbitmq.repo etc/yum.repos.d/CentOS-NFS-Ganesha-4.repo etc/yum.repos.d/CentOS-NFS-Ganesha-5.repo etc/yum.repos.d/CentOS-NFV-OpenvSwitch.repo etc/yum.repos.d/CentOS-OKD-4.13.repo etc/yum.repos.d/CentOS-OKD-4.14.repo etc/yum.repos.d/CentOS-OpenStack-antelope.repo etc/yum.repos.d/CentOS-OpenStack-Client-xena.repo etc/yum.repos.d/CentOS-OpenStack-yoga.repo etc/yum.repos.d/CentOS-OpenStack-zed.repo etc/yum.repos.d/CentOS-OpsTools.repo etc/yum.repos.d/CentOS-oVirt-4.5.repo etc/yum.repos.d/CentOS-oVirt-4.5-testing.repo etc/yum.repos.d/centos.repo etc/yum.repos.d/CentOS-Samba-414.repo etc/yum.repos.d/CentOS-Samba-415.repo etc/yum.repos.d/CentOS-Samba-416.repo etc/yum.repos.d/CentOS-Samba-417.repo etc/yum.repos.d/CentOS-Samba-418.repo etc/yum.repos.d/CentOS-Storage-common.repo etc/yum.repos.d/CentOS-Stream-Hyperscale-Experimental.repo etc/yum.repos.d/CentOS-Stream-Hyperscale.repo etc/yum.repos.d/CentOS-Stream-Hyperscale-Spin.repo etc/yum.repos.d/epel-next.repo etc/yum.repos.d/epel-next-testing.repo etc/yum.repos.d/epel.repo etc/yum.repos.d/epel-testing.repo

2 2

Furthering the evolution of CentOS Stream
by Leon Fauster 26 Jun '23

26 Jun '23

Hi All, I wonder if someone is in the role/position to shed some more light on the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream Any deadlines? Does this target only EL10 or also any current release? Would be great if some discussion/communication could be happen. Thanks! -- Leon

7 20

How was the old centos git repo maintained?
by Gordon Messmer 23 Jun '23

23 Jun '23

I never paid much attention to the repos in the past, but after reading a comment about "exploded src.rpms" I picked one to review... (https://git.centos.org/rpms/bash/commits/c8) It looks like there was a process (or a person?) that would unpack released src.rpms into a git repo, delete Source0, and then commit whatever was left. Is that approximately correct?

2 1

2023-06-14 - CentOS Public Board Meeting
by Thomas Oulevey 13 Jun '23

13 Jun '23

Hi Everyone, Our next board meeting will take place at 20:00 UTC tomorrow: `date -d "2023-06-14 20: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 Zoom 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/ry93GGRI2 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. Sorry for the late announcement. thanks, -- Thomas 'alphacc' Oulevey CentOS Board of Directors Secretary alphacc(a)centosproject.org

1 0

Planned Outage - networking upgrades - 2023-06-13 20:00 UTC
by Fabian Arrotin 13 Jun '23

13 Jun '23

Forwarding here the info that was sent to Fedora infra list ( https://pagure.io /fedora-infrastructure/issue/11365 ) In summary, today you'll probably see some services being unreachable, and impacted services are the ones located in the Fedora DC (it doesn't impact https://cbs.centos.org and others). Impacted services: - https://accounts.centos.org (and https://fasjson.fedoraproject.org that some infra services are using to retrieve users info and groups) - ns2.centos.org Worth knowing that, due to network upgrade, we'll also have to power off in advance some Virtual Machines that are located on a remote iscsi block device. And at the same time we'll also convert some VMs/KVM hosts from centos 7 to el9 Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 0

Discussion: Open technical questions concerning SIG content for RHEL releases
by Peter Georg 09 Jun '23

09 Jun '23

Dear all, There has been an inquiry to the CentOS Board to clarify how long SIGs can expect to be able to build against RHEL build targets [1]. This is necessary to allow SIGs themselves to communicate expected lifecycle of their content to users. The outcome of this, in summary, is that SIGs should be able to build against RHEL until it reaches EOL (end of Maintenance Phase) + 30 days (no access to ELS content). This policy follows the one used by EPEL. Note: It is (obviously) still up to every single SIG to decide if and for how long they want to support a particular RHEL (or CentOS Stream) release. This inquiry also included respectively raised some technical questions. These technical questions are not to be decided by the CentOS Board. In [2] it has been recommended to discuss these on centos-devel. So let's do that. I want to start with two open questions which I do know of. In case there are other open question concerning this matter please raise them here. First open question is where to push content produced by SIGs for RHEL8 to. To better understand the issue, let me summarize the current situation, for which we first need to define the used format for tags in CBS: <sig><el>-<project>-<version>-{candidate,testing,release} where <el> can currently be 7,8,8s,9,9s Packages tagged for -testing are pushed to: https://buildlogs.centos.org/centos/<el>/<sig>/<arch>/<project>-<version>/ Packages tagged for -released are push to: If el = 8 or 8s: debuginfo rpm packages: https://debuginfo.centos.org/centos/<el>/<sig>/<arch>/<project>-<version>/ src.rpm packages: https://vault.centos.org/centos/<el>/<sig>/Source/<project>-<version>/ Everything else: http://mirror.centos.org/centos/<el>/<sig>/<arch>/<project>-<version>/ If el = 9 or 9s: http://mirror.stream.centos.org/SIGs/<el>/<sig>/<arch>/<project>-<version>/ For src.rpm <arch> is source. Note: Although it is not relevant for the discussion, in fact on the mirrors the suffix "s" of <el> is replaced by "-stream". This currently is all fine. However it is planned that the infrastructure currently used for packages built for 8 or 8s will disappear once CentOS Stream 8 and CentOS Linux 7 are EOL (June 30th, 2024). So in case any SIG decides to produce content for RHEL 8 after that date packages can not be distributed properly anymore. Only using the -testing tag and thus https://buildlogs.centos.org is not really an option as it would probably produce too much load on these. My proposal: After CentOS Stream 8 went EOL (May 31st, 2024), which is the same date as the end of the Full support phase of RHEL 8, at least the -release tag of all RHEL 8 build targets is locked and SIGs have to opt-in in case they want to build content for RHEL 8 during its Maintenance Support phase (End: May 31st 2029) for a particular build target. For these, tagging for -release will then push content to http://mirror.stream.centos.org/SIGs/8/<sig>/<arch>/<project>-<version>/, i.e. the same location as used for 9 and 9s. This gives SIGs one month for all required changes before the currently infrastructure disappears. Of course this means additional work for SIGs and Infra. However at some point the location where to push content to has to be changed before the currently used infrastructure disappears. Choosing an earlier date would result in work for SIGs who do not want to continue providing any packages once RHEL 8 enters Maintenance Support phase anyway. The second open question concerns the centos-release-* packages provided by SIGs to allow users to easily consume SIGs' content. For 8s and 9s the CBS tags extras<el>-extras-common-{candidate,testing,release} are used to build these packages. This repository is added in CentOS Stream 8 and 9. For packages build for RHEL 8 and 9 there is currently no common way to provide any means of easing the process to consume SIGs' content. My proposal to fix this is by adding extras<el>-extras-common-{candidate,testing,release} for <el> = 8 and 9, i.e., using the same system as currently used for 8s and 9s. To further ease the process I propose to introduce a package named centos-release-extras which contains the repository config pointing to the content of the tags extras<el>-extras-common-{testing,release} (only -release enabled by default) and the CentOS-SIG-Extras GPG key. The centos-release-extras packages itself would be built in the extras<el>-extras-common-el<el> build target. Users of RHEL would then only need to install this single package to allow them to easily install any other centos-release-* packages. Obviously someone needs to maintain the centos-release-extras package. I volunteer to maintain this package. [1]: https://git.centos.org/centos/board/issue/82 [2]: https://pagure.io/centos-infra/issue/1002

4 11

Introducing the CentOS ISA SIG
by Josh Boyer 09 Jun '23

09 Jun '23

Hi All, As Florian Weimer originally proposed, we have created the CentOS ISA SIG to focus on potential benefits of newer ISA baselines and optimizations. You can find our bare-bones SIG docs here: https://sigs.centos.org/isa/ We'll be adding more information to that site over the coming weeks. For now, we're getting SIG projects setup and bootstrapped. There is a #centos-isa libera.chat IRC channel for the SIG and anyone interested is welcome to join and follow along. We'd like to thank the CentOS community and Board for their support, the CentOS Infra team for the rapid response and help, and the Hyperscaler SIG for providing some great examples to follow on SIG setup. josh

1 0

CentOS Cloud SIG meeting minutes (2023-06-08)
by Joel Capitao 08 Jun '23

08 Jun '23

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2023-06-08) ====================================================== Meeting started by jcapitao[m] at 14:59:47 UTC. The full logs are available athttps://www.centos.org/minutes/2023/June/centos-meeting.2023-06-08-14.59.… . Meeting summary --------------- * roll call (jcapitao[m], 15:00:06) * centos-release-cloud RPM contains now the GPG key of Cloud SIG (jcapitao[m], 15:04:43) * all centos-release-openstack CS9 RPMs requires it now (jcapitao[m], 15:05:13) * LINK: https://git.centos.org/rpms/centos-release-openstack/pull-requests (jcapitao[m], 15:07:20) * OKD/SCOS updates (jcapitao[m], 15:22:29) * current pre-release: https://github.com/okd-project/okd-scos/releases/tag/4.14.0-0.okd-scos-2023… (lorbus, 15:22:44) * current latest release: https://github.com/okd-project/okd-scos/releases/tag/4.13.0-0.okd-scos-2023… (lorbus, 15:23:04) * work has begun to onboard OKD dependency RPMs to CBS (lorbus, 15:23:43) * OKD repo files are available in the centos-release-okd-4.13 and centos-release-okd-4.14 RPMs (from extras-common) (lorbus, 15:25:35) * OKD cluster on MOC is down for maintenance until June 12 (lorbus, 15:29:34) Meeting ended at 15:44:40 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jcapitao[m] (40) * lorbus (22) * amoralej (8) * centguard (7) * spotz_ (5) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

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