April 2021 - devel - lists.centos.org

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

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

repomd.xml.asc outdated?
by Leon Fauster 11 Jun '21

11 Jun '21

JFYI: LANG=C yum update --noplugins ... Error: Failed to download metadata for repo 'appstream': repomd.xml GPG signature verification error: Bad GPG signature http://mirror.centos.org/centos-8/8/AppStream/x86_64/os/repodata/ shows repomd.xml 2021-03-16 15:43 repomd.xml.asc 2021-03-03 00:29 -- Leon

5 6

RFC: Stream Kernel SIG Proposal
by redbaronbrowser 19 May '21

19 May '21

There are four main goals of this SIG: First, break down changes in the Stream version 4.18.0 kernel into individual patches. When possible, document the source the patch is from and the purpose of the patch. Moving forward also document which Stream kernel package revision introduced the patch. Second, build CentOS Plus kernel for Stream. Third, package newer LTS kernels during the LTS lifespan. These would be available as alternative kernels for Stream similar to the CentOS Plus kernel. Fourth, work on tools for better delivery of live security patches to be applied via kpatch. The reasoning for this SIG is to improve the openness of kernels available through Stream. Normally a distribution upstream would have access to which patch or commit each addition to the kernel belongs to. The patch name or commit comment would also give information as to the purpose of the patch. Stream's kernel reports to be 4.18.0 but uses a tar that is 110% the size of a true 4.18.0 tar. A breakdown of the additional 10% is not provided. Hence Stream's kernel still functions similar to a downstream rather than providing what is expected for a successful upstream project. This SIG would help close the kernel openness gap by documenting the changes. Stream users would then be in a better position to track down individual patches that cause regressions or bugs. This SIG would also help smooth the adoption of Stream for users that depend on CentOS Plus kernel features. Next, this SIG should help improve feedback to the LTS kernel developers. Tracking LTS kernel changes may also help with documenting some changes in the primary Stream kernel. Lastly, this SIG should help improve kernel security by promoting methods to enable kernel security updates even when a reboot of the system is not possible.

12 42

Making EPEL available in CBS for SIG builds
by Davide Cavalca 13 May '21

13 May '21

Hello, Fabian suggested to post about https://pagure.io/centos-infra/issue/306 so we can have a wider discussion around it. That ticket is specifically for the Hyperscale SIG, but I think this is something that could be generally useful. Within Hyperscale, we have a need to build a few packages that have dependencies coming from EPEL. While we could rebuild those dependencies within the SIG, that seems both wasteful and undesirable, as it would lead to needless deviation and potentially discourage folks from maintaining stuff in EPEL (where it has a chance to benefit the most people). So, our conclusion was that it would be great to just depend directly on EPEL and have it added to our build targets in CBS so we can build against it. One concern with doing this is that EPEL is kind of a moving target. This doesn't really apply to Hyperscale (as we track CentOS Stream), but it could be relevant for SIGs tracking CentOS Linux. Still, this would just be a non-default option for a SIG to add to their build tags, so I don't think this will be much of a problem in practice. From my chat with Fabian I understand this was raised in the past and there had been policy concerns around it. I'd love to get more context around this and see if we can get them addressed. Alternatively, if there are no concerns I'd be happy to entertain suggestions on how to actually do this :) Thanks! Cheers Davide

13 32

Missing build dependencies in CentOS 8 repositories
by František Šumšal 07 May '21

07 May '21

Hello! I'm not sure if this has been already answered somewhere on this list, but I'm curious why the CentOS 8 repositories are missing certain build dependencies (although they're present in RHEL's internal repositories). This makes rebuilding some of the CentOS 8 packages a bit painful. For example, let's try to rebuild util-linux: ``` $ podman run -it --rm centos:8 # rm -f /etc/yum.repos.d/CentOS-Linux-Media.repo # dnf -y install dnf-plugins-core ... # dnf --refresh --enablerepo \* -y builddep util-linux Failed to set locale, defaulting to C.UTF-8 CentOS Linux 8 - AppStream 10 kB/s | 4.3 kB 00:00 CentOS Linux 8 - BaseOS 23 kB/s | 3.9 kB 00:00 CentOS Linux 8 - ContinuousRelease 5.3 kB/s | 3.0 kB 00:00 CentOS Linux 8 - Debuginfo 1.6 MB/s | 27 MB 00:16 CentOS Linux 8 - Devel WARNING! FOR BUILDROOT USE ONLY! 18 kB/s | 13 kB 00:00 CentOS Linux 8 - Extras 8.2 kB/s | 1.5 kB 00:00 CentOS Linux 8 - FastTrack 933 B/s | 257 B 00:00 CentOS Linux 8 - HighAvailability 741 kB/s | 504 kB 00:00 CentOS Linux 8 - Plus 807 kB/s | 596 kB 00:00 CentOS Linux 8 - PowerTools 2.1 MB/s | 2.0 MB 00:00 CentOS Linux 8 - BaseOS - Source 120 kB/s | 384 kB 00:03 CentOS Linux 8 - AppStream - Source 271 kB/s | 991 kB 00:03 CentOS Linux 8 - Extras - Source 2.2 kB/s | 7.8 kB 00:03 CentOS Linux 8 - Plus - Source 1.7 kB/s | 5.0 kB 00:03 Package systemd-239-41.el8_3.x86_64 is already installed. No matching package to install: 'libuser-devel' Not all dependencies satisfied Error: Some packages could not be found. ``` Oh well, looks like we have to rebuild libuser as well: ``` # dnf --enablerepo \* -y builddep libuser Failed to set locale, defaulting to C.UTF-8 Last metadata expiration check: 0:02:14 ago on Tue Apr 13 10:36:39 2021. No matching package to install: 'openldap-servers' Not all dependencies satisfied Error: Some packages could not be found. ``` And apparently openldap, too. I noticed that Davide from FB already come across this issue and filed it in RHBZ[0], where it was confirmed that the dependency is indeed present only in the internal RHEL buildroot repository - and after a quick test they still are: # dnf --enablerepo rhel-buildroot search libuser-devel ... libuser-devel.i686 : Files needed for developing applications which use libuser libuser-devel.x86_64 : Files needed for developing applications which use libuser Is there any reason why they aren't shipped in some CentOS repository or was there any progress to make them available? Thank you! Frantisek [0] https://bugzilla.redhat.com/show_bug.cgi?id=1868430 -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B

