devel April 2020

devel@lists.centos.org

44 participants
38 discussions

Meeting minutes of today's Storage SIG gathering
by Niels de Vos 07 Apr '20

07 Apr '20

Hi all, Today we had our monthly CentOS Storage SIG meeting again. The agenda is available at https://hackmd.io/Epc35JIESaeotoGzwu5R5w and is open for topics we'll discuss next time. The time of the meeting will likely change. A bit later in the day would allow contributors from the US to join as well. Details on that will follow at a later point on this list. Once a decision on the new time has been made, the CentOS Calendar at https://centos.org/community/calendar/ will be updated too. Cheers, Niels Meeting started by ndevos at 10:06:34 UTC. The full logs are available at https://www.centos.org/minutes/2020/April/centos-meeting.2020-04-07-10.06.l… . Meeting summary --------------- * attendees (ndevos, 10:07:03) * agenda (ndevos, 10:08:46) * Change the Meeting Time? (ndevos, 10:10:02) * ACTION: fmount will send a poll to the -devel list about the best time for the monthly meeting (ndevos, 10:14:04) * AGREED: the new meeting time will be in effect for the May gathering (ndevos, 10:15:12) * building centos-release packages for CentOS 8 (ndevos, 10:15:31) * Open Floor (ndevos, 10:22:21) Meeting ended at 10:24:48 UTC. Action Items ------------ * fmount will send a poll to the -devel list about the best time for the monthly meeting Action Items, by person ----------------------- * fmount * fmount will send a poll to the -devel list about the best time for the monthly meeting * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * ndevos (37) * fmount (24) * gfidente (8) * centbot (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Please update repodata
by Akemi Yagi 06 Apr '20

06 Apr '20

Forwarding: From: Tetsuo Handa <penguin-kernel(a)i-love.sakura.ne.jp> Subject: Please update repodata Date: Thu, 2 Apr 2020 15:53:23 +0900 +++++++++++++++++++++++++++++++++++++++ Hello. Please update repodata in the following directories. http://debuginfo.centos.org/6/i386/repodata/ http://debuginfo.centos.org/6/x86_64/repodata/ http://debuginfo.centos.org/7/x86_64/repodata/ There may be other directories, but I didn't check them. Also. I found a line baseurl=http://vault.centos.org/$contentdir/$releasever/BaseOS/Source/ in /etc/yum.repos.d/CentOS-Sources.repo for CentOS 8 which makes it impossible to download latest source rpm files. If I change that line to baseurl=http://vault.centos.org/8.1.1911/BaseOS/Source/ , I can download latest source rpm files. Regards.

2 1

CPE Weekly: 2020-04-04
by Aoife Moloney 04 Apr '20

04 Apr '20

# CPE Weekly 2020-04-04 --- 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. Check out our teams info here https://docs.fedoraproject.org/en-US/cpe/ ## GitForge Updates Idea for note: *There has been a lot of discussion this week on the devel and infra lists about the decision to move to GitLab in the near future. Firstly, let us apologize again to the communities for our drop in communication between the requirement collecting phase and the decision making phase. As we have said before, it was in no way, shape or form an intentional lapse of communications. However we do recognize that it was still nonetheless a decision that was not made in public, and for that we can only now offer our apologies for this mistake and learn a hard lesson from it. We do want to let you know that we deeply appreciate the requirements you have given us and would like to ask you to continue engaging with us while we are moving through our next steps with GitLab. While the discussions on the lists are deeply emotional, they are still incredibly valuable to us to truly comprehend the importance of our next steps in ensuring we make the right choices in the coming months. Now more than ever, your guidance is needed to make sure we achieve the best possible result for you and our team from this decision. CPE management and I, our team's product owner, are also actively engaging with the Fedora Council and soon the CentOS Board to make sure that ALL of the developments and progress between us and GitLab are publicly available. We have a long way to go in this process and your feedback on our progress will be vital to make sure we remain on course. We hope in time you can understand our decision was made in good intent for the betterment of both our team and the communities we serve, and we hope to still be able to rely on you all as peers and friends for feedback and guidance during this journey.* ## CentOS Updates ### CentOS * CentOS CI is stable with 0 downtime! * RHEL 7.8 released this week too! ### CentOS Stream * qt5, go-toolest (module), container tools (module) are updated to their 8.2 versions * We are also looking at easier automation of koji tags ## Fedora Updates * Final Freeze starts 7th April 2020 @ 1400 UTC * Pagure 5.9.1 release pushed to both staging and pagure.io * the-new-hotness configuration was updated https://pagure.io/fedora-infrastructure/issue/8783 * Michal Konečný has been working on mapping the fedora infrastructure applications, his project, (which sounds really cool and useful!) can be found here https://github.com/Zlopez/fedora-infra-map ### Data Centre Move * Please note Communishift will be down from 13th April - 8th May to facilitate the first shipment wave of our datacenter * We are also still on track to switch to a reduced Fedora offering from 25th May until est. 1st July\*. * For a list of services we are planning to have available during this window, please see mail thread in archive https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… * We will not have staging available so we will not have capacity to review or deploy new or upgraded features and applications during this time. * As always, please view our public schedule here for more a more detailed overview https://hackmd.io/@fedorainfra2020/rJpsA4FLL#First-draft-of-schedule-for-PH… * We found a password, we do not know whose it is, but we have turned it into the lost and found. ### AAA Replacement * First development phase complete & the team worked through 57 tickets in total * The codebase was sent to our team first for demo and we will be using feedback to develop the portal further * During phase two we would like to change some codebases in existing apps, and write documentation on how to upgrade applications to redirect to the new API * We would like to roll this request for feedback out to some community maintainers during this phase too for another iteration on the service and documentation * Our work is publicly tracked here https://github.com/orgs/fedora-infra/projects/6 so please stop by and check out the progress we are making, and what we are looking at working on next ### CI/CD * Monitor-gating is still running in production and giving us some data about the health of the packager workflow: * For example, these are the statistics between Monday and Wednesday: 39 messages retrieved prod.monitor-gating.multi-build.end.failed -- 7 prod.monitor-gating.multi-build.end.succeeded -- 2 prod.monitor-gating.multi-build.start -- 10 prod.monitor-gating.single-build.end.failed -- 3 prod.monitor-gating.single-build.end.succeeded -- 7 prod.monitor-gating.single-build.start -- 10 * rpmautospec 0.0.1 through 0.0.10 have been released and deployed in staging * We got two builds to go through fine, from the same commit, getting two different NEVR and an auto-generated changelog * However, for this to happen, we had to tweak a couple of things on the builder which is not really ideal/acceptable, so we moved a part of the processing inside the chroot where the SRPM will be built, which solved the main issues we faced * To be done: Make tagging (latest) existing builds a separate operation executed outside the build root, to avoid having to talk to Koji inside it. * In other words: Stay put, we're getting there! ### Sustaining Team * Mbbox * The team have made some progress on koji-builder CRD * The team are also working on Bodhi 5.3 with few improvements and bug fixes from 5.2. * The team had a reboot and Update cycle this week. * The team are also discussing ideas around a releng bot to help process the tickets that require manual interventions. * They also add more updates to compose-tracker * And started playing with odcs on new odcs-backend-releng01.phx2.fedoraproject.org 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/gSci385uRoeNVEuoNUS1pg?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

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 Stream source rpms
by lejeczek 02 Apr '20

02 Apr '20

hi guys. Is there a problem with Stream rpms? These are not in the repos, right? many thanks, L.

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel April 2020