Hi all,
One thing we realized this morning after the cbs.centos.org migration to
8-stream is that because kojid builders are now running also 8-stream ,
and so with dnf/mock/yum able to understand modularity, we had a
specific issue for SIG eventually building/tagging pkg that *also* exist
as module/stream in AppStream repository.
With default setup, when "merging" repositories (so BaseOS/AppStream and
your SIG tag), it would just filter out your built pkg
Example: package python3-pytest-4.6.9-1.el8.noarch is filtered out by
modular filtering
This pkg also exist in AppStream and so koji would try to use it from
default enabled module.
So we have decided to just turn the module_hotfixes = 1 boolean for
yum/dnf for all el8-build/el8s-build tags, so that it would just work as
before. With that option turned on, that still allows koji to consume
pkgs from SIG tags.
So in case you *don't* want cbs.centos.org to do that for your SIG tags,
just let us know and we'll revert that for your tags (we decided to make
it that an "opt-out" thing rather than "opt-in" as currently it just
work as before the migration to 8-stream/koji 1.23)
Kind Regards,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab
Due to a major upgrade, we'll have to take the cbs/koji setup into
maintenance window.
We're basically upgrading from koji 1.19 running on CentOS 7 to koji
1.23 running on CentOS 8-stream, meaning a parallel reinstallation.
Migration is scheduled for """"Tuesday May 4th, 6:00 am UTC time"""".
You can convert to local time with `date -d '2021-05-04 06:00 UTC' `
The expected "downtime" is estimated to ~60 minutes , time needed to
- backup/restore last postgresql dump ,
- apply DB schema upgrade[s]
- verify service and switch public IP to new kojihub.
We've already taken some kojid builders instance down (and reinstalled
with 8-stream already) and these will be the first ones to be attached
back to kojihub, and so letting you, SIG members, be able to submit
builds again asap.
The remaining kojid nodes will then be reinstalled with 8-stream too,
and enabled back normally on the same day, to be back at "full st[r]eam" :)
Thanks for your comprehending and patience.
on behalf of the Infra team,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab
I would like permission to use this graphic in a lightning talk
describing why I see CentOS Stream as an improvement over CentOS.
However, I don't see licensing information available for the graphic.
Who can I contact to request that permission?
https://access.redhat.com/sites/default/files/images/rhel_8_life_cycle_8_06…
Hi, folks.
Well, this is embarrassing.
Due to a mixup in the mailing list moderation queue, we have not
received any of your board of director nominations (and at least a few
of you have mentioned that you sent one!) and we have to ask you to
submit them again.
This time, we're going to do this via a Google Form, and hopefully avoid
the problem that we had last time. That form is here:
https://forms.gle/U777HHDTkKgkg6Sa6
As a reminder, if you're considering nominating someone, have a look at
the requirements/recommendations document, at
https://www.centos.org/about/governance/director-requirements/ , where
we discuss what's involved in being a director, and who's eligible.
Thanks!
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