15 23

[Infra] - Planned outage : cbs.centos.org
by Fabian Arrotin 04 May '21

04 May '21

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

1 1

CentOS Stream 9 Buildsystem is publicly viewable
by Brian Stinson 02 May '21

02 May '21

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

12 22

[ppc64le] Missing advancedvirt-common repo in stream
by Michael Turek 30 Apr '21

30 Apr '21

Hey everyone, Our ppc64le tripleo container build job [0] is broken by the lack of the advancedvirt-common repo outside of x86_64 [1] [2] There was a topic on the ML about this a few weeks ago [3] for what it's worth. Any ideas if we can get this fixed? Thanks! Mike <mjturek> [0] https://ci.centos.org/job/tripleo-upstream-containers-build-master-ppc64le/ [1] http://mirror.centos.org/centos/8-stream/virt/aarch64/ [2] http://mirror.centos.org/centos/8-stream/virt/ppc64le/ [3] https://lists.centos.org/pipermail/centos-devel/2021-April/076754.html

1 0

Re: [CentOS-devel] Documentation change propsal - "Contributing to CentOS Stream" web page
by Tomas Tomecek 30 Apr '21

30 Apr '21

Hi Michal, thanks for your thorough feedback! More comments inline. On Thu, Apr 29, 2021 at 5:14 PM Michal Schorm <mschorm(a)redhat.com> wrote: > > Hello, > > The "Contributing to CentOS Stream" webpage: > https://wiki.centos.org/Contribute/CentOSStream > is very confusing (at least to me) and lacks a lot of details. It's true the documentation is not finished yet - the CentOS Stream team is planning to provide comprehensive contributor's documentation, the wiki is really just an intro. > Here is my proposal to update / fix / enhance / clarify at least some > of the sections. > > -- > > (1) > Section 1 > Text: "You should always open a bugzilla first" > > The link leads to the most general selection in Bugzilla. > Even in the "All" category, there is no "CentOS" or "CentOS Stream" product. > Let's clarify that the product selected should be "Red Hat Enterprise > Linux *" and provide more accurate link: > https://bugzilla.redhat.com/enter_bug.cgi?classification=Red%20Hat Oh yeah, this is gonna be really handy! I just updated it to point to RHEL 8 and picked CentOS Stream as the version. > (2) > Section 1 > Text: "You should always open a bugzilla first" > > "Should" ? > The process *requires* package maintainers to have the ACKed BZ > referenced in the commit message, otherwise it will be impossible to > merge it. > I haven't heard of any other way, so this should be changed to " *MUST* ". The reason I wrote "should" there is that it may already be a bugzilla opened for the MR. I can see that Rich already changed it to "must" so let's keep it that way because that would incentivize potential contributors to discuss changes first, which is what we really want. > Also, the GitLab offers features such as "Issues" and so on. Will > those be globally disabled to discourage the contributors to file > tickets in the wrong place ? Yes, issues are disabled. Bugzilla is still the official tracker. > (3) > Section 1 > Text: "As with any open source projects, in the end it's up to > maintainers to decide which changes they want to accept and maintain, > so Red Hat maintainers can decline contributions for any reason." > > This sentence is heavily suggesting that only "Red Hat maintainers" > have the power to decide the fate of the contributions. Correct. > Does that mean that there can be no CentOS stream maintainer that is > not a RH employee at the same time ? > If yes, why don't make this clear and say it explicitly ? I'd say it's explicitly stated there already. Please suggest a better wording if you have one in your mind already. > Also if yes, why can't I login to CentOS project using Red Hat > credentials or SSO ? Because the CentOS identity provider is not utilizing Red Hat's SSO - I'd suggest starting a new thread for such a request because that's a big one. Though you can log in to GitLab via https://red.ht/GitLabSSO > If not, the sentence doesn't make much sense. > > (4) > Section 1 > Text: "It's also great to have it in Fedora Linux first as well." > > AFAIK, the OS you are mentioning is named "Fedora" or you can use > "Fedora Operating System" (to distinguish from the Fedora Project that > has a broader portfolio than just the OS). I think the "Fedora Linux" > is not correct. > Correct me if I'm wrong https://communityblog.fedoraproject.org/fedora-is-a-community-fedora-linux-… > Also, shouldn't be the "It's also great to have it in ..." statement > which is "nice-to-have" like, rather something more stressing the fact > that Fedora serves as an upstream for RHEL an in order to avoid future > regressions, it is very important to have the change accepted in the > Fedora first - if possible && if it makes sense. > The Red Hat package maintainers have to do it (the upstreaming of > relevant code to Fedora) anyway as a part of their job. > Also, how would it need to be a part of the upstream project and not > to be in Fedora at the same time ? I mean Fedora (at least Rawhide) > aims to provide the latest upstream versions possible. This is really hard because you have plenty of software that is being built and configured differently for all the distributions: kernel, qemu-kvm, *-release, subscription-manager... I'll reword that statement and will make it more clear. My assumption is there would be a dialogue between the maintainer and the contributor on how to handle specific contributions: I'd say it's perfectly reasonable to ask the contributor to propose the patch upstream or to Fedora Linux first. > (5) > Section 2 > Text: "If you want to contribute to CentOS Stream, you need to have an > account in CentOS FAS." > > Same issue as (3), same questions I ask. > > How comes it that I do not have the account and still I can contribute ? > The statement is most likely false. I agree this piece is slightly outdated because the sources are now placed on two locations: git.centos.org and gitlab.com/redhat/centos-stream I'll update it. > (6) > Section 3 > Text: "Once your account is set up, you can proceed to clone the > respective package repository locally." > > You can't clone the package repository locally without any account at all? > That would be weird for a public Git repos ... > > I'd reformulate the sentence such as "The next step you like to do is > to clone ... " > Also, the actual goal is not to clone the repo, but fork it, so let's > state that fact right away: > "The next step you like to do is to clone a package (project) from one > of the following repositories and fork it" That's a good point, I simplified the section. > (7) > Section 3 > Text: "The package repositories are right now located in two places:" > > Two places, but four list items? :) will update > (8) > Section 3.1 > Text: "You'll be able to see 3 types of branches: > > Not all projects have all 3 types of the branches. > It would be better to say something like "The repository will contain > some of these types of branches:'' > followed by a bullet point list " To me, it already says that. Would this wording work? "Branches in the repositories follow this naming pattern:" > (9) > Section 3.1 > > Also, what about showing some instructions on how to do it? > Do the contributors from the general public know about the "centpkg" > tool or should they work with bare "git" ? I'll mention centpkg though it doesn't have comprehensive documentation out there yet. > If they should know (or even are encouraged to use) "centpkg", provide > the damn instructions. I don't think such language is necessary. > Otherwise, describe if the forking in the web UI is the only way and > how to do it. > > (10) > Section 4.1 > > I bet this is a confusing section, at least for new contributors. > > 1/ Let's begin with the fact that you need the fork in the first place. > 2/ Inside of the fork, you should create a new branch - based on the > branch they want to contribute to, ideally (but necessarily? ... we > might make a "best practice" though) named "bz12345" referencing the > submitted BZ ticket for easy recognition > 3/ commit the changes. > note: each commit must contain an ACKed BZ ticket in order to be > able to be merged to the target branch. > note: there will be different ACK requirements for different > branches in the future (e.g. Y-stream v s Z-stream) > 4/ Push the branch to your fork > 5/ create MR > note: when using "centpkg" as I asked above, the MR URL will be > created during the push > > (11) > Section 4.2 > Text: "you need to execute %prep phase to see it." > > To "see it"? More like to "retrieve it from the cache". > > (12) > Section 4.4 > > What the hell is this about? > We should be talking about a dist-git layout & workflow in this > section, not a RPMbuild layout (which is completely irrelevant here). > There are no "SOURCES" and "SPECS" directories in dist-git. that is > completely wrong, the whole section. There is: https://git.centos.org/rpms/systemd/tree/c8s The main problem with this wiki page is that it was written as contributor's docs for CentOS Stream 8 while it was hosted on git.centos.org and it was never fully updated for Stream 9 and gitlab, hence the confusion. And also as you can see, Stream 8 and Stream 9 dist-git repos look differently. This is where I'm stopping my replies because your language is just way too offensive and I am not interested in this kind of discussion. > 1/ If you want to make just a packaging change, you *likely* only need > to modify just the SPECfile. > 2/ If you want to make justa patch change, you need to add the patch > AND modify the SPECfile too. > > At the end, you add all the modified files, commit them, add the BZ > ticket to the commit message and create MR. > > (13) > Section 4.5 > Text: "4.5. After a pull request is created" > > For a reason I don't know, some people call it "pull requests" (e.g. > in Fedora), some people "merge requests" (e.g. in GitLab). > Anyway, we are working with GitLab, so use it's naming. > > So: "4.5. After a merge request is created" > > Please find all 3 occurrences of the word "pull" on the page and fix them. > > (14) > Section 4.5 > Text: "When you submit a pull request for source-git, automation will > pick up the change and build it " > > Does it not work for the dist-git too? > Why ? > What about mentioning the scratch-build then? ... aww hell, we are > back to the "centpkg" again :) > > (15) > Section 4.5 > Text: "Once your change is accepted, it will be marked with the label > "accepted". Our automation will create a corresponding bugzilla with > the patch attached and then it’s up to the RHEL maintainer to pick it > up, commit and build internally so that it can land back into CentOS > Stream" > > This is most confusing. > > Why won't a maintainer merge it into CentOS first? > Why would he first apply it in the most downstream place? What about > the "upstream first" rule? > > How can a package maintainer mark the MR as "accepted"? > I haven't found such an option anywhere. > > "Our automation will create a corresponding bugzilla with the patch attached" > So ... another BZ ? This time to ... what product ? > Again see (1). > > I personally actually created a MR, but none BZ has been created: > https://gitlab.com/redhat/centos-stream/rpms/mariadb-connector-c/-/merge_re… > > "RHEL maintainer to pick it up, commit and build internally so that it > can land back into CentOS Stream" > That sentence suggests that the RHEL is the upstream for CentOS > stream, but at the same time we are pushing CentOS stream to be > upstream for RHEL. > Get this straight. > > BTW on a webpage: > https://wiki.centos.org/Contribute#CentOS_Stream > the re is a clear statement: > "CentOS Stream is a continuously delivered distribution which is > upstream to the next minor version of Red Hat Enterprise Linux" > > (16) > Section 5 > Text: "it needs to be reviewed and approved by the RHEL maintainer for > the particular component." > > Again - so only RH employees will be able to maintain ? > Why don't have a CentOS FAS access already created ? > Why would anyone else need a CentOS FAS ? > > "maintainer for the particular component" > Also, I believe this is a false statement too. > The current permissions AFAIK allow for any RH employee with the > GitLab account with the "devel" role over gitlab.com/redhat space to > merge the MR. > > (17) > Section 5 > Text: "We are making sure behind the scenes they see your patch." > > Who is making sure? > the RH employees ? > Who are "they" > *the same* RH employees ? :D > > (18) > Section 6 > > Might help to add instructions on how to do it. > > (101) > > Is there not a single documentarist as a part of the CentOS project > who would read through the webpages ? > > > -- > > Michal Schorm > Software Engineer > Core Services - Databases Team > Red Hat > > -- >

