devel

devel@lists.centos.org

4618 discussions

C8 EOL DRAFT announcement
by Rich Bowen 19 Jul '21

19 Jul '21

Hi, folks, following up from the discussion over the last two weeks about the CentOS 8 EOL announcement, and specific details of that plan, I wanted to share with you this DRAFT announcement, for commentary. It's worth noting that certain aspects of this draft are not negotiable. Specifically: * We will not ship further updates after the EOL date * We will not automatically migrate CentOS Linux 8 users to CentOS Stream 8 However, other suggestions, clarifications, and edits are welcome, with the goal of removing any ambiguity or misunderstanding that might occur from a poorly worded message. ------- DRAFT BEGINS: CentOS 8 EOL messaging CentOS Linux 8 will reach End Of Life (EOL) on December 31st, 2021. Here’s what that means. In line with the EOL of previous releases, we will NOT be automatically migrating anyone to the next version (which is CentOS Stream 8 in this case). We will be shipping a rebuild of Red Hat Enterprise Linux (RHEL) 8.5 once it is released, even if that means that this is released slightly after the EOL date. The release of a RHEL point release is often accompanied, immediately afterwards, by a set of zero-day updates. We will be providing this content as part of the final CentOS Linux 8 release. There will, however, be no more updates to the CentOS Linux 8 content after that time. Additionally, with this deadline falling during a time when many of our team, as well as many of our users, will be out of the office, we intend to bend the usual EOL process by keeping this content available until January 31st. At that time, or in the event of a serious security bug in this time window (Defined as anything with a VCSS v3 score of 9 or greater), this content will be removed from our mirrors, and moved to vault.centos.org where it will be archived permanently, since we will not be able to provide updates to the content after the EOL date. DRAFT ENDS ----------------- We are considering shipping a dnf plugin that gives informational messages about the CL8 EOL, and explain the process for moving to CS8, for users who are not yet aware of the change. There is some concern around this plan due to anecdotal evidence that some people automate the capture and parsing of dnf output, and this might break that. Comments welcome on this topic, but of course if you’re reading this, you’re already aware of the EOL, making this a challenging issue to get feedback on. We welcome your comments on this proposal, and intend to publish this more widely after a reasonable comment period. Thanks!

1 0

RHEL for Research and Academia
by Mike McGrath 19 Jul '21

19 Jul '21

Hi everyone, I had sent a few other updates to the list regarding free RHEL programs and so I thought I would make sure to link to this one announced today. For those of you in academic or research institutions, this is the announcement you've been looking for. Generally, this program has been in place for some time but you had to know who to reach out to for discussion. For those who are interested, give it a read. https://www.redhat.com/en/blog/expanding-red-hat-enterprise-linux-choices-r… -- Mike McGrath Linux Engineering - Chicago Red Hat mmcgrath(a)redhat.com T: (312)-660-3547

4 4

ANN: Hyperscale (GNOME) Workstation snapshot 20210718 LiveDVD
by Neal Gompa 18 Jul '21

18 Jul '21

