devel March 2020

devel@lists.centos.org

43 participants
31 discussions

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel March 2020