1 0

Missing dependencies while rebuilding OpenStack packages on centos8 stream
by Jose Castro Leon 30 Apr '21

30 Apr '21

Hi Cloud SIG, With every OpenStack release (and also with CentOS 8 stream), we have to rebuild some OpenStack packages to be installed at CERN. Those packages carry downstream patches for integration into our environment. While building those, we have observed that there are some packages that are required to build but are not provided in the testing repositories, for example openstack-macros In the past, we were using trunk.rdoproject.org/centos8-wallaby but it seems that those packages are not there. While looking into cbs.centos.org, I saw them on this tag cloud8s-openstack-wallaby-el8-build Would it be possible to have the dependencies available in the testing repo or to have access to that build repository, at least to build the main OpenStack components? Cheers Jose Castro Leon CERN Cloud Infrastructure Team

3 2

CentOS Stream 9 Compose Infrastructure is Available
by Brian Stinson 29 Apr '21

29 Apr '21

Hi again folks, I promised to provide updates as soon as we get new services wired up. I have another one for us. You can now visit https://composes.stream.centos.org/ This is the place where you'll find point-in-time test instances of yum repos, install media, cloud images (coming soon), and other artifacts. For right now we are generating composes for infrastructure purposes and to test out our tooling, but there are a couple of composes that do result in a working installer. Some notes: - RPMs and images are published unsigned in the Test composes right now. We'll be back with an update about signing when that comes online - For now composes are generated Ad-hoc, there is not an automatic schedule yet but that's something that we're working on now that we have the infrastructure ready - We'll soon be including documentation on the different compose types and what they mean, for now we are only generating 'Test' composes. They can be found here: https://composes.stream.centos.org/test - Because things are very early, we are not currently shipping .repo files, we recommend doing fresh installs for testing purposes. Updates from one compose to the next may work but are not tested - Test composes will be cleaned up more frequently than the other upcoming compose types, you can always find a fresh one by using the latest-CentOS-Stream symlink in the test directory Happy testing! --Brian

