devel July 2025

devel@lists.centos.org

14 participants
14 discussions

PostgreSQL ?
by lejeczek 09 Oct '25

09 Oct '25

Hi guys. Do we have 'postgresql-server' in some default repo? I see there is a module but it seems to be "empty". If not what method do you recommend for pgsql? many thanks, L.

3 5

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

git.centos.org to gitlab migration : be ready ! [please read]
by Fabian Arrotin 30 Jul '25

30 Jul '25

If you follow this list, you know that we started a thread about migrating git.centos.org (pagure) to gitlab.com/CentOS We are now to a point where we can easily migrate everything, and have a parallel server hosting the tarballs/sources (aka lookaside cache server) I'd like to target second half of August for real migration and so shutting down git.centos.org (basically when I'll come back from summer holidays) While already migrated projects are already aware of it (and reflected new url in their workflow), I'd just like to ensure that SIGs still relying on git.centos.org for rpm packaging *should* migrate this before the migration. Reminder : all /rpms/* projects hosted on git.centos.org will be (already mirrored) just available on https://gitlab.com/CentOS/archives/git.centos.org/rpms/ , but with the archived bit turned on, so without any way to open MR or push directly to any branch. Current situation was that based on SIG membership/group, people could push to specific branches on projects under /rpms/* So be sure to create yourself new projects under your SIG group (if you don't have one -yet- , create an infra ticket to ask for one) under https://gitlab.com/CentOS/ and migrate what you need to your own projects (see for example Hyperscale, Virt, Storage SIGs, etc , already using gitlab) I'd don't have a list of all SIGs still using git.centos.org but as one example, I know that Cloud SIG (for openstack) was still using it and I don't see any rpms under https://gitlab.com/CentOS/cloud/rpms .. So be ready before the real migration and so before we'll shutdown git.centos.org PS : of course we'll just migrate everything to gitlab, so you can still pull/clone from there and then push to your own new project there, and we'll also keep full backup of git.centos.org (pagure) so nothing will be lost -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 0

CS10 "latest" qcow2 image missing, will return soon
by Troy Dawson 25 Jul '25

25 Jul '25

When this weeks CentOS Stream 10 compose was pushed out, the CentOS-Stream-GenericCloud-10-latest.x86_64.qcow2 image disappeared. Some people who investigated noticed that it was just the image, but not the MD5 and SHA sums. Q: Is this disappearance permanent? A: No. There was a bug. We will get the images back in our next weekly compose / release. Q: Why did the original one go away? Koji was updated, and three of our images started failing. They would build correctly, but koji would fail tagging them. This was OK for a while because "latest" just kept pointing to the latest successful image. Eventually the image got too old and our cleanup script removed it. Details can be found in this bug/issue: https://issues.redhat.com/browse/CS-2959 Q: When will the original one come back? They should come back on Monday's (July 28) compose and release. Q: What is the difference between the two x86_64 qcow2 images? The original (without the extra x86_64) is our original Bios only image. The one with the extra x86_64 boots using EFI We, the CentOS Stream team, apologize for the inconvenience that has caused.

1 0

Curiosity: Does Red Hat freeze the major-version branch?
by Gordon Messmer 25 Jul '25

25 Jul '25

Does the RHEL major branch have code freeze periods leading up to minor-release branching, or does branching simply happen early enough to treat the period between branch and release as a freeze? Or is there some other process that's less obvious?

2 1

CentOS Projects git repositories to move from git.centos.org to gitlab (a thread/please participate)
by Fabian Arrotin 24 Jul '25

24 Jul '25

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]

6 7

Discussion: Thoughts of new sig - CentOS Rollup
by Troy Dawson 23 Jul '25

23 Jul '25

I have heard several times from different people and SIGs that they would like a Rollup (Snapshot) of their SIG's stuff, along with the corresponding CentOS Stream and EPEL release. So, I'd like to start a discussion about the possibility of creating a SIG that would rollup all of the "stuff" (images, repos, packages, documentation, etc...) from all the CentOS SIGs, along with the the corresponding CentOS Stream and EPEL releases, once a quarter. We could put all of that in AWS space, and leave it there for a period of time. Some people I talked to said a year, some said for the remainder of the corresponding Stream life. There are several details that would need to be worked out, but I'm sending this email out to start the discussion about the feasibility and desire for such a SIG. Troy

2 2

CentOS Alt Images July 2025 Update
by Troy Dawson 17 Jul '25

17 Jul '25

The CentOS Alternative Images SIG has released their July 2025 update of images. The easiest way to get the updates is from our download webpage. https://www.centos.org/altimages/ Our biggest news is our updated WSL image. [1] Utilizing the latest WSL features, it is now very easy to install and get running. It is very literally a click and run solution now. We also updated out WSL installation page to reflect the new way of installing. [2] Beyond WSL, we have the usual updates that happen in CentOS Stream and EPEL. My personal favorite is that KDE on CentOS Stream 10 is now at version 6.4.2 If you don't want to go to our download page, here is where the various released images are. CentOS Stream 9: Live Images: https://mirror.stream.centos.org/SIGs/9-stream/altimages/images/live/x86_64/ https://mirror.stream.centos.org/SIGs/9-stream/altimages/images/live/aarch6… WSL Images: https://mirror.stream.centos.org/SIGs/9-stream/altimages/images/wsl/x86_64/ https://mirror.stream.centos.org/SIGs/9-stream/altimages/images/wsl/aarch64/ CentOS Stream 10: Live Images: https://mirror.stream.centos.org/SIGs/10-stream/altimages/images/live/x86_6… https://mirror.stream.centos.org/SIGs/10-stream/altimages/images/live/aarch… WSL Images: https://mirror.stream.centos.org/SIGs/10-stream/altimages/images/wsl/x86_64/ https://mirror.stream.centos.org/SIGs/10-stream/altimages/images/wsl/aarch6… We hope these images are useful to you. Alternative Images SIG [1] - Windows Subsystem for Linux (WSL) lets developers install and use a Linux distribution on Windows 10 or 11 without the overhead of a traditional virtual machine or dualboot setup. [2] - https://sigs.centos.org/altimages/wsl-images/

1 0

CentOS Infra tracker moving to Gitlab.com (please read)
by Fabian Arrotin 15 Jul '25

15 Jul '25

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]

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel July 2025