Hello all, As I announced a few weeks back[1], the CentOS Hyperscale SIG started producing an experimental Hyperscale Workstation Spin to showcase the technologies we're working on to the broader community. Today, I'm pleased to announce that we've made an updated image to address some issues present in the first release. Like before, the spin is currently available here: * ISO: https://ngompa.fedorapeople.org/centos/hyperscale/CS8-HS-WORK-LIVE-LATESTDE… * SHA512 checksum: https://ngompa.fedorapeople.org/centos/hyperscale/CS8-HS-WORK-LIVE-LATESTDE… The changes with this build (aside from updated packages): * The Anaconda installer icon and other branding is now correctly present and used. Thanks to Alain Reguera Delgado and Carl George for getting all this in place! * "dnf upgrade" works now, as we've refreshed our custom version of the RPM+DNF stack. * UDisks2 now has its Btrfs module installed out of the box. GNOME Disks, Cockpit, and others that use UDisks2 will now be able to properly detect and work with Btrfs (insomuch as the feature have been implemented in those tools). The other known issues from the initial announcement[1] are still present in this release. However, there is a new known issue: * Blivet is broken with MD devices with names that look like BIOS drive numbers, causing Anaconda to crash in the process. This is caused by the blivet rebase from 3.2.x to 3.4.0 without backporting the fix for this issue and is present in the CentOS Stream 8 software. Red Hat Bugzilla bug report (with patch): https://bugzilla.redhat.com/1983309 If you find any other issues, we would definitely love to hear about them! We have a dedicated issue tracker for Hyperscale spins where we would appreciate bugs to be reported: https://pagure.io/centos-sig-hyperscale/spin-bugs We hope you enjoy it as much as I enjoyed making this! Thanks and best regards, Neal (on behalf of the CentOS Hyperscale SIG) [1]: https://lists.centos.org/pipermail/centos-devel/2021-June/077079.html -- 真実はいつも一つ！/ Always, there's only one truth!

1 0

Documenting the CentOS Linux 8 EOL process
by Rich Bowen 16 Jul '21

16 Jul '21

As we get closer to the CentOS Linux 8 EOL, we're getting more and more questions about how the EOL is actually going to work. While there tends to be a great deal of "everybody just knows how it works" among the people actually on this list, we're getting attention from a much larger audience now, and they don't know. To that end, I want to make sure we have clear documentation, prominently displayed, that sets expectations as we get closer to that December 31 date, So ... as I understand, our process is basically: 1. Copy old data to vault.centos.org 2. Update web pages and links to say it is now on vault.centos.org 3. Turn off mirrorlist to that release name (aka all requests to CentOS-8 will 404) 4. Remove the data from the main mirrors with a file saying look at vault.centos.org 5. Mirrors pick all that up in 4-8 hours. Is there more to it than this? Will we do anything different this time because CL8 is a special case? Am I missing any steps, or have I misunderstood any of the steps? Is this already documented somewhere that I simply haven't found yet? Are there any changes to this process that we *want* to advocate for, given the special nature of this particular EOL? (No, I absolutely cannot promise anything, but I can ask.)

20 39

Dependent on PowerTools
by Mike Rochefort 16 Jul '21

16 Jul '21

Based on the office hour earlier this week, I spent some time performing scans of the PowerTools repo to see what packages from BaseOS, AppStream, and EPEL rely on it. The results of these scans can be found in a repo here: https://gitlab.com/omenos/crb-depends I was only able to do x86 based scans, and there will be some dupes of packages because i686 and x86_64 versions exist. Unfortunately this is a pretty basic check; I didn't differentiate between package types during cleanup, so there will be a lot of -devel packages showing up. Hopefully the data is accurate, I did this fairly late at night :) -- Mike Rochefort

2 4

Proper CentOS Stream value for ID_LIKE
by Mike Rochefort 15 Jul '21

15 Jul '21

When it comes to CentOS Stream, should the ID_LIKE parameter be changed to properly designate the upstream nature of CentOS in regards to RHEL? As of now, both Stream 8 and 9 are using the classic CentOS identifier of "rhel fedora". If the change of being upstream is strict enough, CentOS should be changed to "fedora", and RHEL should be altered to "centos fedora". However, I've got a feeling a lot of scripts and tooling may be looking to see if "rhel" is in the ID_LIKE parameter, which may end up preventing installations of software on Stream for limited reasons. I don't have any examples or numbers to back that up, just a hunch on how people use the os-release (and redhat/centos-release) file. Is this something that should be adjusted, or left as is for compatibility? -- Mike Rochefort

7 8

July board meeting, quick summary
by Rich Bowen 15 Jul '21

15 Jul '21