2 3

Re: [CentOS-devel] [Dev] Documentation change propsal - "Contributing to CentOS Stream" web page
by Miro Hrončok 29 Apr '21

29 Apr '21

On 29. 04. 21 17:13, Michal Schorm wrote: > (4) > Section 1 > Text: "It's also great to have it in Fedora Linux first as well." > > AFAIK, the OS you are mentioning is named "Fedora" or you can use > "Fedora Operating System" (to distinguish from the Fedora Project that > has a broader portfolio than just the OS). I think the "Fedora Linux" > is not correct. > Correct me if I'm wrong I am afraid that you actually are. See https://fedoraproject.org/wiki/Changes/Fedora_Linux_in_os-release -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

1 0

Community Build Service (cbs): deprecating ppc64/armhfp builders
by Fabian Arrotin 27 Apr '21

27 Apr '21

Background story : for some SIGs building for/against 8-stream (and hopefully soon for/against 9-stream), we'd like to upgrade cbs.centos.org to koji 1.23 and all components on CentOS 8-stream. The current setup is based on koji 1.19 on top of CentOS 7 nodes. While we have tested that it works fine for all builds and signing with 8-straem (tracking ticket https://pagure.io/centos-infra/issue/233) we have though a "small" issue that we'd like to announce first here : 8-stream doesn't exist for the following architectures : ppc64 (Big Endian, while ppc64le - Little Endian - exists) and armhfp. I had a quick survey on what is being built/maintained (and so pushed out to mirror CDN) and ppc64/armhfp aren't even used. So it seems that removing ppc64/armhfp support from CBS is the way to go and it wouldn't hurt any SIG. The only SIG that actually builds and ships packages to external mirror is the Infra SIG (so "us"), but we're building pkgs just because we had to maintain that arch ourselves, meaning that if we remove it from cbs, we don't have to maintain infra for ppc64 anymore (for SIG, as pkgs from CentOS 7 distro itself will continue to be built and shipped, but they aren't built on cbs anyway) Opinions ? thoughts ? Depending on feedback (or lack of in this case), I'll announce the maintenance window about cbs.centos.org migration to 8-stream in the next days (normally planned for next week but waiting for some feedback) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

