On 6/21/23 22:26, Gerald Henriksen wrote:
On Wed, 21 Jun 2023 21:06:40 +0100, you wrote:
Hi all,
Obviously many will have seen:
https://www.redhat.com/en/blog/furthering-evolution-centos-stream
and see, where EL (contributors like you of fedora/EPEL) have been knocked down:
https://bugzilla.redhat.com/show_bug.cgi?id=2215299
Let us face it our efforts with the Fedora project are not valued and it is a means nothing to the
new corporate IBM/Red Hat enterprise systems that we have to struggle to get access to srpms, to
make a community. What is community now to Red Hat?
My interpretation of the blog post, combined with recent actions
towards Fedora by Red Hat, is that Red Hat now views CentOS Stream as
the new "Fedora" for basing future versions of RHEL.
CentOS Stream topic is still confusing to many, thus I am going to use
the opportunity to mention two talks which I have provided at FOSDEM
2022 [1] and Open Infra Summit 22 [2] on the matter:
[1]
https://archive.fosdem.org/2022/schedule/event/centos_stream_stable_and_continuous/
[2]
https://discussion.fedoraproject.org/t/centos-stream-talk-at-openinfra-summit/40045/1
I also have a leaflet version [3] for those who prefer text.
[3] https://gitlab.com/bookwar/centos-leaflet/-/blob/main/centos-leaflet.pdf
----
Part of the confusion comes from the fact that people refer to upstream
development, Fedora development and CentOS/RHEL development using just
one word - development, while in reality these are three very different
activities, and all of them are required for the RHEL existence.
You can not replace upstream with RHEL development, you would have to
create new upstream for that. The same way you can not replace Fedora
development with RHEL/CentOS Stream development, it is a very different
thing and you would need to create it.
The second part comes from thinking of CentOS Stream as something in the
middle, between Fedora and RHEL. CentOS Stream is a rebuild of RHEL. It
is a rebuild of exactly RHEL sources taken from the same git tree as
RHEL builds take those sources. It is not a middle - it is RHEL.
----
So let's look at the sources story closely:
1) How it was before Stream:
there was an internal git tree. RHEL Engineers would commit RHEL changes
to that tree, changes would be built into RPM and SRPM. On release, RPM
and SRPM would be published for RHEL customers. On that release date
CentOS engineers would take the published SRPM, unpack it, and upload
the content to the centos git repo.
So CentOS git essentially contained the "exploded SRPMS". No git history
was available.
CentOS Engineer then would go to CentOS Koji and build the CentOS
package from that exploded source
2) How it was after Stream but Before the announcement:
There is a public git tree on GitLab.com [4] RHEL Engineers commit
changes to it. RHEL engineers build CentOS package in public Stream Koji
_and_ RHEL package internally from the same git commit. CentOS package
becomes public, RHEL package goes into RHEL repository.
[4] https://gitlab.com/redhat/centos-stream/rpms/glibc
As soon as RHEL package is released, the SRPM for a RHEL package becomes
available. CentOS Engineer would take that SRPM, unpack it and upload
the content to CentOS Git.
But the CentOS package for that RHEL SRPM has already been built weeks ago.
So now we have CentOS package, which is available for weeks in Koji, its
sources available for the same two weeks on GitLab [4], with proper git
history, MR history, and test history. And then a there is a second set
of CentOS sources (exploded rpms, no history), which are not really
CentOS sources anymore, because CentOS doesn't build anything from them.
3) So what happened?
- CentOS Engineers will not be producing that git repo of exploded SRPMs
anymore because there is no need for them in CentOS project.
- Red Hat recommends to take RHEL sources from CentOS Stream
repositories because that is the actual source from which RHEL packages
are built by RHEL Engineers.
Can you still get access to SRPMs and create exploded sources repo -
Yes. But there is no practical reason for Red Hat or for CentOS Project
to maintain such a service.
There is no change in Fedora or with anything related to Fedora.
--
Aleksandra Fedorova,
member of Fedora Council
RHEL/CentOS Strem CI Engineer
bookwar on Matrix
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
