March 2020 - devel - lists.centos.org

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

Staging CentOS website redesign
by Alain Reguera Delgado 29 Apr '20

29 Apr '20

Hi everyone, Along the CentOS Logo redesign effort recently mentioned by Tuomas, I would like you to know the availability of https://www.stg.centos.org/, the place where changes pushed to the staging branch of https://github.com/areguera/centos-jekyll-sites are made visible for you to test on-line. I encourage you all interested in CentOS website redesign to look at https://www.stg.centos.org/ and use https://github.com/areguera/centos-jekyll-sites to open issues or even better create merge requests. A big thank you to Fabian Arrotin for making the staging site online and create the github connection that keeps content up-to-date in a pretty fast way. Also to all of you that one way or another contribute to make CentOS a better place. Best regards, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

4 4

building modules
by Tane Adam 27 Apr '20

27 Apr '20

Hi. I was wondering if someone here can provide some guidance on how I can rebuild modules on CentOS (locally)? I found the instructions here https://docs.fedoraproject.org/en-US/modularity/making-modules/building-mod… But I'm not sure it applies directly on CentOS. For example I can locate 'module-build-service'. Any help or advice appreciated. Tane.

4 5

Question: Gluster v7.4 package build status
by Strahil Nikolov 23 Apr '20

23 Apr '20

Hello CentOS Storage SIG, Can someone tell me how I can check the build status of the Gluster v7.4 packages ? Best Regards, Strahil Nikolov

3 7

[FIPS] FIPS_selftest failing in Centos 7
by Akshar Kanak 09 Apr '20

09 Apr '20

Dear team The API FIPS_selftest() is failing . The content of the file /proc/sys/crypto/fips_enabled is 1 I have executed the below mentioned code The code is #include "stdio.h" int main() { int ret=0; ret=FIPS_mode(); printf("\nFIPS_mode = %u \n",ret); ret=FIPS_selftest(); printf("\nFIPS_selftest=%u \n",ret); ERR_print_errors_fp(stderr); } Output is " FIPS_mode = 1 FIPS_selftest=0 140091346814640:error:0607B0A3:lib(6):func(123):reason(163):evp_enc.c:313: 140091346814640:error:2D06F065:lib(45):func(111):reason(101):fips_des_selftest.c:134: " Looks like flag EVP_CIPH_FLAG_FIPS is not set for the cipher returned by EVP_des_ede_ecb() . I am using openssl-1.0.2k-19.el7.x86_64 on "CentOS Linux release 7.6.1810 (Core)" Please let me know you thoughts on this Thanks and Regards Akshar

2 1

Dealing with unshipped -devel packages in CentOS Linux 8 and CentOS Stream
by Brian Stinson 03 Apr '20

03 Apr '20

Hi Folks, We were exploring ways to deal with devel packages that are unshipped upstream in RHEL 8, but which are required at build-time in SIG deliverables, or for software that you might want to build at home. We just pushed the Devel variant to the mirrors, as soon the mirror network coalesces, you can find this repository at: http://mirror.centos.org/centos/8/Devel, OR http://mirror.centos.org/centos/8-Stream/Devel We are currently in the process of including a .repo file (disabled by default) in centos-release. Look for an update to that soon. Special thanks to James Antill, who did most of the compose work on this variant. Here are some questions that you might have, and some answers: ## What is the Devel repo for? We envision using the Devel repo for packages that are unshipped in CentOS Linux/CentOS Stream but needed for build-time dependencies of other packages. Devel is *NOT* meant to satisfy runtime dependencies or for long term use on general purpose machines. ## How do I use the Devel repo? We will soon ship repo files in centos-release-8.1-1.1911.0.9.el8 and centos-release-stream-8.1-1.1911.0.9.el8, once those are installed you can enable the Devel repo by running: dnf config-manager --enable Devel (on CentOS Linux), OR dnf config-manager --enable Stream-Devel (on CentOS Stream) Reminder: this repo is *not* for general purpose use, and is only recommended for buildtime activities only. ## How do I ask for an unshipped package to be included in Devel? Please file a bug on bugs.centos.org Project: CentOS-8 Category: _unreleased_devel_packages Give us a short description of the -devel package that you need, and a description of what the -devel package is used to build. ## Why do you need to know what the -devel packages are used for? We ask for that information to better understand the impact of not including them in a normal release artifact. This is an information gathering opportunity and is *not* for making inclusion/rejection judgements for Devel ## Why isn't my package included yet? We began with a small subset of requests to test our compose and delivery configs. We plan to close out bugs that are fixed with this push shortly, and then process the rest of the queue. Stay tuned to your open bugs if you have them. ## Why not include *all* unshipped components in Devel? One reason is that we want to gather impact information that we can communicate upstream. More importantly, Red Hat has decided that these unshipped packages are lower in bugfix/update priority compared to the ones that made it into RHEL. In very limited cases, we may not see updates to such packages through the usual source-drop process, we need to maintain a list so that the CentOS team can monitor those packages more closely. Happy Building! -- Brian Stinson

5 6

CentOS logo and brand update on the next board meeting agenda
by Tuomas Kuosmanen 01 Apr '20

01 Apr '20