We had a *very* productive Board of Directors meeting yesterday. We'll be publishing the meeting minutes soon, but I wanted to summarize a couple of important items from yesterday's Board of Directors meeting. * The proposed Automotive SIG was approved: https://wiki.centos.org/SpecialInterestGroup/Automotive * We'll start planning for the third virtual Dojo of 2021 in the coming weeks. If you're interested in being part of that effort, please let me know, and subscribe to the centos-promo mailing lst. * Pursuant to the "Documenting the CentOS Linux 8 EOL process" thread on this list over the past week, the board came to agreement on several details around the CentOS 8 EOL in December, and we'll be drafting those in more detail over the coming days. * Pursuant to our commitment, in January, to continue being more transparent around the Board of Directors process, we'll be announcing a general public invite to future Board meetings. Details will be drafted over the coming days. * Over the past few months, I've been working on some updates to our governance docs, both to reflect the desire for greater transparency, as well as to promote a division between governance and technical direction. Over the next few weeks I'll be bringing drafts of those documents to this list for public commentary before we adopt them as our new guiding principles. So ... that's a *lot*, and some of it is going to take a while for us to get done. So, please do remind me if you don't see any progress on any of these items over the coming months. Many thanks to the Board of Directors for their hard work yesterday, and the work yet to come on the above items. --Rich, for Board of Directors

1 0

Community Platform Engineering Quarterly ~~Bragging Rights~~ Report Q2 2021
by Aoife Moloney 12 Jul '21

12 Jul '21

