hi everyone.
dnf updates collide:
$ dnf update corosynclib
Last metadata expiration check: 0:19:02 ago on Fri 17 Apr
2020 14:57:48 BST.
Error:
Problem: problem with installed package
corosync-3.0.2-3.el8_1.1.x86_64
- package corosync-3.0.2-3.el8_1.1.x86_64 requires
corosynclib(x86-64) = 3.0.2-3.el8_1.1, but none of the
providers can be installed
- cannot install both corosynclib-3.0.3-2.el8.x86_64 and
corosynclib-3.0.2-3.el8_1.1.x86_64
- cannot install the best …
[View More]update candidate for package
corosynclib-3.0.2-3.el8_1.1.x86_64
(try to add '--allowerasing' to command line to replace
conflicting packages or '--skip-broken' to skip
uninstallable packages or '--nobest' to use not only best
candidate packages)
$ dnf list corosynclib --showduplicates
Last metadata expiration check: 0:18:45 ago on Fri 17 Apr
2020 14:57:48 BST.
Installed Packages
corosynclib.x86_64
3.0.2-3.el8_1.1
@AppStream
Available Packages
corosynclib.i686
3.0.2-3.el8
AppStream
corosynclib.x86_64
3.0.2-3.el8
AppStream
corosynclib.i686
3.0.2-3.el8_1.1
AppStream
corosynclib.i686
3.0.2-3.el8_1.1
HighAvailability
corosynclib.x86_64
3.0.2-3.el8_1.1
AppStream
corosynclib.i686
3.0.3-2.el8
Stream-AppStream
corosynclib.x86_64
3.0.3-2.el8
Stream-AppStream
It cannot be that those(some of?) repos exclude each other,
right?
many thanks, L.
[View Less]
Hi CentOS developers, especially Cloud SIG team,
tl;dr: I need some help in packaging Python3 packages available in PyPI for CentOS 7.
Details:
we are a public cloud provider based on OpenStack and many of our customers and partners unfortunately still request CentOS 7 images for their VMs. In my team we support the upstream development of OpenStack SDK and OpenStack Client (both seem to be de facto one combined team now) and also provide some extensions specific to our cloud (via a plugin …
[View More]mechanism in recent releases of the SDK).
Our clients frequently ask for updated RPMs for CentOS 7. I wonder if you as CentOS community at large are interested in having them as well, or, if not, if you could point me in the right direction how to build them.
One major conflict I am currently struggling with is that virtually all Python 2.7 code is not only no longer supported (due to a community goal in OpenStack), but actually removed (which is in itself a good decision, no doubt about it). The mentioned packages work well with Python 3, but as I understand it, Python 3 is not available by vanilla CentOS 7.
The affected packages are available in PyPI:
* https://pypi.org/project/openstacksdk/ (version 0.46.0)
* https://pypi.org/project/python-openstackclient/ (version 5.2.0, not to be confused with "openstackclient" without the "python-" prefix, which is stuck at 4.0.0)
* https://pypi.org/project/otcextensions/ (version 0.6.9, but this our own business)
They are all easily installed with "pip" once you have a Python 3 environment, but draw a total of 100 other packages as dependencies. Could you please advise how to proceed if someone insists on RPMs for those?
Thank you + Regards,
/Nils
[View Less]
---
title: CPE Weekly status email
tags: CPE Weekly, email
---
# CPE Weekly 2020-04-18
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Check out our
team's info here https://docs.fedoraproject.org/en-US/cpe/
## GitForge Updates
We are still actively engaging with the Fedora Council and have not
made any further progress with this project. We are focusing on
ensuring we have captured the most granular of …
[View More]requirements before
further engaging with GitLab by rereviewing what we have gathered so
far and requesting more specific technical clarifications on some.
We are also as a team discussing the best way to track the updates on
this project publicly and hope to have something published early next
week. We will send an email to the devel list as soon as we have
agreed and created this.
Thank you for your patience and engagement with us thus far.
## Fedora Updates
* Fedora 32 release: RC 1.3 was tested this week
* Go/No-Go meeting happened on Thursday 16th April - decision:No Go
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…
### Data Centre Move
* Please note Communishift is now down and is en route to the
datacentre in RDU-CC.
* We have a list of affected services that will be in effect from May
25th - July 1st (est) as part of the full datacentre move. You can
view that list here https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA
* 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…
### AAA Replacement
* The team officially kicked off phase two of the project development today.
* They are going to look at applications that currently use the FAS
client to change their codebase to the FASJSON client post production.
* The team are also working on adding a python library to the API so
that this maps to python objects easily.
* They are also working on API endpoints, specifically to be able to
retrieve the open-api specification in JSON format & provide a health
endpoint for monitoring tools.
* Our work is publicly tracked here if you want to find out more
https://github.com/orgs/fedora-infra/projects/6
### CI/CD
* rpmautospec is available for testing in staging, find more info here
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…
### Sustaining Team
* The team are looking at creating a ticket dashboard for tickets and
have reused most the fedora-gather-easyfix code base to work on this
* https://fedorapeople.org/~humaton/cpe/
* Some cool stats about tickets from the infra repo here
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr…
* Mbbox:
* Review koji-hub CRD PR
https://github.com/fedora-infra/mbbox/pull/19
Starting to play around with koji-ansible collections for releng work (here).
Automation of the openh264 packages.
## CentOS Updates
### CentOS
* CentOS CI - stable with 0 downtime
* 7.8 QA tree is being tested by CentOS QA folks
### CentOS Stream
* The team are working on having Stream be publically consumable in
the coming months, with SIG enablement so watch the devel lists for
more technical updates as and when they are announced!
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
[View Less]
> Message: 8
> Date: Tue, 31 Mar 2020 13:36:45 -0700
> From: Troy Dawson <tdawson(a)redhat.com>
> To: "The CentOS developers mailing list." <centos-devel(a)centos.org>
> Subject: [CentOS-devel] New KDE available for testing on CentOS Stream
> Message-ID:
> <CAKndyUTRpN_fsqs2o1CGbnGSOMAtmOso=rJS3mjxp4masnqQhw(a)mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> CentOS Stream has recently been updated to include the updated
> …
[View More]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.
Hey Troy now the qt packages have been updated to 5.12 do we have a
date for the 8.2 release as I'd like to just "dnf groupinstall KDE"
for a shiny new ( stable ) desktop but right now this will fail :-(
Thanks !
[View Less]
When I joined Red Hat in 2013, it was to help CentOS facilitate open
source communities such as RDO, oVirt, and others. In the years since,
my goal grew to include helping Red Hat develop more openly, and to help
align the value CentOS provides with the needs of Red Hat.
With Red Hat’s increased investment, focus, and interest in CentOS
Stream, I feel like this has been successful. While the work is far from
finished, I’m confident that the CentOS team in coordination with other
RHEL teams …
[View More]will see it through. Much like Mary Poppins, when people
you’re helping are doing the right things, it’s time to move on.
Therefore, I intend to leave Red Hat, and my last day will be May 8th.
While I’ve very much enjoyed causing trouble at the Hat, it’s time for
me to put this skill to use elsewhere. Don't worry or read too much into
this. I’m not going far, and I’ll still be active in the community.
--
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
[View Less]
Hello everyone,
as per last meeting I'm writing to get feedback on what the best meeting
time would be for all
parties interested in participating in the Centos Storage SIG meeting.
Currently we have a monthly scheduled meeting on Tuesday at 1000 UTC, but
sounds like it's not
ideal for a bunch of folks and we should consider changing it to allow a
wider audience.
For this reason I've created a doodle that will run for one week [1].
In this Doodle, I'd like folks to vote on whatever time works …
[View More]best for
them, then we can just
choose the time with the highest number of votes and change the calendar
accordingly.
Note:
I excluded 1400 and 1500 UTC from this doodle since two meetings are
running at that time [3].
@Giulio Fidente <gfidente(a)redhat.com> and @Niels de Vos <ndevos(a)redhat.com> if
anything is missing.
Thanks,
Francesco
[1]
https://www.centos.org/minutes/2020/April/centos-meeting.2020-04-07-10.06.h…
[2] https://doodle.com/poll/pixtyzsxwemny48s
[3] https://centos.org/community/calendar/
--
Francesco Pantano
GPG KEY: F41BD75C
[View Less]
# CPE Weekly: 2020-04-14
---
title: CPE Weekly status email
tags: CPE Weekly, email
---
Hi All,
Apologies for the delayed weekly mail, I enjoyed a lovely four-day
weekend with my family over Easter which was important and didn't get
around to sending this email.
The upside is you get two emails from me this week instead :)
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:…
[View More]//docs.fedoraproject.org/en-US/cpe/
## GitForge Updates
* Initial conversations have started with GitLab to investigate
options and weight them against more refined requirements to make sure
we reach the best possible outcome
* We are still engaging with Fedora Council
https://pagure.io/Fedora-Council/tickets/issue/292
* We are also engaging with the CentOS board too
* And we are looking at ways to have open conversations/Q&A sessions
in public forums too as we move through this journey.
## Fedora Updates
* F32 release first go/no-go meeting is scheduled for this week to
review the estimated release date of 21st April
* Calendar for meetings here
https://apps.fedoraproject.org/calendar/Fedora%20release/
* F32 release schedule here https://fedoraproject.org/wiki/Releases/32/Schedule
### Data Centre Move
* CommuniShift is now down until May 8th est. to facilitate the data
centre move that has now officially begun.
* Please see our list of affected https://hackmd.io/hpYYJQRjQy-oHxUS7IonIA
* Our first few sets of hardware have been deracked and are awaiting
collection from PHX2 this week.
* Please check our schedule here - we are on Week 06
https://hackmd.io/R3EkjzVyTG2TYwQvkfzYrA
### AAA Replacement
* The team are planning phase two of the replacement which will target
UX/UI improvements,
### CI/CD
* rpmautospec
* Call for testers has been sent to the devel-announce list:
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…
* Documentation is also being refined on:
* How it works
* What are its peculiarities
* How to opt-in
* What is working and what isn't yet
* What remains to do before this gets pushed to production
* Thank you for your feedback!
### Sustaining Team
* Mbbox Upgrade
* The team are making good progress on the koji-builder & koji-hub
CRD https://github.com/fedora-infra/mbbox/pull/20
* They also have resolved the issue with PVC in the mbox-operator
https://github.com/fedora-infra/mbbox/pull/23
* We are now looking into CI support and the work that this will involve
* Bodhi
* Investigation database lockups, seems related to celery worker
not completing their tasks
* Working on a 5.3 release
* Releng
* fedscm-admin 1.0.13 released
* Future openh264 composes will use ODCS, script is added to releng repo
* Infra
* The daily standup the team has has helped a lot with managing
infra tickets - they are down to 99 tickets!
* Mass update of stg and prod
* Please note you may experience some Kojira slowness
* New review-stats application deployed -
(https://fedoraproject.org/PackageReviewStatus/)
## CentOS Updates
### CentOS
* CentOS CI is stable and all working fine
* Investigation for cloud vms addition to cico is also underway
* RHEL 8.1 batch update 07-Apr
### CentOS Stream
* We have now ~200 packages built in CentOS Stream & we expect a few
hundred more to become available to us soon!
* The team are also still working on general compose config, koji tag
& housekeeping :)
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
[View Less]
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:…
[View More]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
[View Less]
Hi,
The CentOS Governing Board of Directors is pleased to appoint two new
Directors to be added to the Governing Board, effective 8th April 2020:
Thomas Oulevey [1] and Patrick Riehecky [2]. The community will
instantly recognise both from their long standing and well established
support for the CentOS Project over the years, initially as consumers
and community participants, and in more recent times as active across
various initiatives in and around the project space.
Over the last …
[View More]sixteen years the CentOS project has established itself
as a critical component in the open source ecosystem online. In order to
maintain this leading role and help drive success for the wider open
source ecosystem, we are moving to a more contributor-centric model. A
key part of enabling this goal is to evolve our transparent governance.
Pat and Thomas have shown keen interest in participating in this
specific endeavour, and we are excited to welcome them to the team,
helping us get there.
Thomas (alphacc) works in the Controls group within the CERN Beams
department [3]. He has contributed to the CentOS Project since 2012, as
a member of the infrastructure team. He helped to bootstrap a few
Special Interest Groups, helped the QA team with reports, and now mainly
designs and improves the Community Build Service [4]. Thomas’s sponsor
on the Board is Mike McLean, who will help oversee his transition to
project leadership.
Patrick (jcpunk) works at Fermi National Accelerator Laboratory [5].
He is part of the Scientific Linux team [6] and works on systems that
perform Data Acquisition for various experiments at Fermilab. Although a
long time member of the community, formally Pat began working with the
CentOS Community when Fermilab decided to use CentOS 8 [7] as its
EL8-base platform. Pat’s sponsor is Johnny Hughes, who will help oversee
his transition to project leadership.
Please join me in welcoming them to the team,
Regards
Karanbir Singh
Project Lead, The CentOS Project
[1] https://wiki.centos.org/ThomasOulevey
[2] https://wiki.centos.org/PatrickRiehecky
[3] https://beams.cern
[4] https://cbs.centos.org
[5] https://beams.cern
[6] https://www.scientificlinux.org/about/who-makes-scientific-linux/
[7]
https://listserv.fnal.gov/scripts/wa.exe?A2=SCIENTIFIC-LINUX-ANNOUNCE;11d60…
[View Less]