I'd like to continue moving some git projects/repositories from
https://git.centos.org to https://gitlab.com/CentOS (and eventually
through different under project, like Artwork/Promo/etc).
For unknown ones, I'd probably propose to just create corresponding
hierarchy and put that under archives, so something like
https://gitlab.com/CentOS/archives/git.centos.org/centos/<project_name>.
That means we can easily write RewriteRules/Redirect from old to new one
if that follows a pattern.
Here is the list of projects hosted under
https://git.centos.org/projects/centos/%2A , so I'd like to get opinions
about where to move these (and some were probably already "moved" by
some SIGs, who probably migrated silently to gitlab.com some time ago) :
* artwork-archive
* Artwork
* bld-seven
* board
* buildsys-macros
* c6-livemedia
* cbs-content-control
* cbs-tools
* centos-infra-docs
* centos-metadata
* centos-module-defaults
* centos.org
* centos-packager
* centos-torrents
* centpkg
* centpkg-minimal
* comps
* connect
* infra-playground
* kickstarts
* livemedia
* pungi-centos
* releng
* sig-guide
* storage-sig-docs
* stream-team-docs
* t_docker
* t_functional
at least I see that can eventually move under Promo SIG (like centos.org
website), and some others that some SIGs would like to pick up and
host/manage under their SIG umbrella under gitlab.com/CentOS
In lack of reaction to this mail, I intent to just massively import all
under archives, *but* also lock these down as archives (so way to to
commit/push nor open MR to these)
So if your SIG wants to take ownership of some specific git
repositories, that you use in your workflow, now is the time to say so.
PS: Main ticket for git.centos.org is
https://gitlab.com/CentOS/infra/tracker/-/work_items/1654 but for
different type of projects (like /rpms/* will clearly be a different
one), I'll create linked task to main one to reflect status
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
As proposed/announced/requested by the CentOS Board
(https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/thread/NFNC…)
projects are now encouraged to migrate to gitlab.com/CentOS namespace,
instead of using git.centos.org (pagure).
While we'll announce the git.centos.org migration to gitlab.com later
(for all the rpms/* projects), we (Infra team) thought that it would be
a good idea to move ourselves (and board will probably follow soon ...)
our own tracker from pagure.io to gitlab.com/CentOS/infra.
# What will happen
The current https://pagure.io/centos-infra/issues tracker will be
exported/imported in a new project under gitlab.com/CentOS/infra (to be
announced when migrated).
All metadata/history from open/closed tickets, and labels will be
imported (thanks to the work done by Akashdeep on
https://github.com/fedora-infra/pagure-exporter/ , the tool used to
migrate from pagure to gitlab !)
Worth knowing that only tickets and content will be migrated, but as we
can't impersonate users at gitlab.com sides, tickets will appear to be
created by our bot account used for the migration. You'll be able (and
we plan on closing open tickets on pagure.io with a link to new ticket
on gitlab.com side) to just "subscribe/watch" new ticket to follow
status updates.
For new tickets, normal workflow will resume as you'll be the real user
creating the ticket[s] (with your gitlab.com account, linked to your
ACO/FAS account - see
https://docs.centos.org/centos-sig-guide/auth/#linking-your-centos-account-…)
# When will that happen
Migration is scheduled for July 15th, around 1:00pm UTC
The way we'll proceed will be :
- create new tracker project on gitlab.com/CentOS/infra
- transfer tickets with metadata (that can take some time)
- close all open tickets with link to new ticket (same number !) on
gitlab.com
- set the issue tracker to "read only" on pagure.io/centos-infra
- update README.md on pagure.io with some explanations and link to
gitlab (in case people aren't following devel mailing list)
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Hi folks,
We're holding another CentOS Showcase on July 28. CentOS Showcase is
our half-day virtual conference series that we're trying to do three
times a year. The CFP is open until July 21. We'd love to hear what
you've been working on.
https://www.centos.org/events/showcase-2025-07/
All talks are short, just 20 minutes, including any time you want to
leave for Q+A. We run the event from 17:00 to about 21:00 UTC. This
time slot best accommodates NA Pacific to EU Central. Apologies to
folks outside that range. Round planets are hard.
CentOS Showcase is free, but we strongly recommend registering. It
helps us a lot with planning. The registration link is on the event
page.
Thanks,
Shaun
Hi everyone,
CentOS Stream 10 now has a working secure boot!
This shim-15.8-5.el10 build enabled it earlier this week:
https://kojihub.stream.centos.org/koji/buildinfo?buildID=79665
For that to work, the unsigned shim first had to go through a community
review: https://github.com/rhboot/shim-review/issues/454 and after that get
signed by Microsoft.
The signed shim is now available on the mirrors.
I'd like to thank Fabian Arrotin for pushing this through and testing,
Marta Lewandowska for helping with the review and organization, Nicolas
Frayer for all the packaging work, Peter Jones for handling the signing,
and Brian Stinson for submitting the initial review.
CentOS Stream 9 should have it in the following weeks as well.
Cheers,
Adam
--
Adam Samalik
---------------------------
Principal Software Engineer
Red Hat
Over the last few days it seems like many of the RPM mirrors are desync'd for some subsets of the repo. Many of my builds do `dnf builddep` and the `appstream|baseos-source` repos seem to have an especially high desync rate.
$ podman run --rm -ti quay.io/centos/centos:stream10 bash
# dnf --disablerepo='*' --enablerepo=appstream-source update
CentOS Stream 10 - AppStream - Source 682 B/s | 3.0 kB 00:04
Errors during downloading metadata for repository 'appstream-source':
- Downloading successful, but checksum doesn't match. Calculated: 09dc868bd85b58f482d2645fb823e5f7e835d219c515a72e8bca228dbe402387c72cab68273022a1ec9d76160ad513397549a4e336635ee1e22740ed3ec78ee0(sha512) Expected: 43068ade5bff34f3c74a58bc33e0e63d44de48586ba3ead6ee6b44ea7a506f069c5227a34ab64396b915432495c069f193586d2842208387758d54edb033a2e0(sha512)
- Downloading successful, but checksum doesn't match. Calculated: 4fc5a6c4d27c34d0ca881b0ae0332448bc06917fd206bc1f1aab6fc9159c84598528e9c398a338fb67819488c6883239f48b3a37ba95ad887d51857aa396849d(sha512) Expected: 43068ade5bff34f3c74a58bc33e0e63d44de48586ba3ead6ee6b44ea7a506f069c5227a34ab64396b915432495c069f193586d2842208387758d54edb033a2e0(sha512)
Error: Failed to download metadata for repo 'appstream-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Looking at the logs, mirrors like osuosl.org, ftpmirror.your.org, centos-stream-distro.1gservers.com are all out of sync, but are in the mirror list rotation.
Hi *
I am having difficulties compiling locally centos-stream-10 kernel (https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10) on Fedora 42 x86 machine.
I am trying to compile for x86 and aarch64 architectures.
I am able to build on RHEL 10,without any difficulties.
I am using :
make dist-rpms
make dist-all-rpms
make dist-cross-aarch64-rpms
Has anyone had a success in such a compilation?It seems to be impossible without making fixes to the build process