2 1

Board of Directors: Nominations sought
by Rich Bowen 26 Apr '21

26 Apr '21

** Please do read the message before responding with your nominations. We have a process, and if you don’t follow the process, it makes everything harder for everyone. ** ** The process is to email centos-board-private(a)centos.org. Read on for more details. ** At the April Board of Directors meeting, we discussed the annual process of re-appointing the Board of Directors, as defined in our Governance documents. At that time, two directors indicated that they wished to step down, to focus on other things in their life and open the seats to new contributors. (Historical note: The last time a director resigned, the Board simply appointed replacements with no public process. We believe that greater transparency is needed in this new chapter of our existence as a project, and are committed to making that happen.) With two resignations, we have 8 Board seats filled. Our governance definition as it currently stands indicates 8 to 11 seats[1], so we’re still covered. However, we have decided to continue to seat 10 directors as part of the new Board. To this end, we come to you, the CentOS Community, for nominations for who should fill those seats. We ask that you send nominations to centos-board-private(a)centos.org and NOT to this list. There are several reasons for this: 1) Our governance indicates that the Board selects the next Board. We do not have any defined notion of project “membership” or a voting class of any kind, other than the Board itself. We do not wish to give any false impression that a public vote will be held on this list. 2) We do not wish for this to devolve into a bikeshed over proposed names. 3) We do not wish for individuals named to assume that they have any particular advantage over other nominees, nor do we wish for anyone to be shamed, embarrassed, or disappointed, if they are named and then not seated on the Board. The Board will collect those nominations, consider them at an upcoming meeting, and select the next Board at that time. We ask, if you wish to nominate someone, to consider the list of director requirements/recommendations listed at https://www.centos.org/about/governance/director-requirements/ Thank you for your participation in this important moment in our project’s history. Rich, for the CentOS Board of Directors [1] https://www.centos.org/about/governance/

2 2

Mock configs for CentOS SIGs
by Davide Cavalca 26 Apr '21

26 Apr '21

Hello! With the help of Neal, I've put together a mock-centos-sig-configs project to hold mock configs for CentOS SIGs: https://pagure.io/centos-sig-hyperscale/mock-centos-sig-configs This should make it easier to build packages against a given SIG for testing and development using mock. The project currently contains configs for the Hyperscale SIG, but other SIGs are obviously welcome -- just file an issue or (even better) send a PR on Pagure. mock-centos-sig-configs is already packaged in Fedora, and should become available in EPEL in a week or so: https://src.fedoraproject.org/rpms/mock-centos-sig-configs Cheers Davide

1 0

[NFV SIG] NFV SIG meeting minutes - 2020-04-21
by Alfredo Moralejo Alonso 21 Apr '21

21 Apr '21

============================================= #centos-meeting: NFV SIG meeting - 2020-04-21 ============================================= Meeting started by amoralej at 15:09:06 UTC. The full logs are available athttps://www.centos.org/minutes/2021/April/centos-meeting.2021-04-21-15.09… . Meeting summary --------------- * CentOS Stream 8 (amoralej, 15:09:29) * oVirt on CentOS Stream uses the NVF stream repo now: https://gerrit.ovirt.org/c/ovirt-release/+/114200 (dholler, 15:09:53) * now centos-release-nfv-openvswitch points to CentOS Stream 8 repo when installed in CentOS Stream 8 servers (amoralej, 15:10:58) * LINK: https://git.centos.org/rpms/centos-release-nfv/c/d0c51a3918b6c22d393b4f9636… (amoralej, 15:11:28) * LINK: https://blog.oddbit.com/post/2021-04-17-vm-ovs-vxlan/ (amoralej, 15:14:15) Meeting ended at 15:34:49 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (38) * dholler (18) * centbot (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Code of Conduct
by Rich Bowen 19 Apr '21

19 Apr '21

You may have seen, a few days ago, that the Fedora project announced[1] a new Code of Conduct for their community. What you may not have known is that the CentOS project was involved in the crafting of that Code, so that we could also use it here. Yeah, I know, this is something we should have done a long time ago. But, you know what they say about the best time to plant a tree. (The best time to plant a tree is 20 years ago. The second best time is today.) As we continue to work to make all aspects of the CentOS Project more open and transparent, it is important that we create an open, welcoming community where all people, from all backgrounds, feel safe in their participation. This allows for a broader contributor pool, with more ideas and more community ownership of the resulting outcomes. And it's just the right thing to do. It is our intent to take the text of the Fedora CoC, and replace 'Fedora' with 'CentOS' everywhere, and propose it here. There will, of course, be other small changes to the text (Board vs Council, and so on) but not to the details of the Code itself, and how we intend to address reports. We're holding off on those edits so that our version doesn't drift from theirs, during their 2 week comment period. (Ends April 26th.) The document is derived from the Contributor Covenant, along with work that has been ongoing in the Fedora project for some time. Note also that the Contributor Covenant is also the source material for the CoC used by the Linux kernel project.[2] To that end, we encourage you to engage in the discussion around the Fedora CoC, because any changes made there will influence what we end up with here. And we also encourage discussion on centos-devel[3], for anything that you feel is specific to our community. --Rich, on behalf of the CentOS Board of Directors [1] https://communityblog.fedoraproject.org/policy-proposal-new-code-of-conduct/ [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… [3] https://lists.centos.org/mailman/listinfo/centos-devel

