Hi Folks,
There’s been a lot of CentOS Stream 9 activity over the past few weeks that I’d like to share with you. First, if you haven’t noticed already, Stream 9 package sources are publicly available in GitLab: https://gitlab.com/redhat/centos-stream/rpms
Second, we’ve been leading up to a very important end-of-April milestone. You can now watch package build activity in the Stream 9 build system: https://kojihub.stream.centos.org
We started using these sources in the middle of March to complete our bootstrap round. That was followed almost immediately by a mass rebuild on April 12th to set the architecture baselines to POWER 9 and Z14 for the ppc64le and s390x architectures respectively.
If you find your favorite package in GitLab, you can visit the ‘Merge Requests’ tab to see how the Fork/Merge Request/Build workflow works. RHEL maintainers have been using this workflow for a few weeks now as part of regular development. We’ll provide more posts this week to explain how to use the same workflow, and work with maintainers who can evaluate your changes. If your changes are merged into CentOS Stream they can directly affect RHEL 9.
## What you can do now - Sign up for a gitlab.com account: https://gitlab.com/users/sign_up - On Fedora install centpkg-0.6.3-1 from the updates/updates-testing repo - On CentOS Stream 8 install centpkg-0.6.3-1 from the epel/epel-testing repo - Pull package sources from gitlab.com - `centpkg clone -b c9s <pkgname>` gives you a dist-git checkout from gitlab - `centpkg sources` from your checkout pulls source tarballs from the lookaside cache - Download and inspect artifacts and logs for builds already in the build system - Use `centpkg mockbuild` to try local builds of your own
## Plans for upcoming work - Updates to the contributor guide which contains important requirements and guidelines for how to submit changes to CentOS Stream via Merge Request
- Availability of the Composes (including install media, cloud images, container images)
- Announcements later this week describing upcoming milestones, new services, and when we expect to publish to the mirrors
Just a reminder: CentOS Stream 9 is still very early. We’re going to make lots of changes together, and we’re quickly bringing up services to support our long-term goal of having CentOS Stream 9 development continuously targeting the next minor release of RHEL. Currently these packages are subject to RHEL gating tests. We’ll be back with more about how that works, and what we’re doing to increase our ability to run tests directly in CentOS Stream too.
Cheers! --Brian
On ti, 27 huhti 2021, plageat@tut.by wrote:
Judging by builds from https://kojihub.stream.centos.org
is there any chance > 0 %, that el9 will not contain modularity?
It is up to individual teams to use or not use the modularity feature.
It will be available but some components already have already been de-modularized for various reasons. For example, IdM is de-modularized but will provide idm:client and idm:DL1 module streams that will have the same module stream profiles as before and will ship no components, only the profiles.
On Tue, Apr 27, 2021 at 5:05 AM Alexander Bokovoy abokovoy@redhat.com wrote:
On ti, 27 huhti 2021, plageat@tut.by wrote:
Judging by builds from https://kojihub.stream.centos.org
is there any chance > 0 %, that el9 will not contain modularity?
RHEL 9/CentOS Stream 9 will contain modules. We expect the first module to be added in the coming weeks.
It is up to individual teams to use or not use the modularity feature.
It will be available but some components already have already been de-modularized for various reasons. For example, IdM is de-modularized but will provide idm:client and idm:DL1 module streams that will have the same module stream profiles as before and will ship no components, only the profiles.
Generally speaking, many of the default streams in RHEL 8 will be non-modular content in RHEL 9/CentOS Stream 9. As newer versions are added, they may show up as parallel available module streams.
josh
On Wed, 28 Apr 2021 at 05:03, plageat@tut.by wrote:
OK, in that case, is there any chance to get API for downloading all srpms associated with some module stream? For, example:
$ centpkg clone-all -b c9s-stream-5.32 --module perl $ centpkg sources --modular
We've been struggling with this since 8.0, and I very hope is somehow feasible at least in EL9.
It would be like a dream feature. Like god blessing. Like 1 million winning in the lottery.
Please, Josh, please Brian, hear me! :-)
That isn't a little ask. You need some amount of code written to do that in different steps. It needs to be able to download the module, parse the yaml to see all the src.rpms, clone all of those, download side source for each package, build the src.rpm for that module.
On Wed, Apr 28, 2021 at 7:43 AM plageat@tut.by wrote:
Of course, I know. This is exactly what I do ATM, but the solution is quite "dirty" and, sometimes, inaccurate. In other hand, the official support would be nice step forward
It's an interesting idea. Could you file an RFE against centpkg for this so it doesn't get lost?
josh
That isn't a little ask. You need some amount of code written to do that in different steps. It needs to be able to download the module, parse the yaml to see all the src.rpms, clone all of those, download side source for each package, build the src.rpm for that module.
-- Stephen J Smoogen.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Apr 28, 2021 at 8:04 AM plageat@tut.by wrote:
Thanks for replying. The only way I know is submit a BUG in https://bugzilla.redhat.com/ for CentOS Stream/rhel9, but it seems there is no component named 'centpkg' yet available
"centpkg" is maintained in Fedora and EPEL, so file the bug there:
* Fedora: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=centp... * EPEL: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&componen...
The best place would be to open an issue on the centpkg development repo.
https://git.centos.org/centos/centpkg/issues
On Wed, Apr 28, 2021 at 7:05 AM plageat@tut.by wrote:
Thanks for replying. The only way I know is submit a BUG in https://bugzilla.redhat.com/ for CentOS Stream/rhel9, but it seems there is no component named 'centpkg' yet available
28.04.2021, 14:47, "Josh Boyer" jwboyer@redhat.com:
It's an interesting idea. Could you file an RFE against centpkg for this so it doesn't get lost?
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Tue, Apr 27, 2021, at 04:24, plageat@tut.by mailto:plageat%40tut.by wrote:
It seems, that you are using your internal RH links in public gitlab repo, well... $ uname -a Linux localhost.localdomain 5.11.14-200.fc33.x86_64 #1 SMP Wed Apr 14 15:25:53 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ centpkg clone --anonymous -b c9s gcc Cloning into 'gcc'... warning: redirecting to https://gitlab.com/redhat/centos-stream/rpms/gcc.git/ remote: Enumerating objects: 181, done. remote: Counting objects: 100% (181/181), done. remote: Compressing objects: 100% (94/94), done. remote: Total 181 (delta 96), reused 155 (delta 81), pack-reused 0 Receiving objects: 100% (181/181), 127.24 KiB | 259.00 KiB/s, done. Resolving deltas: 100% (96/96), done. $ cd gcc $ centpkg sources Downloading gcc-11.0.1-20210324.tar.xz Could not execute sources: (6, 'Could not resolve host: sources.stream.rdu2.redhat.com')
26.04.2021, 21:32, "Brian Stinson" bstinson@redhat.com:
- Pull package sources from gitlab.com
- `centpkg clone -b c9s <pkgname>` gives you a dist-git checkout from gitlab
- `centpkg sources` from your checkout pulls source tarballs from
the lookaside cache
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel%40centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Which version of centpkg do you have? We updated 0.6.3-1 (possibly still in updates-testing) to include publicly accessible URLs.
--Brian
On Tue, 2021-04-27 at 10:12 -0500, Brian Stinson wrote:
Which version of centpkg do you have? We updated 0.6.3-1 (possibly still in updates-testing) to include publicly accessible URLs.
The 0.6.3-1 version presents the issue still, however the 0.6.4 version (presently in updates-testing) works as expected:
]$ sudo dnf --enablerepo updates-testing update centpkg centpkg-sig
]$ centpkg clone -b c9s centos-logos Cloning into 'centos-logos'... client_global_hostkeys_private_confirm: server gave bad signature for RSA key 0 remote: Enumerating objects: 6, done. remote: Counting objects: 100% (6/6), done. remote: Compressing objects: 100% (5/5), done. remote: Total 6 (delta 0), reused 0 (delta 0), pack-reused 0 Receiving objects: 100% (6/6), 7.32 KiB | 7.32 MiB/s, done.
]$ cd centos-logos/
]$ centpkg sources Downloading centos-logos-85.1.tar.xz ####################################################################### # 100.0%
]$ ll total 48940 -rw-rw-r--. 1 al al 50079044 Mar 12 14:32 centos-logos-85.1.tar.xz -rw-rw-r--. 1 al al 25286 May 1 10:04 centos-logos.spec -rw-rw-r--. 1 al al 165 May 1 10:04 sources
Amazing work.
Thanks.
On Mon, Apr 26, 2021 at 2:32 PM Brian Stinson bstinson@redhat.com wrote:
Hi Folks,
There’s been a lot of CentOS Stream 9 activity over the past few weeks that I’d like to share with you. First, if you haven’t noticed already, Stream 9 package sources are publicly available in GitLab: https://gitlab.com/redhat/centos-stream/rpms
Second, we’ve been leading up to a very important end-of-April milestone. You can now watch package build activity in the Stream 9 build system: https://kojihub.stream.centos.org
This is awesome. :)
My only real (minor) gripe is that the URL isn't koji.stream.centos.org, because my automation for poking all the different Koji instances I interact with have made that assumption. Is there any chance we could get the URL changed? That would mimic koji.fp.o and koji.mbox.c.o too.
But otherwise, this is absolutely fantastic and I'm really happy to see this exist now!
On Wed, 2021-04-28 at 14:48 +0300, plageat@tut.by wrote:
I am curious, is there any way to bootstrap some chroot with all stuff built for c9s atm? I am trying with something like in my repo:
baseurl=https://kojihub.stream.centos.org/kojifiles/repos/c9s-build/1696/x86_64/
and getting: (101/274): libgomp-11.0.1-0.3.1.el9.x86_64.rpm 307 kB/s | 271 kB 00:00 (102/274): libgpg-error-1.42-3.el9.x86_64.rpm 250 kB/s | 215 kB 00:00
[MIRROR] libkcapi-1.2.0-3.el9.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://download.eng.bos.redhat.com/brewroot/repos/rhel-9.0.0-beta-build/late... [Could not resolve host: download.eng.bos.redhat.com]
I reported this earlier today in #centos-stream to Brian Stinson as well. There's a small subset of packages that's not currently downloadable: https://paste.centos.org/view/0be5b45b
Luckily, none of those are terribly essential. I was able to get something working in mock with the attached config. Goes without saying, this is a horrible hack, and mostly just for playing around at this stage.
Cheers Davide
On Wed, Apr 28, 2021 at 02:48:12PM +0300, plageat@tut.by wrote:
Hi. Can you please adjust your mail client configuration to either post plain text to this list or include a text/plain (or similar) MIME section as required by RFC?
Thank you,
John
On Wed, Apr 28, 2021 at 02:48:12PM +0300, plageat@tut.by wrote:
Hi. Can you please adjust your mail client configuration to either post plain text to this list or include a text/plain (or similar) MIME section as required by RFC?
Thank you,
John
-- Don't mistake my kindness for weakness. I am kind to everyone, but when someone is unkind to me, weak is not what you are going to remember about me.
-- Alphonse Gabriel Capone (1899-1947), American gangster _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
test
I am so sorry for spamming. Currently mail.yandex.ru completely changed to use a new web interface with absolutely broken text/plain. I'd better stop mailing at all with this account :-(
On Wed, Apr 28, 2021 at 02:48:12PM +0300, plageat@tut.by wrote:
Hi. Can you please adjust your mail client configuration to either post plain text to this list or include a text/plain (or similar) MIME section as required by RFC?
test
Hi,
I have been following the publicly available progress on CentOS Stream 9 for some time now. So far it has been really interesting to get more information about the process of creating the next major RHEL. Indeed it also helps to better understand some design decision of the final product.
Lately I have been looking at the available composes at [1] and have one question about these:
So far there is a repository/compose/folder/whatever-you-name-it "Everything", which (as the name suggests) simply contains all built packages including all subpackages. However, it seems (see [2]) that this will probably not be available in future composes. Is this correct?
I'm asking cause the "Everything" variant would obviously solve the missing subpackages issue we had to (and still have to) deal with for CentOS Stream/Linux 8.
In case I got it right: What is the plan to solve the missing subpackages issue for CentOS Stream 9?
I wanted to ask here to get a little more insight before I start filing bugs to try getting missing subpackages back into CRB/PowerTools. Just looking for a few minutes I immediately found a subpackages that was missing in RHEL 8.0 and people successfully argued to get into CRB/PowerTools later. In RHEL 9.0 it is now missing again :(
Thanks
Peter
[1] https://composes.stream.centos.org/test/ [2] https://gitlab.com/redhat/centos-stream/release-engineering/pungi-centos/-/m...
On Sat, May 1, 2021 at 12:58 PM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
Hi,
I have been following the publicly available progress on CentOS Stream 9 for some time now. So far it has been really interesting to get more information about the process of creating the next major RHEL. Indeed it also helps to better understand some design decision of the final product.
Lately I have been looking at the available composes at [1] and have one question about these:
So far there is a repository/compose/folder/whatever-you-name-it "Everything", which (as the name suggests) simply contains all built packages including all subpackages. However, it seems (see [2]) that this will probably not be available in future composes. Is this correct?
Yes.
I'm asking cause the "Everything" variant would obviously solve the missing subpackages issue we had to (and still have to) deal with for CentOS Stream/Linux 8.
In case I got it right: What is the plan to solve the missing subpackages issue for CentOS Stream 9?
We're still working on this. As a start, all of the content is publicly accessible in koji.
I wanted to ask here to get a little more insight before I start filing bugs to try getting missing subpackages back into CRB/PowerTools. Just looking for a few minutes I immediately found a subpackages that was missing in RHEL 8.0 and people successfully argued to get into CRB/PowerTools later. In RHEL 9.0 it is now missing again :(
We'd definitely like to avoid regressions. If you notice issues like that, please report them in bugzilla against the distribution component and we'll try to clean them up unless the package is slated for removal entirely. A major release is quite an undertaking and the rare opportunity for large amounts of change which can cause issues like that, so help is certainly appreciated.
josh
-
Alain Reguera Delgado -
Alexander Bokovoy -
Brian Stinson -
Brian Stinson -
Carl George -
Davide Cavalca -
John R. Dennison -
Josh Boyer -
Neal Gompa -
Peter Georg -
plageat＠tut.by -
Stephen John Smoogen