Hi Everyone, Below you will find a report of the work the Community Platform Engineering (CPE) team was involved in over the last three months. If you would like to view this in a 'toggle-able' view, I would suggest you visit this hackmd link https://hackmd.io/@Ap8CkTlpSfmjb44UGV-kWA/BJlrOsBpu ## Intro The Community Platform Engineering team is a group of people who work on infrastructure, release engineering, documentation, development and just about anything else you can think of that supports both the CentOS and Fedora projects. In an effort to try work even more effectively and improve on our work planning, we have been scheduling some of our work on a quarterly basis for the last 15-18 months. And its been working pretty well...once we got the hang of it :) This in a nutshell, just means that there is work the CPE team *will commit* to delivering every quarter that relates to both distros, while also still providing support to the projects infrastructure that come in as bugs, tickets, etc. Quarter two 2021, or April, May and June to give them their government names, has been a particularly good quarter for our team with a lot of work getting completed. Below is a breakdown of what our team delivered over the quarter per project. A note, that is a given but should never go without saying - is that the CPE team work in the Fedora and CentOS communities, and rely on community member feedback and discussion while working. Without your continued support and engagement with our team - be it when we are announcing something available and need input on how it works or an idea we have had and we want more discussion on a proposal before we start developing - the work we deliver at the end of each quarter would not be possible. So on behalf of the CPE team, thank you for your involvement in our quarterly work! This is as much your bragging rights as it is ours :) ## Fedora ### RPMautospec This project was originally prototyped early last year and presented at Nest with Fedora last August. It was a body of work that would relieve packagers from the burden of manually updating the Release field and %changelog section in RPM spec files. Some of the highlights of this project that the team delivered was: * Implemented a simplified release enumeration algorithm (from the discussion on the devel list and with FESCo) * Reflect flags to %autorelease in generated changelog entries * `fedpkg local`, `fedpkg mockbuild` (possibly `fedpkg srpm`) supports rpmautospec features, i.e. prepare the SRPM on the fly as Koji would do it before building. * Allows for uncommitted changes in local builds with fedpkg, i.e. bump the release number by one and generate a boilerplate “- uncommitted changes” RPM changelog entry. * Up-to-date and more complete documentation :) You can read more detailed information on this project from the repo https://pagure.io/docs/fedora-infra/rpmautospec/ and from the fedora mailing list https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ### Infrastructure & Release Engineering * F34 was released! https://fedoramagazine.org/announcing-fedora-34/ * New Status Page released! https://www.fedorastatus.org/ * Fedora Accounts got new features in staging that will be deployed to production soon: * Noggin (upstream project name) now supports Matrix IDs as well as IRC nicknames https://github.com/fedora-infra/noggin/pull/668 * Integrated the Spammish app into Noggin https://github.com/fedora-infra/noggin/pull/672 * FPCA status displayed on Noggin’s user page * https://fedoraloveskde.org site was deployed in staging and production * A *lot* of builder fixing and module cleanup * Behind-the-scenes work: * updates to services and applications, eg Bodhi * Upgraded machines to F34 * Fedocal now runnning on Openshift rather than VMs * Mass update/reboot to systems ## CentOS ### CentOS Stream 9 * Development composes are available https://composes.stream.centos.org/ * Container Images are available https://quay.io/repository/centos/centos?tag=stream9-development&tab=tags * Quickstart Contribution Guide available https://docs.centos.org/en-US/stream-contrib/quickstart/ * New SIG approved: Feature Request SIG for CentOS Stream https://lists.centos.org/pipermail/centos-devel/2021-April/076716.html * Centpkg development and release * CentOS Stream 9 build system is publicly viewable https://kojihub.stream.centos.org/koji/ * CentOS Stream 9 package sources are publicly available in GitLab https://gitlab.com/redhat/centos-stream/rpms ### CentOS Stream 8 * CentOS Stream 8 repository pipeline upgraded to merge new composes rather than replacing the previous content giving users the ability to `dnf downgrade` packages easily. More info https://lists.centos.org/pipermail/centos-devel/2021-May/076839.html * Centos8-stream buildroot available for missing -devel pkgs https://pagure.io/centos-infra/issue/316 ### CentOS Linux * CentOS Linux 8 had a new release derived from Red Hat Enterprise Linux 8.4 Source Code! Read more here https://lists.centos.org/pipermail/centos-devel/2021-June/077021.html ### Infrastructure & Release Engineering * EPEL repositories (plain rpms, no module content) can be enabled on demand on CBS for: * epel 7 (x86_64, ppc64le, aarch64) * epel 8 Everything (x86_64, ppc64le, aarch64) * epel Next 8 Everything (x86_64, ppc64le, aarch64) * Auth system switch completed in April bringing both CentOS and Fedora backend system under one stack and allowing contributors to both projects use one email for both projects! More info: https://lists.centos.org/pipermail/centos-devel/2021-April/076694.html * Deployed some instances for Artwork SIG to test centos visual theme for www/blog/mirror/mailman https://pagure.io/centos-infra/issue/366 This report is really only a snapshot of the volume of work the people on the Community Platform Engineering do, and also at a more high level overview, but even still there are *a lot* of very noteworthy successes in there that we are very proud of delivering this quarter, and we hope the communities we are part of and serve find value in the work we do too. Have a lovely weekend everyone, and I will be back with our plans for July, August and September with links to the projects work trackers and their respective goals that we are going to shoot for in Q3 very soon (like, next week) :) Kindest regards, Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Automotive SIG in CentOS
by Jeffrey Osier-Mixon 09 Jul '21

09 Jul '21

Hello all - there is now a proposed Automotive SIG in CentOS. It has been requested for consideration at next week's board meeting. https://wiki.centos.org/SpecialInterestGroup/Automotive The goal for this SIG is to enable code as well as active collaboration on ideas for automotive operating systems, with the eventual goal to create an in-vehicle automotive CentOS variant/spin. This SIG is open to all and we value active participation. If approved, we will host our first (virtual) meeting in August. best regards, Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

Two directories for 8.4.2105 and 8-stream in the centos mirrors
by Burn Alting 08 Jul '21

08 Jul '21

Recently, it appears that two directories for 8.4 and 8-stream are being distributed in the Centos mirrors. You can't see it if you view the mirrors, but if one downloads the filelist.gz file and grep for '^\.\/\.' one will see the directories, with content, .8.4.2105 and .8-stream. Can this be explained? An error or a new distribution concept?? If the latter, then this may have an impact on those who have off-line repos which they manually rebuild. Rgds

4 5

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