1 0

How do I request a new package repo in CentOS 8/9 Stream?
by Connor Kuehl 19 Apr '21

19 Apr '21

Hello, I recently packaged a utility in Fedora 34[1] that enterprise cloud users might find helpful so I'd like to package it for CentOS 8 Stream and CentOS 9 Stream as well. I've been following the CentOS Stream Contributing wiki page[2] to figure out how to get started with this. However, it seems like all of these instructions are only relevant if the package that someone would want to contribute to already has its own repo in the dist-git. I've made some good progress on the CentOS 8 Stream package already, and I'm used to the Fedora process where this is about the time that I'd post it for review soon as part of the authorization process for getting a new repo in the dist-git. Is there a CentOS equivalent to the Fedora package review process for getting a repo created? Thank you, Connor [1] https://src.fedoraproject.org/rpms/rust-sevctl [2] https://wiki.centos.org/Contribute/CentOSStream

6 11

[Cloud SiG] CentOS Cloud SIG meeting (2021-04-08)
by Amy Marrich 16 Apr '21

16 Apr '21

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2021-04-08) ====================================================== Meeting started by paulbisaacs at 15:02:45 UTC. The full logs are available athttps://www.centos.org/minutes/2021/April/centos-meeting.2021-04-08-15.02… . Meeting summary --------------- * CentOS Dojo (paulbisaacs, 15:08:30) * LINK: https://wiki.centos.org/Events/Dojo/May2021 (spotz, 15:11:12) * LINK: https://etherpad.opendev.org/p/centos-cloud-sig (spotz, 15:12:06) * Wallaby (paulbisaacs, 15:17:00) * LINK: http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-wallaby/ (jcapitao, 15:17:32) * Open Discussion (paulbisaacs, 15:25:28) * LINK: https://www.openstack.org/ptg/ (amoralej, 15:28:48) Meeting ended at 15:38:11 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * paulbisaacs (19) * spotz (14) * amoralej (13) * jcapitao (12) * centbot (5) * cyberpear (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy(a)redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz <https://www.redhat.com/>

1 0

Advanced Virtualiazion builds for ppc64le and aarch64 missing on Stream
by Sandro Bonazzola 14 Apr '21

14 Apr '21

Hi, while verifying https://gerrit.ovirt.org/#/c/ovirt-release/+/114299/ noticed we are missing Advanced Virtualization builds for aarch64 and ppc64le on CentOS Stream. I guess it's similar to what happened with ovirt 4.4 and tracked here: https://pagure.io/centos-infra/issue/254 Eduardo can you follow up on this and ensure we have ppc64le and aarch64 packages there? -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

CentOS Stream Feature Request SIG Proposal
by Aoife Moloney 14 Apr '21

14 Apr '21

Hi everyone, I would like to share with you all a proposal I have submitted on creating a SIG dedicated to reviewing and triaging feature requests that come from CentOS Stream development intended for future RHEL releases. The full proposal can be read on the CentOS wiki [0] and an issue has been opened on the CentOS board tracker [1] for review and decision. Here is the proposal summary and I welcome any thoughts, feedback and discussion: Purpose The purpose of this SIG will be to serve as a gate for feature requests that are first developed in CentOS Stream from contributors who wish to request these features to be included in future RHEL releases and are then filed in bugzilla. The SIGs overall goal is to make sure that features which have been filed and have technical merit are triaged internally to the correct venue for further review and development. The SIG will take ownership of regular bugzilla reviews filed under Stream and map feature requests from these bugzillas against the formal RHEL Feature Request criteria to identify and file qualifying requests inside Red Hat to achieve this. I hope you all have a lovely weekend! Kindest regards, Aoife, [0] - https://wiki.centos.org/SpecialInterestGroup/StreamFeatureRequest [1] - https://git.centos.org/centos/board/issue/33 -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

12 16

yum module info squid
by Markus Falb 13 Apr '21

13 Apr '21

Hi, There are 2 versions of squid module available for CentOS 8 http://mirror.centos.org/centos-8/8.3.2011/AppStream/x86_64/os/Packages/ squid-4.4-8.module_el8.3.0+623+2bb85980.2.x86_64.rpm squid-4.11-3.module_el8.3.0+558+7bf80f5f.x86_64.rpm But the output of yum module info does not give corresponding information [root@127162ed7c15 /]# yum module info squid Last metadata expiration check: 0:00:12 ago on Tue Apr 13 18:15:31 2021. Name : squid Stream : 4 [d][a] Version : 8030020201223011621 Context : 30b713e6 Architecture : x86_64 Profiles : common [d] Default profiles : common Repo : appstream Summary : Squid - Optimising Web Delivery Description : an initial version of the squid caching proxy module Requires : platform:[el8] Artifacts : libecap-0:1.0.1-2.module_el8.3.0+395+6cb406eb.src : libecap-0:1.0.1-2.module_el8.3.0+395+6cb406eb.x86_64 : libecap-debuginfo-0:1.0.1-2.module_el8.3.0+395+6cb406eb.x86_64 : libecap-debugsource-0:1.0.1-2.module_el8.3.0+395+6cb406eb.x86_64 : libecap-devel-0:1.0.1-2.module_el8.3.0+395+6cb406eb.x86_64 : squid-7:4.4-8.module_el8.3.0+623+2bb85980.2.src : squid-7:4.4-8.module_el8.3.0+623+2bb85980.2.x86_64 : squid-debuginfo-7:4.4-8.module_el8.3.0+623+2bb85980.2.x86_64 : squid-debugsource-7:4.4-8.module_el8.3.0+623+2bb85980.2.x86_64 One thing is, I would have expected both versions of squid listed. But CentOS repodata seems to generally list one version of the module? The other thing is that squid 4.4-8 has a modification date 2020-12-23 02:14, while squid 4.11-3 dates from 2020-11-04 02:43. The newer package is older, so only the older package is made available? kind regards, markus