Hello everyone. I hope everyone is coping as well as possible in the current events. There has been a collaborative design effort to update the CentOS logo and brand, and we are on the agenda of the next CentOS board meeting (in a week) to present an update to the current CentOS branding for approval. We are excited to be at this point. In the spirit of openness, and because we are human, it could be that some of us have missed the earlier mail about this [ https://lists.centos.org/pipermail/centos-devel/2020-January/036517.html] So, I am announcing this yet once more, to make sure everyone is aware of our progress, the upcoming decision, and has a final chance to voice possible concerns and give feedback. I want to avoid sending attachments to the mailing list, so please see the blog post i wrote on January which summarizes the process and features the proposed logo and brand updates: https://blog.centos.org/2020/01/updating-the-centos-logo-and-visual-style/ Also, the issue on git.centos.org can be interesting reading for anyone interested in how we have reached this point: https://git.centos.org/centos/Artwork/issue/1 The feedback we have received so far has been positive and constructive, so let us know of any concerns you might have. Best regards, Tuomas Kuosmanen

10 18

New KDE available for testing on CentOS Stream
by Troy Dawson 01 Apr '20

01 Apr '20

CentOS Stream has recently been updated to include the updated qt5-5.12.5 that will be part of RHEL 8.2. The qt5-5.12.* releases are the LTS version of qt5, we this very good news. The problem is that the KDE packages in EPEL were built on qt5-5.11.*, and many of them won't install on 5.12. I have rebuilt KDE for RHEL 8.2 x86_64 and have it in my Fedora people area. I have updated all the added qt5 packages to be 5.12.*, to match the qt5-5.12 in RHEL 8.2. I have also updated most of the plasma packages to 5.18.*. This is the corresponding plasma LTS release that goes with qt5-5.12. I have also updated most of the kf5 packages to 5.67.* / 19.12 . There is no LTS release for the kf5 packages, there were the latest at the time I was rebuilding them. In summary, this is a new shiny KDE Plasma Desktop. It would be great if people could test it before RHEL 8.2 / CentOS 8.2 comes out. How to try it out. 1 - Install CentOS-Stream http://isoredirect.centos.org/centos/8-stream/isos/x86_64/ 2 - Install the config for my KDE on Stream repo wget-O /etc/yum.repos.d/rhel8-beta-kde.repo https://tdawson.fedorapeople.org/epel8/kde/rhel8-beta-kde.repo 3 - Setup EPEL configs rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm 4 - Enable Stream-PowerTools, and disable non-stream repos dnf config-manager --enable Stream-PowerTools dnf config-manager --disable AppStream dnf config-manager --disable BaseOS dnf config-manager --disable extras 5 - Install KDE Plasma Desktop dnf group install kde-desktop (Optional) dnf group install kde-media (Optional) dnf group install kde-apps 6 - If installed from GNOME, reload gdm systemctl reload gdm 7 - If installed from minimal install, setup graphical boot systemctl set-default graphical.target systemctl enable sddm -f Give it a try, and let me know of any bugs. Thank You Troy Dawson

2 1

CentOS 8 upcoming OpenStack packages are htting gRPC bug #21213
by Anthony Alba 01 Apr '20

01 Apr '20

Hi CentOS developers (especially CloudSIG), I started playing with some of the el8 OpenStack Ussuri packages like gRPC 1.26 and protobuf 3.11.2. The packages from CBS are: grpc*1.26.0-1.el8.x86_64.rpm protobuf*3.11.2-2*rpm Immediately I hit the bug https://github.com/grpc/grpc/issues/21213 trying the simplest helloworld quickstart, where the ./greeter_server hangs. The Train packages for EL7 (gRPC 1.20, protobuf 3.6) work fine. Just a heads-up - I manually compiled gRPC 1.27.x (wow — that is hard to do) with CBS's protobuf and I got the quickstart to work. Anthony Alba

4 5

Storage SIG meeting minutes - March 2020
by Giulio Fidente 30 Mar '20

30 Mar '20

Hi, I wanted to share the latest Storage SIG meeting minutes: https://www.centos.org/minutes/2020/March/centos-meeting.2020-03-03-10.03.h… Please remember we have an open agenda so feel free to add questions/topics into it for the next occurrence: https://hackmd.io/@qItv4l_CSAOOoigrY3dOGA/rkAGV6Lpr Thanks everyone for participating -- Giulio Fidente GPG KEY: 08D733BA

1 0

Re: [CentOS-devel] The Git forge decision (was CPE Weekly: 2020-03-28)
by Neal Gompa 30 Mar '20

30 Mar '20

On Mon, Mar 30, 2020 at 8:13 AM Nicolas Mailhot via devel <devel(a)lists.fedoraproject.org> wrote: > > Le dimanche 29 mars 2020 à 23:47 -0400, Neal Gompa a écrit : > > > > > As a General User > > > I want to access repos fully over https > > > For environments where SSH is blocked > > > > I would be really curious if the Red Hat Infrastructure Security guys > > have changed their opinion on this after four years of blocking the > > development of this feature in Pagure. The two major reasons we don't > > have this in Pagure are: > > Neal, > > Security is the usual excuse not to implement stuff. That does not work > when competing with others that did their homework. As you noted > yourself ssh accesss is not blameless either. > > Gitlab and Github work in https mode. Pagure does not. End of story. > > Expecting others to hole their security with corkscrew because of the > ssh holy cow was never going to impress any third party. > You don't have to tell me, I already know. It was intentionally not implemented. And even with all that, we *do* have HTTPS through SSO on src.fp.o. We just don't have it on pagure.io. Don't expect it to be available with the move to GitLab. GitLab admins have a toggle they can use to disable HTTPS pushing for policy reasons, and I will strongly bet on it being flipped so that HTTPS pushing will not be available in our GitLab. -- 真実はいつも一つ！/ Always, there's only one truth!

1 0

Git Forge Decision from the CPE Team
by Leigh Griffin 30 Mar '20

30 Mar '20

Hi everyone, Thank you for your patience while the CPE Team worked through an incredible number of requirements from multiple stakeholder sources. On Friday evening we announced on the CentOS Blog <https://blog.centos.org/2020/03/git-forge-decision/> our decision to adopt Gitlab as our Git Forge and to retain pagure.io to ultimately hand over to the Community to maintain. It wasn't an easy decision by any stretch of the imagination and we hope that the compromise that we are striking will help to allow Pagure flourish and to give a choice of Forges for your usage. I'm happy to field any questions or comments about this decision. Kind regards, Leigh, on behalf of the CPE Team -- Leigh Griffin Engineering Manager Red Hat Waterford <https://www.redhat.com/> Communications House Cork Road, Waterford City lgriffin(a)redhat.com M: +353877545162 IM: lgriffin @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://red.ht/sig>

1 0

CPE Weekly: 2020-03-28
by Aoife Moloney 28 Mar '20

28 Mar '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-03-06 Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. ### CentOS * ppc64le and aarch64, 8 and 8-stream nodes now available in cico for tenants to checkout. -- Email sent to ci-user list * New signing for SIGs (through https://cbs.centos.org) live this week! ### CentOS Stream * Qt5.12 pushed in response to an internal request * NetworkManager re-imported ## Fedora Updates * Freeze is over! * New version of pagure (5.9.0) has been released and deployed in staging and on pagure.io * Document being worked on about how to onboard new CI systems in Fedora - this is a work in progress! https://hackmd.io/5gk_kHFhSR6sKa1huPA-4Q ### Request for Review * Fedora magazine: Article proposals about Silverblue rebase to F32 https://pagure.io/fedora-magazine-proposals/issue/59 * Packit integration in the-new-hotness https://github.com/packit-service/packit/issues/689 * KeepassXC flatpak issue https://pagure.io/flatpak-module-tools/issue/6 ### Data Centre Move * Communishift will be unavailable from 2020-04-13 until 2020-05-08 * Check out our detailed move shedule here https://hackmd.io/R3EkjzVyTG2TYwQvkfzYrA?sync=&type= * Covid-19 has seen restrictions added to the data centres we are moving from and to, however we are unaffected as of yet for the move. * If or when our timelines become affected, we will inform you immediately of any outages, downtimes, etc a delay could cause. * Thank you for your understanding at this particularly uncertain and worrying times. ### AAA Replacement * We are nearly complete in our phase one development! * Below are some of the features the team have developed since beginning the project in mid-Jan * UI where people register and login * Add groups function * Change personal details * Enroll OPT * Reset password * View group owner details * Use a search engine * Our next steps in this project is to demo to the team for feedback and then continue to develop CentOS authentication, more user focused features, request for more feedback and test, test test! ### CI/CD * Monitor-gating is now running in production and has already caught a couple of issues with bodhi (both in stg and in prod)! * Rpmautospec * This is in review as a Fedora package: https://bugzilla.redhat.com/show_bug.cgi?id=1816124 * Work progressing on Koji tagging plugin (post-build), full use case support for bumping releases * The team hope to deploy this in staging soon! ### Sustaining Team * Mbbox * Some progress on CRD for koji-builder and koji-hub components has been made this week * Bodhi 5.2.2 released * Some issues with celery tasks & rawhide monitoring has been super useful with this. * Compose Tracker enhancement * Tagging issues have been resolved * Ability to ping maintainers * Fedora Minimal Compose * Odcs-backend-releng01 has been provisioned to enable testing ## CentOS Updates ### Other Updates #### GitForge Decision * After evaluating over 300 user stories from multiple stakeholders we have aligned on a decision for the Gitforge that CPE will operate for the coming years. We are opting for Gitlab for our dist git and project hosting and will continue to run pagure.io with community assistance. * Check out our GitForge decision on the Fedora Community blog https://communityblog.fedoraproject.org/ * And at the CentOS blog page https://blog.centos.org/2020/03/git-forge-decision/ * Keep an eye out for mails in the coming months to the devel lists as we plan transitions and next steps with GitLab * We would like to express our sincere thank you to all who contributed requirements to us! As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Last call for video content: CentOS @ Red Hat Summit
by Rich Bowen 25 Mar '20

25 Mar '20

Next month, Red Hat Summit will be happening, as a virtual event. They're expecting 30,000 "attendees", and we're delivering content via videos. If you'd like to present your work in the CentOS project to 30,000 interested people, PLEASE get in touch with me ASAP, and we can schedule a short video interview for inclusion in that event. Any topic is fair game, if it's related to the CentOS project. The deadline for delivering these finished videos is Monday, March 30th, so I really need to hear from you today or tomorrow if we want to make this happen. Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

3 3

CBS Signing process going live this wednesday !
by Fabian Arrotin 25 Mar '20

25 Mar '20

Hi all, After some tests and some feedback from some SIGs , we're happy to announce that we'll go live this wednesday with the new signing process (also covering c8) Per discussion/feedback with some SIGs (or lack of feedback), we locked the following CBS tags : paas7-openshift-origin311-release paas7-openshift-origin-release paas7-openshift-origin13-release paas7-openshift-origin14-release paas7-openshift-origin15-release paas7-openshift-origin36-release paas7-openshift-origin37-release paas7-openshift-origin38-release paas7-openshift-origin39-release paas7-openshift-origin310-release paas7-openshift-common-release nfv7-vpp-1801-release nfv7-vpp-1804-release nfv7-vpp-1807-release nfv7-common-release virt7-ovirt-42-release virt7-ovirt-44-release virt7-kubernetes-19-release virt7-kubernetes-110-release opstools7-perfmon-common-release opstools7-common-release opstools7-sensu-common-release opstools7-sensu-027-release opstools7-sensu-110-release opstools7-fluentd-012-release If you have questions, Thomas and myself will be answering in #centos-devel, should any issue arise. PS : for Trimmed content/EOL, each SIG should start considering announcing content that will go away (to vault and not available to mirror network) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

3 4

SIG members: Presentations for the "virtual summit"
by Rich Bowen 24 Mar '20

24 Mar '20

As you may have seen, Red Hat Summit has been converted to a virtual event - https://www.redhat.com/en/summit - and we, the community projects that were to have a presence there - have been asked to supply some of the content for that virtual event. This is an opportunity to tell a wider audience about what we're doing in this project. In particular, I invite SIG members to provide an update, in the form of a video/slide presentation, about what your SIG has been working on, what's planned for the coming year, and how new participants can get involved. If you are involved in a SIG, please discuss this with the other participants, and put together 2-5 slides about the above topics, and designate someone who can deliver this content. Get in touch with me, and we can schedule a time to record this presentation via Google Meeting, or Bluejeans. I *think* that the "virtual summit" will be async, rather than live presentations, but that is still being figured out at this time. Meanwhile, gathering the content and identifying the speakers is an important first step. If you're interested in presenting some other (ie, non-SIG related) content, please do get in touch with me. Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 1

CBS mash repositories going away next wednesday
by Fabian Arrotin 23 Mar '20

23 Mar '20

Tied to the previous announce, the new signing system will not depend on cbs-content-control, which itself was using repositories prepared by mash. Those repositories, while normally not meant to be consumed, will so go away. So all https://cbs.centos.org/repos/* will disappear next wednesday (FWIW) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

2 2

CPE Weekly: 2020-03-21
by Aoife Moloney 21 Mar '20

21 Mar '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-03-21 Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. ## Fedora Updates * Fedora 32 Beta is released * Pungi configs created * RC composes ran * Synched to stg * Checksums signed * Pushed to mirrors * F32 flatpack support added * Silverblue is rebased for f32 - article on proposal to Fedora Magazine https://pagure.io/fedora-magazine-proposals/issue/59 ### Issue FYI's & Request for Review * The team are working on resolving the issues in the staging environment for the packager workflow https://pagure.io/releng/issue/9293 * Help with infra-sig packaging appreciated https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&… * Packit integration in the-new-hotness https://github.com/packit-service/packit/issues/689 * KeepassXC flatpak issue https://pagure.io/flatpak-module-tools/issue/6 ### Data Centre Move * Communishift will be unavailable from 2020-04-13 until 2020-05-08 * Check out our detailed move shedule here https://hackmd.io/R3EkjzVyTG2TYwQvkfzYrA?sync=&type= ### AAA Replacement * OTP & 2FA authentication is now working! * Fedora messaging is also integrated in the project * As always, check out our progress on github here https://github.com/orgs/fedora-infra/projects/6 ### CI/CD * The koji plugin which is triggered post git checkout has been written and merged in the rpmautospec project * Working on finishing the rpmautospec logic for release and changelog and use it in the koji post git-checkout plugin and hope to achieve the following * Write the koji plugin to add git tags on dist-git (via pagure) upon successful builds * Package rpmautospec as an RPM * Deploy to stg * Links to the WIP issues in the POC * https://pagure.io/Fedora-Infra/rpmautospec/pull-request/15 https://pagure.io/Fedora-Infra/rpmautospec/pull-request/9 https://pagure.io/Fedora-Infra/rpmautospec/pull-request/5 https://pagure.io/Fedora-Infra/rpmautospec/pull-request/7 https://pagure.io/Fedora-Infra/rpmautospec/pull-request/8 https://pagure.io/Fedora-Infra/rpmautospec/pull-request/13 ### Sustaining Team * Mbbox upgrade work * Project is kicked off https://github.com/fedora-infra/mbbox/projects/1 Vagrant environment for operator-sdk ready Initial operator project ready Work on koji-hub CRD started Work on koji-builder CRD started * RabbitMQ has an outage so a new troubleshooting section has been added to the SOP https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/rabb… ## Docs * Issue created for problems with SELinux documentation in Fedora Quick Fix https://pagure.io/fedora-docs/quick-docs/issue/207 * Build errors updated in the Fedora Defensive Coding Guide https://pagure.io/defensive-coding-guide/issue/7#comment-634123 * F32 release notes being worked on ### Misc Updates/Review Requests * Upgrade pagure and pagure-dist-git on stg * Bugzilla overrides on src.stg landing * Infra-Sig Package Updates * https://bodhi.fedoraproject.org/updates/FEDORA-2020-2c40290717 https://bodhi.fedoraproject.org/updates/FEDORA-2020-2f3ff7bd46 https://bodhi.fedoraproject.org/updates/FEDORA-2020-2c3c3a9e25 https://bodhi.fedoraproject.org/updates/FEDORA-2020-dcb1f11c25 * Jms-messaging-plugin wire support https://github.com/jenkinsci/jms-messaging-plugin/pull/162 * Create 1.0 milestone for Anitya https://github.com/fedora-infra/anitya/milestone/6 * Openh264 Generated the repos Signed the rpms and repodata Sent them to cisco and waiting ## CentOS Updates ### CentOS * Fedora infra images are added to quay.ie for shared library * ppc64le image in testing ### CentOS Stream * Python38 module is running in c8S! * Kernel + VDO has been created for Stream * The team are refactoring the sync2git role and hope to deploy it soon As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

newer cri-o builds for CentOS 7
by Baptiste Agasse 20 Mar '20

20 Mar '20

Hi all, I try to find a build of cri-o > 1.13 in a repo for CentOS 7. I find some package version that fit this requirement [1] and some builds[2] that are tagged with 'paas7-crio-115-release' but I didn't find any newer version of cri-o than crio-1.11 in origin311 repo [3]. Is there any repo that I'm missing where newer cri-o builds are located ? Have a nice day. Cheers. [1] https://cbs.centos.org/koji/packageinfo?packageID=5695 [2] https://cbs.centos.org/koji/buildinfo?buildID=26497 [3] http://mirror.centos.org/centos-7/7.7.1908/paas/x86_64/openshift-origin311/ -- Baptiste

4 3

Tags structure proposal (and fix) for CBS
by Fabian Arrotin 19 Mar '20

19 Mar '20

When working with Thomas on new signing process, we decided that we'd use Koji/CBS as single source of truth, so new signing process should only query koji/cbs and automatically act when there would be something to do. Creating so a different thread to discuss the koji tags we have. We discovered some inconsistencies and we think that $now would be a good time to fix/move those if needed. The current proposal would be (and most of the existing tags are following that convention) : <sig><dist>-<sig_project>-<sig_project_rel>-<sig_level> If we take an example for Gluster 7 for CentOS 7, built by Storage SIG, that means the following tags : storage7-gluster-7-{candidate,testing,release} The path where new process would automatically push out (to mirror CDN) would be so based on koji tag : mirror.centos.org/{centos,altarch}/<dist>/<sig>/{arch}/<sig_project>-<sig_project_rel>/ Once again, if we take the gluster 7 as an example, that would mean that process would automatically (for -release tag, with three enabled arches), push to those paths (created if needed) : * http://mirror.centos.org/centos/7/storage/x86_64/gluster-7/ * http://mirror.centos.org/altarch/7/storage/aarch64/gluster-7/ * http://mirror.centos.org/altarch/7/storage/ppc64le/gluster-7/ The full path is coming from the koji tag, but we see some issues for some paths/SIGs (like NFV) As we think that it would be good to have confirmations from all SIGs (as they are responsible for content to be pushed out, and also good time to have EOL content removed), we'd eventually "lock" koji tags for which we have *not* received confirmation for final destination path. Other thing we discovered : some SIGs (in the past) have asked for a "common" tag but then have asked (through cbs-content-control) to have content from that common tag to be added in other repo. As we'll *not* use cbs-content-control anymore, the way to deal with this would be : - either we use koji tag inheritance (preferred solution) - or you just "tag-build" yourself when needed from one to the other The advantage of doing this through koji tag inheritance is the following : When you request for some tags, and specify what they would need, nothing else would have to be done and you can just tag-build from -testing to -release to trigger the sign+push to mirrors (while tag-build to -testing first would push unsigned pkgs automatically to buildlogs.centos.org, as usual) Can we ask each SIG Chair to see which projects/releases are still needed and so come back (either in this thread of #centos-devel) Thanks for your collaboration ! -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

2 1

CentOS for IBM LinuxONE / IBM System Z
by FuLong Wang 19 Mar '20

19 Mar '20

Hello Everyone, I'm from IBM China Development Team and I'm working on a new initiative that plan to enable a "*minimized*" or "full" CentOS operating system on IBM LinuxONE / IBM System Z (s390x architect). The reason why we start this topic is we are trying to contribute to the RDO community with our OpenStack build on LInuxONE. We have successfully finished the build job for OpenStack Train Version on LinuxONE and passed the basic function verification tests recently. Now, we already have a link for worldwide users & fans to reference for their needs. For "official official" contributing to the RDO community, community admin stated that a TripleO CI env is a must for community release criteria and the OpenStack packages need to be built in the CentOS build system which run on s390x arch. So, we turn to here for help, we know CentOS community ever had releases for s390x arch but for whatever reasons finally stopped for update. We want to take this opportunity to enable it up again and therefore want to know about the overall processes, skills required, hardware requirements, manpowers and duration estimated and which parts need IBM's team's input, etc. Our target is to enable at least a *"minimized" CentOS* (which can support the OpenStack CI work), is there a SIG fit for this purpose? or a "full" CentOS with default feature sets. Could anybody kindly give us some clue to start this journey? Thanks everyone in advance! The Howto of OpenStack Train Installation on IBM LinuxONE had been merged to the RDO official website. https://www.rdoproject.org/install/ -- FuLong Wang fulong.wang(a)cn.ibm.com IBM China Systems Lab, Beijing, China _______________________________________________

5 9

New CBS/SIG signing process
by Fabian Arrotin 16 Mar '20

16 Mar '20

Hi all (especially SIG members/contributors) , As announced by Jim some time ago, we wanted to redesign the current signing process that is in place for https://cbs.centos.org for CentOS 6 and 7 (so quite some years now) The goal is to automate as much as possible the workflow, and working for all releases (yeah for CentOS 8 and Stream) Thomas and myself have worked on the following idea and we're now happy with the results (in our Dev environment) : - when someone builds a pkg, and that it's tagged to -testing, koji sends a notification (through koji callback - https://fedoraproject.org/wiki/Koji/WritingKojiCode#Event_Plugin) to a bus - signing machine listens to the bus, process the tag and push directly to buildlogs - when someone tag-build said pkg to -release, the node signs it with correct gpg key id (from the SIG), push generated repository (including for debuginfo/src.rpm packages) to mirror CDN As we were working on such automation, we also confirm that if one uses "untag-build", the same rule applies : it triggers automatically koji to reprocess the tag/repo and so removes the pkg from mirror (we got some requests for that in the past) The process so would work 24/7, and also have monitoring built-in (so that we can detect - the infra team - when something doesn't work, and so we can still process the tag again) We recently upgraded cbs.centos.org to newer koji version that permits some of the needed operations for this to happen. At this stage, we are just missing the SIG GPG private keys, but we were promised to have those this week. We don't have any ETA yet for the migration to new signing system, but we were thinking about such plan: - deploy and configure (automatically) new signing node (this week) - import GPG keys in the new system and validate that we can sign (when we get those) - changes some flags/parameters on tags on cbs.centos.org (this week) Once we have this in place, we'd like to start validating the signing process but *not* pushing to mirror CDN (yet). Same for the bus : we'd like to process all tags in advance as we'll have to import RPM signatures back in koji/cbs. After full validation, we announce that new system would be fully in place, and kojihub restarted with the notification plugin. From that point, the system would be fully operational and so when SIG members would build/tag pkgs, that would trigger the push (and signing if needed for -release tag) Worth knowing that with the update to some components in the chain, the directory layout will change a little bit (like people are already used to if using Fedora and Epel) : the Packages will be splitted by first letter. Here is an example from our testing : └── storage └── x86_64 └── gluster-7 ├── Packages │ ├── g │ │ ├── glusterfs-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-api-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-api-devel-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-cli-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-client-xlators-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-cloudsync-plugins-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-devel-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-events-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-extra-xlators-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-fuse-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-geo-replication-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-libs-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-rdma-7.2-1.el7.x86_64.rpm │ │ ├── glusterfs-resource-agents-7.2-1.el7.noarch.rpm │ │ ├── glusterfs-server-7.2-1.el7.x86_64.rpm │ │ └── glusterfs-thin-arbiter-7.2-1.el7.x86_64.rpm │ ├── p │ │ └── python2-gluster-7.2-1.el7.x86_64.rpm │ └── u │ ├── userspace-rcu-0.7.16-3.el7.x86_64.rpm │ └── userspace-rcu-devel-0.7.16-3.el7.x86_64.rpm └── repodata ├── 047503df3313d596e14a1a0d097b6c2261b26690000ecd4260d212a6f5e5632d-other.sqlite.bz2 ├── 34c1f5dd954099816d6cce289e52f96e61cc2e6430e13072194e35c063b0e3da-primary.xml.gz ├── 6293e07e4c5a7acc2c610beb5acb84b996329ef3c6d61c03e375f2afc6a71536-filelists.sqlite.bz2 ├── 6f89e8b43fb7e384f86f041c4de84d9afeb15dca981559b15230cb48887095db-other.xml.gz ├── bef236563d185417fbda48e3b4dd1d62714d1af2b7a7d6dc1a7213af5de1aa9b-primary.sqlite.bz2 ├── fb66c148e8e2738bd5d19b88d1b3507b0383aaab0938de3809b399babb1a0b44-filelists.xml.gz ├── repomd.xml └── repomd.xml.asc From a usage perspective that will not change the way pkgs can be consumed, as repodata will always be at the right place, but in the case of SCLs that will mean no subdirectory like before, but instead just same "first letter" name (while repodata will be global) So in the current stage, we'd like to deploy and fully validate the signing setup and we'll announce on this list when we'll fully switch to new system. Also worth noting that with the new system in place, in theory we'll *not* use the old cbs-content-control git repo (as we'll query automatically koji for tags, enabled architectures, etc) so tagging to -testing and -release should trigger automatically the "push to mirrors" step If you have questions, comments, feel free to answer in this thread and/or #centos-devel on irc.freenode.net Kind Regards, Thomas and Fabian -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

8 18

Trimming/Removing EOL SIG content from mirror.centos.org
by Fabian Arrotin 16 Mar '20

16 Mar '20

Hi all SIG members, When working in our "Staging" environment while validating the new signing process (still to be announced when fully in use/prod), we detected some SIGs having multiple variants/versions of their packages. Just one example (already discussed with Niels and Kaleb in #centos-devel but let's just this one a example): Gluster has multiple versions still listed on mirror.centos.org : http://mirror.centos.org/centos/7/storage/x86_64/ As the new process would automatically decide where to push content based on koji/cbs tag name, we found the interesting corner case of gluster312. The CBS tag is storage7-gluster-312-release and so new process would push to centos/7/storage/x86_64/gluster-312/ instead of http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/ (see the diff betwen koji/cbs tag and the final path/destination) It seems that only Gluster was impacted for older releases, while it should be good for new releases (tested). But so that brings the following request : can you come with a list of EOL repositories that you'd like us to trim/remove from mirror.centos.org (they'll be archived to vault.centos.org) ? Doing that at the same time as we launch the new signing/push process would be a good idea. Thanks a lot in advance for your collaboration ! -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

5 9

CPE Weekly:2020-03-14
by Aoife Moloney 14 Mar '20

14 Mar '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-03-06 Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. ## Fedora Updates * Fedora 32 Beta work is underway * Fedora Minimal Compose is being worked on with a dedicated ODCS backend running being investigated * Check out the Fedora Council video meeting to find out more about our team here https://www.youtube.com/watch?v=QN8HqBeoozo * Take a look at our (work in progress!) project taiga board to see what we're working on now, next, and still to do! https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null * Have a read of one of our teams article in Fedora magazine: https://fedoramagazine.org/fish-a-friendly-interactive-shell ### Data Centre Move * Communishift will be unavailable from 2020-04-13 until 2020-05-08 * Check out our detailed move shedule here https://hackmd.io/R3EkjzVyTG2TYwQvkfzYrA?sync=&type= ### AAA Replacement * OTP & 2FA authentication is now working! * Fedora messaging is also integrated in the project * As always, check out our progress on github here https://github.com/orgs/fedora-infra/projects/6 ### CI/CD * Progress on tagging package history: tests, robustness * Progress on koji plugin to run the rpmautospec * Most work in this repo: https://pagure.io/Fedora-Infra/rpmautospec ### Sustaining Team * Mbbox upgrade work underway with the team looking at operators to deploy and maintain the different services * Infra tickets are starting to be prioritized https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… * Looking at the ansible operator https://github.com/fedora-infra/mbbox/issues/5 * Creating mbbox sustaining project https://github.com/fedora-infra/mbbox/projects/1 * Vagrant OpenShift 3.11 for mbbox https://github.com/fedora-infra/mbbox/pull/1 ## Docs ### Misc Updates/Review Requests * PR Reviews needed for the following: * Vagrant Operator SDK for mbbox review https://github.com/fedora-infra/mbbox/pull/9 * Rebase Silverblue to Fedora 32 - multi monitor setup issue https://bugzilla.redhat.com/show_bug.cgi?id=1810070 * Fedora magazine: Article proposals about Silverblue rebase to F32 https://pagure.io/fedora-magazine-proposals/issue/60 https://pagure.io/fedora-magazine-proposals/issue/59 * Packit integration in the-new-hotness https://github.com/packit-service/packit/issues/689 * KeepassXC flatpak issue https://pagure.io/flatpak-module-tools/issue/6 * Jms-messaging-plugin reviews https://github.com/jenkinsci/jms-messaging-plugin/pull/162 * Misc Updates: * Helped firefox maintainer sort out koji auth * Gathered logs for qgis maintainer to debug why builds hang * Checked over rawhide compose after open-h264 repo was enabled by default to make sure no content from it got in. * PR sent to fix f32 media with rawhide kickstarts * Migrated fedora-comps to weblate. * Upgraded koji to 1.20.1 via freeze break * PR's Created this week: * Bodhi 5.2 PR reviews https://github.com/fedora-infra/bodhi/pull/3945 https://github.com/fedora-infra/bodhi/pull/3940 https://github.com/fedora-infra/bodhi/pull/3933 https://github.com/fedora-infra/bodhi/pull/3931 https://github.com/fedora-infra/bodhi/pull/3910 https://github.com/fedora-infra/bodhi/pull/3903 https://github.com/fedora-infra/bodhi/pull/3798 * Infra tickets https://pagure.io/fedora-infrastructure/issue/8684 https://pagure.io/Fedora-Infra/review_stats/issue/2 * Fedmsg-koji-plugin https://pagure.io/koji-fedmsg-plugin/pull-request/12 https://pagure.io/koji-fedmsg-plugin/pull-request/13 * Fedora-messaging https://github.com/fedora-infra/fedora-messaging/pull/163 ## CentOS Updates ### CentOS * CentOS CI uptime is 100% * Kickstarter for CentOS 8 arch ppc64le * Check out the mail thread about dealing with unshipped -devel packages for CentOS Linux & Stream too https://lists.centos.org/pipermail/centos-devel/2020-March/036644.html ### CentOS Stream * Python38 module is running in c8S! * More work being done on the contributor workflow too with help from the Packit Team As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Upcoming CentOS events and COVID-19
by Rich Bowen 12 Mar '20

12 Mar '20

TL;DR: We have postponed the upcoming Dojo at Facebook, and are carefully watching the situation to determine any other event participation in the coming months. Due to the developing situation with the Corona virus and COVID-19, we have made the decision to postpone our upcoming CentOS Dojo that was scheduled to occur at Facebook on April 24th. Details of that event are here - https://wiki.centos.org/Events/Dojo/Facebook2020 - and will be updated once a new date has been selected. Other upcoming events are still scheduled to occur, as they are farther out. The next scheduled event will be at CERN on October 23rd, and we will update details as we get closer. Details for that event are available at https://wiki.centos.org/Events/Dojo/CERN2020 and the call for presentations is still open. Our planned booth presence at other upcoming events has been canceled for the foreseeable future, and we will update our event listing at https://wiki.centos.org/Events once the world situation improves and travel is once again feasible. There are several other proposed Dojos in the works at this time, but we are not going to publish any details until the epidemic crisis has passed. Thank you for your patience and understanding, and we'll send updates here once things become clearer. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

CentOS 8 Stream: new python38 module
by Carl George 11 Mar '20

11 Mar '20

Howdy everyone, The CentOS team is pleased to announce that we have added a python38 module to CentOS 8 Stream. This has been published and is currently propagating out to the mirror network. We're hoping to get developer feedback on this module to help demonstrate the value of Stream and identify any potential issues before they make their way into RHEL and regular CentOS. We've listed some notable features below that python38 provides over the existing python36 module. We won't always announce updated Stream packages like this, but we wanted to highlight some of the early successes as we figure out the Stream workflow. Enjoy! * Built-in breakpoint() * https://docs.python.org/3.7/whatsnew/3.7.html#pep-553-built-in-breakpoint * https://realpython.com/python37-new-features/#the-breakpoint-built-in * Data classes * https://docs.python.org/3.7/whatsnew/3.7.html#dataclasses * https://realpython.com/python37-new-features/#data-classes * Overhauled asyncio module * https://docs.python.org/3.7/whatsnew/3.7.html#asyncio * https://realpython.com/python37-new-features/#asyncio-face-lift * Assignment expressions (walrus operator) * https://docs.python.org/3.8/whatsnew/3.8.html#assignment-expressions * https://realpython.com/python38-new-features/#the-walrus-in-the-room-assign… * F-strings support = for debugging * https://docs.python.org/3.8/whatsnew/3.8.html#f-strings-support-for-self-do… * https://realpython.com/python38-new-features/#simpler-debugging-with-f-stri… -- Carl George

1 0

Minutes for CentOS Board of Directors 2020-02-12
by Karsten Wade 11 Mar '20

11 Mar '20

[These are publishing a little late, I got busy and fell behind partially because the agenda/minutes process has multiple steps where blockages occurred. I'll keep working to improve the underlying process to make the production of these agendas and minutes more reliably consistent.] https://blog.centos.org/2020/03/minutes-for-centos-board-of-directors-2020-… On 2020-02-12 the CentOS Board of Directors met and discussed several ongoing efforts across the Project. The opening discussion was around the new work to evolve the project logo and branding identity being conducted in open channels. Overall the Directors really liked the direction the effort is going and were quite pleased with the open nature of the process. What is needed to bring a conclusion and present a final design for the Board’s approval is the completion of the open design discussion and decision process to be conducted in centos-devel. As the Board is working on adding new Directors and improving governance and transparency, there is an open discussion around the possibility of having a face-to-face meeting of the Board in 2020. This ideally would include an additional day of interactions with other project leadership. One idea floated was to conduct this prior to the CentOS Dojo being planned at CERN in October 2020. At the time of this writing, it is unknown if this Dojo will be affected by COVID-19 related or other travel restrictions. On another topic, in addition to the focused resources of the Community Platform Engineering (CPE) team that supports the CentOS Project in technical ways, Karsten gave a brief explanation of how the Community Architects from the Red Hat Open Source Program Office (OSPO) are in support of the project, specifically Rich Bowen on the community side, Brian Exelbierd on the business interaction side, and Karsten Wade on the strategic and visionary side. >From the Brussels Dojo, Karsten gave a report out about how he had a meeting room for one-to-one discussions with community members. These discussions were an invitation to talk about what works and doesn’t work for users and contributors around the project; an open office hours to hear out anything. It also served to help get an idea of how and why people use CentOS as a platform. This work is to help inform the CentOS 2020 open goals discussion now underway. In support of these efforts, the Board came to the following decisions, resolutions, and agreements: 1. Logo redesign 1. AGREED: Board is requesting Tuomas to lead the discussion on centos-devel toward creating the final /branding redesign proposal for the Board to give final approval on. This process should follow an open decision process of inviting participation, hearing out other ideas, and taking and incorporating feedback on the existing design ideas into the final plan. All this can be done over a reasonable time period of four to eight weeks, so that a decision can be reached that has an opportunity to include voices from across the community. 2. Board face-to-face 1. AGREED: Board will watch the travel situation with an eye toward deciding yay/nay on the face-to-face as the June timeframe approaches. 2. ACTION: Board will request RIch Bowen to coordinate with the Board Secretary on plans for adding meetings around the CERN Dojo. 3. Consent items 1. Adopt minutes from 2020-01-08 meeting 2. Noting that Fabian Arrotin has resigned his role as a CentOS Project Director as of October 2019. 4. Rolling (last from 2020-01-08): 1. Any other topics aka What other things do you want on our master initiatives list? 2. Stepping-up our meeting norms 3. Transparency initiatives Present at the meeting: * Ralph Angenendt * Jim Perrin * Mike McLean * Karsten Wade (Secretary) * Johnny Hughes -- Karsten Wade [he/him/his]| Senior Community Architect | @quaid Red Hat Open Source Program Office (OSPO) : @redhatopen https://community.redhat.com | https://next.redhat.com | https://theopensourceway.org gpg: AD0E0C41 | https://red.ht/sig

1 0

Packages dropping out of modules
by Paul Clifford 10 Mar '20

10 Mar '20

Earlier this month this was a report that softhsm was available but not installable in CentOS 8 due to a "No available modular metadata for modular package" error. The solution was to enable the idm:DL1 module, but my understanding is that modular packages shouldn't be visible while their modules are disabled (this seems to be the behaviour in RHEL 8). Looking in http://mirror.centos.org/centos/8/AppStream/x86_64/os/Packages/ there are two versions of softhsm in the AppStream repository: * softhsm-2.4.0-2.module_el8.1.0+253+3b90c921.x86_64.rpm * softhsm-2.4.0-2.module_el8.1.0+265+e1e65be4.x86_64.rpm The repository's modules.yaml file only describes one version of the module, idm:DL1:8010020200121181805:4a0acb9a:x86_64, which owns the newer package. When idm:DL1 is enabled this masks the older softhsm version but when it's disabled (the default) the newer package is removed from view, and with no repository metadata to indicate that the older softhsm is part of a module it effectively becomes an ordinary member of the AppStream repository. So "dnf install softhsm" offers two different package versions based on whether or not idm:DL1 is enabled, instead of failing with "Error: Unable to find a match" when the module is disabled. You can see a similar thing with the go-toolset module. It's enabled by default and disabling it should hide all of its packages. Instead, because a second version has been published (see the two versions of go-toolset, golang, etc at the earlier URL), disabling go-toolset makes the previous versions of all the packages appear as ordinary members of the AppStream repository. I found https://bugs.centos.org/view.php?id=16808 from around the time of the 8.0 release querying the lack of older version data, and have commented on it, but I wanted to confirm that I haven't misunderstood the expected behaviour. For example, if nodejs:12 receives an update and the earlier package versions drop out into the main AppStream repository it seems that this might cause conflicts for someone installing nodejs from a third party repository, even if they've disabled nodejs:12.

6 8

CPE Weekly: 2020-03-06
by Aoife Moloney 06 Mar '20

06 Mar '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-03-06 Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. ## Fedora Updates * Fedora Minimal Compose is being worked on currently for F32 beta ### Data Centre Move * Please start to plan for 2-3 week outage of communishift starting 2020-04-12 to allow for the move * Due to the data centre move, we cannot get a new box to run odcs-backend https://pagure.io/fedora-infrastructure/issue/8721 * We are also scoping the work required for 'Minimum Viable Fedora' - here is the link to the mail as a refresher of what to expect, and what not https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… Our move dates are as follows: * Move 1 April 13 to IAD2 (essential hardware) * Move 2 April 13 to RDU-CC (communishift) * Move 3 May 11 to IAD2 (QA equipment) * Move 4 June 1 to IAD2 (anything and everything else) ### AAA Replacement * Sprint 5 will see the team focusing on integration with FASJSON API and 2FA token * We have also decided to postpone testing of the new solution until post data centre move to make sure it is * As always, check out our progress on github here https://github.com/orgs/fedora-infra/projects/6 ### CI/CD * Monitor-Gating: Blocked in staging because F32 isn’t branched off there yet (Koji, Bodhi, PDC, https://pagure.io/releng/issue/9293) * Automatic Release Tags and Changelog: Ongoing Devel-list thread here https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… * The team have moved to Jitsi video conferencing with interested community members (ngompa, clime, mboddu, mhroncok) about the different approaches to automatic release tags. Result: Approach considering existing EVRs most palatable (over <#commits>.<#builds>). * We now have a more official looking repo: https://pagure.io/Fedora-Infra/rpmautospec * The team also created implementation details and roadmap: https://hackmd.io/2iQUWeLdR1uTSJ6WL2JqBA ### Sustaining Team * Old cloud is now officially retired * Bodhi XSS vulnerability patched * The team are also looking to prepare a Bodhi 5.2 release * Fedora Minimal Compose (Use ODCS to trigger test composes) * The team are also scoping the Mbbox upgrade and Task breakdown https://github.com/fedora-infra/mbbox/projects/1 * Support community members helping with Badges outage * The teams has started a conversation about Infra Ticket prioritization https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… ## Docs ### Misc Updates/Review Requests * Initial f32-updates-testing push is fixed https://github.com/fedora-infra/bodhi/issues/3936 * Fixed perms on f32 ostree to finish updates pushes * Anitya tests are fixed https://github.com/fedora-infra/anitya/commit/8fe224dbc6b8071f5c5e6f11abe15… * Failing tests in the-new-hotness being resolved https://github.com/fedora-infra/the-new-hotness/pull/273 * Please review Packit integration in the-new-hotness https://github.com/packit-service/packit/issues/689 * Please review KeepassXC flatpak issue https://pagure.io/flatpak-module-tools/issue/6 * Please review Jms-messaging-plugin reviews https://github.com/jenkinsci/jms-messaging-plugin/pull/162 ## CentOS Updates ### CentOS * Ppc64le kickstarter added for CentOS 8 * This will still need to be tested and added in production * The infrastructure is stable overall though! ### CentOS Stream * We are now working on the sync-to-git process * Tycho module was successfully added to Stream in development! * We are also getting closer to having a contributor workflow model available for later this year - watch this space! * We are also working with upstream to generate reports for Stream too As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Update: CentOS Dojo at Facebook postponed
by Rich Bowen 05 Mar '20

05 Mar '20

Due to the change in the status of Red Hat Summit (https://www.redhat.com/en/blog/moving-red-hat-summit-2020-virtual-experience) we have made the decision to postpone the CentOS Dojo at Facebook to a later date. Many of our potential speakers, as well as many of our attendees, had travel plans that were dependent on attendance at Red Hat Summit, and without that event happening they are no longer able to travel. If you have already registered for the event, we encourage you to stay registered, so that we have an easy way to contact you about event updates through Eventbrite. We do still plan to hold an event at Facebook, but, due to the current corona virus situation, we are holding off on making any firm plans until the danger has passed. We thank you for your patience and understanding, and hope to see you when we reschedule. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Fwd: [EPEL-devel] gnu-free-fonts-20120503-18.el8.0.1 still not tagged into dist-c8-compose
by Troy Dawson 05 Mar '20

05 Mar '20

Sending this to the correct mailing list. ---------- Forwarded message --------- From: Mattias Ellert <mattias.ellert(a)physics.uu.se> Date: Wed, Mar 4, 2020 at 11:17 PM Subject: [EPEL-devel] gnu-free-fonts-20120503-18.el8.0.1 still not tagged into dist-c8-compose To: <epel-devel(a)lists.fedoraproject.org> Hi. I was asked to repost a thread from the CentOS forum on this mailing list: Sorry for starting a new thread. But there has not been any activity on the old thread for a month (2020-02-05) except for my request for a status update a week ago (2020-02-26) for which there was no reply. Can someone please tag the update so that it can be installed by users. The packages available to users are still broken, even though the update was built almost two month ago (2020-01-07). For details please see the previous threads and bug reports: https://forums.centos.org/viewtopic.php?f=54&t=73346 https://forums.centos.org/viewtopic.php?f=54&t=72682 https://bugs.centos.org/view.php?id=16759 https://bugs.centos.org/view.php?id=16523 The bug was first reported 2019-10-03 and the fixed packages were built 2020-01-07 but are not yet available for installation/update and the bug still affects users. And before someone replies "should be fixed in RHEL first" before reading the references above - this is a CentOS only bug that never existed in RHEL. Mattias _______________________________________________ epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraprojec…

1 0

Agenda Board of Directors meeting 2012-02-12
by Karsten Wade 04 Mar '20

04 Mar '20

== agenda 2020-02-12 From: https://blog.centos.org/2020/02/agenda-for-centos-board-of-directors-meetin… 1. Do Directors have any questions or concerns about the process being followed to update the CentOS Project logo? Full story in this blog post by Tuomas Kuosmanen: https://blog.centos.org/2020/01/updating-the-centos-logo-and-visual-style/ 1. Specific design concerns should be handled on centos-devel or in the design repo discussion. 2. Having a face-to-face Board and/or leadership meeting in or near Paris in Summer 2020. What month might be good for Directors? 3. Directors and other Project leaders are invited and encouraged to collaborate with the now four community architects from Red Hat working in/around the CentOS Project: Rich Bowen, Brian Exelbierd, Tuomas Kuosmanen, and Karsten Wade. 4. Report out from Karsten on the Board interview/working session room at the Brussels CentOS Dojo. 5. Consent items: 1. Adopt minutes from 2020-01-08 meeting 2. Noting that Fabian Arrotin has resigned his role as a CentOS Project Director as of October 2019. 6. Rolling (last from 2020-01-08): 1. Any other topics aka What other things do you want on our master initiatives list? 2. Stepping-up our meeting norms 3. Transparency initiatives == notes/thoughts Hi all, travel and the awesome CentOS Dojo in Brussels caught me a few days behind on finishing the agenda for this meeting. Honestly, my processes are still evolving over how late to bring in items, keep adding until the last hours, and/or when to call a cut-off and publish. You can read Rich's report of the Dojo here: https://blog.centos.org/2020/02/event-report-centos-dojo-brussels-jan-31-20… Video from Dojo presentations has begun to be available in our YouTube channel: https://www.youtube.com/channel/UC-IoMrffK5xG1UI-skkTlcA -- Karsten Wade [he/him/his]| Senior Community Architect | @quaid Red Hat Open Source Program Office (OSPO) : @redhatopen https://community.redhat.com | https://next.redhat.com | https://theopensourceway.org gpg: AD0E0C41 | https://red.ht/sig

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel March 2020