2 1

Help Clair Support CentOS
by Louis DeLosSantos 12 Apr '21

12 Apr '21

Hello, My name is Louis and I'm the core maintainer of Clar: https://github.com/quay/clair Clair is a project for scanning containers for vulnerabilities. We'd like to support CentOS but we need a little help in the form of information gathering. For Clair to properly support a distribution we typically require it to have an official upstream vulnerability database. For example, RHEL has their own Oval 2 feeds as does Ubuntu, Suse, etc... What we are trying to determine is how we can extract packages from CentOS containers and match against known vulnerabilities. We have the first half worked out already, we have generic RPM database scanners which extract package names and versions. The second half is where we need some more information. A few questions: * Does CentOS maintain its own security database for packages in its downstream repositories ? * If not, can we reliably treat any CentOS packages (name, versions) identical to the way we treat RHEL packages. (For instance if we find package A with version B can we attempt to match this against RHEL's Oval v2 stream?) * Can you provide any information on package naming, versioning, and packaging that creates a difference between RHEL packages and CentOS? Thank you for your time, I look forward to hearing back.

2 3

screen CVE-2021-26937 for x86_64
by Ben 09 Apr '21

09 Apr '21

Hello, The screen package that fixes the recent CVE-2021-26937 (https://vault.centos.org/7.9.2009/updates/Source/SPackages/screen-4.1.0-0.2…) has been built and populated for all altarches, but does not exist in x86_64. This build for x86_64 appears to have slipped through the cracks? I've raised https://bugs.centos.org/view.php?id=18147 to track this issue. Cheers, Ben

2 2

CentOS Stream 9 web browser default page
by Alain Reguera Delgado 08 Apr '21

08 Apr '21

Rich, everyone! I've been re-designing the web browser's default page and am wondering what content you think it should have in order to be great? I would like to make a collaborative effort of it and am looking for the correct way to do it in our community. This is a welcome page. The first we'll see when the web browser is opened. It also would be visible in the screenshot section the wiki has on the front page (following Akemi's tradition here :) https://gitlab.com/areguera/centos-indexhtml Best regards, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

3 4

NFV SIG meeting minutes 07 April 2021
by Dominik Holler 07 Apr '21

07 Apr '21

To CentOS community, here are meeting minutes for 07-Apr-2021: readable html version of minutes are here: https://www.centos.org/minutes/2021/April/centos-meeting.2021-04-07-15.03.h… Meeting started by dholler at 15:03:05 UTC. The full logs are available at https://www.centos.org/minutes/2021/April/centos-meeting.2021-04-07-15.03.l… . Meeting summary --------------- * Release RPM for CentOS 8 Stream (dholler, 15:06:23) * no progress on new release-rpm for centos-8 stream (amoralej, 15:07:28) * Status of automation and CI (dholler, 15:08:31) * big thanks to amoralej and ykarel for the automation! (dholler, 15:09:00) * automation is working fine for 2.11, 2.13 and 2.15, including 2.15 for centos8 stream (dholler, 15:10:33) * thanks msantana for that work! (amoralej, 15:10:48) * automated release process of ovs2.11 works for oVirt (dholler, 15:15:36) * Introduction of Ales (dholler, 15:16:27) * LINK: https://accounts.centos.org/ (amoralej, 15:18:55) * LINK: https://docs.fedoraproject.org/en-US/fedora-accounts/user/#addingmembers (Arrfab, 15:20:25) * LINK: https://accounts.centos.org/group/sig-nfv/ => so you're sponsor :) (Arrfab, 15:21:32) * amusil has been added as member to the NFV SIG (amoralej, 15:23:51) * LINK: https://review.rdoproject.org/login (amoralej, 15:26:25) Meeting ended at 15:36:26 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (47) * dholler (41) * amusil (11) * Arrfab (4) * centbot (3) * ykarel (1)

1 0

Facebook administration
by Ljubomir Ljubojevic 07 Apr '21

07 Apr '21

Hi everyone. I have been main admin on official Facebook Group since 2011, but I am planing to slowly pass down that duty. With AlmaLinux stable appearing and me soon switching my laptop and internet facing servers to AL8 and Samba+KVM servers to TrueNAS, and my much diminished going online on Facebook (every several days at most), it would be good if CentOS board started asking around for Facebook group admins and moderators who are willing to offer newbies clues and links to solve their problems, so they can be properly acclimated to Facebook environment. Best choice would be forum moderators if they use Facebook regularly. Based on log of approving new members, Ralph Angenendt and few other admins also only come intermittently, every few days, so new blood would be welcome. -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant

5 5

Minutes of the monthly Storage SIG meeting (April 2021)
by Niels de Vos 06 Apr '21

06 Apr '21

Agenda: https://hackmd.io/Epc35JIESaeotoGzwu5R5w?view#2021-04-06 Minutes: https://www.centos.org/minutes/2021/April/centos-meeting2.2021-04-06-10.02.… Minutes (text): https://www.centos.org/minutes/2021/April/centos-meeting2.2021-04-06-10.02.… Log: https://www.centos.org/minutes/2021/April/centos-meeting2.2021-04-06-10.02.… =========================================== #centos-meeting2: Aprils Storage SIG meetup =========================================== Meeting started by ndevos at 10:02:37 UTC. The full logs are available at https://www.centos.org/minutes/2021/April/centos-meeting2.2021-04-06-10.02.… . Meeting summary --------------- * Roll Call (ndevos, 10:02:46) * Agenda (ndevos, 10:04:18) * LINK: https://hackmd.io/Epc35JIESaeotoGzwu5R5w?both#2021-04-06 (ndevos, 10:04:33) * CentOS / Fedora Account merging (ndevos, 10:05:46) * cephadm -pacific builds (ndevos, 10:11:52) * Open Floor (ndevos, 10:27:14) * Building for CentOS Stream (ndevos, 10:28:29) * LINK: http://mirror.centos.org/centos/8-stream/ contains packages for some sigs, so I guess we can publish builds for c8s now too (ndevos, 10:49:50) Meeting ended at 10:55:10 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * ndevos (54) * fmount (46) * kkeithley (30) * centbot (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

auth switch status update : git.centos.org is using new auth source
by Fabian Arrotin 06 Apr '21

06 Apr '21

Just a quick mail to mention that https://git.centos.org was also switched to new auth system and there was just a httpd service restart to reload pagure with new settings. Cheers, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

auth switch status update : cbs.centos.org is back online
by Fabian Arrotin 06 Apr '21

06 Apr '21

Hi all, As announced, we started today the centos infra switch to new authentication source (merged with Fedora) So https://accounts.centos.org is now live and using same auth backend (IPA) than https://accounts.fedoraproject.org This morning at 6:00am utc, I kicked the ansible roles to reflect new TLS/CA for https://cbs.centos.org koji systems and took it offline for sanity tests. - kojihub/web were converted - tested authentication with new TLS cert - tested remote authentication with personal TLS cert - tested to submit koji tasks - verified that all builders were back on the hub and enabled - tested a tag-build/untag-build to test the signing process - tested the new sync script to fetch users/groups from IPA (through https://fasjson.fedoraproject.org , IPA API endpoint using kerberos auth) As all was working, https://cbs.centos.org was then back online around 6:30am UTC What do you need to do : Get your new TLS cert that will be used for cert authentication (new TLS cert as new CA, coming from IPA backend) The SIGGuide (https://wiki.centos.org/SIGGuide) was updated to reflect the new way to retrieve your cert (anchor link : https://wiki.centos.org/SIGGuide#SIGGuide.2FSIGProcess.Community_Buildsystem) PS : worth knowing that if you just had your account imported in new IPA backend, you have *first* to reset your own password (password salt/hash from ACO isn't compatible with the one from IPA, so just reset your password on portal https://accounts.centos.org) PS2: as some users were skipped during import process , it can be that you're in a situation where you either don't exist, or your group membership wasn't reflected (and so you currently don't have build rights anymore in koji/cbs). If that's the case, just ask your SIG chair to get in touch Now moving to other services to be converted -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Hyperscale SIG Quarterly Report for 2021Q1
by Davide Cavalca 05 Apr '21

05 Apr '21

Hello! I just posted our first activity report for the Hyperscale SIG on the CentOS blog: https://blog.centos.org/2021/04/centos-hyperscale-sig-quarterly-report/ One thing I'll signal boost: we have released a systemd 247 backport in the SIG repository. This backport includes experimental SELinux support via an overlay module; if you use SELinux in your deployments and would like to provide feedback, that would be much appreciated. Cheers Davide

1 0

Fedora/CentOS authentication merge : April 1st status
by Fabian Arrotin 01 Apr '21

01 Apr '21

Let me start this email by saying that it's *not* a joke (despite April 1st date) :-) As announced, we turned today https://accounts.centos.org into Read-Only mode , so that we were sure that nothing would change (frozen state) wrt users status and group membership, while all services continued to be usable (including for example https://cbs.centos.org) Mark O'Brien and myself then kicked the fas2ipa script, to ensure that it would have enough time to parse the CentOS accounts and groups as first sanity check. Number of users: 1097 Number of groups: 31 But we found a particular case for people who were registered in both FAS and ACO , with different nickname *but* same email address, so the script failed to import these users (81 accounts) The taken action was to send a mail to concerned users so that they can decide which solution they want to adopt : Basically, either consolidating centos group membership on their FAS account (and so using their FAS account for both projects) *or* update their email address so that the fas2ipa script would be able to import them (but that would mean two different accounts in same auth platform) . We'll take action on case-by-case through email feedback for these users. All in all it seems that it went ok for the sanity check tests and that means that it's green light for the real infra switch on Tuesday April 6th. PS : quite some users were in SKIPPED state, as they never took action for the "email address match for same nickname" situation, explained in previous email (https://lists.centos.org/pipermail/centos-devel/2021-March/076690.html) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel April 2021