Due to CentOS Connect, FOSDEM, and general travel, the CentOS Board
didn't get notice out for the February meeting. There was no official
meeting, although there was a video chat. Nonetheless, we'll hold our
monthly board office hours this Thursday, February 16, 15 15:00 UTC.
https://us06web.zoom.us/j/81819497130?pwd=WTQxNDdYS1UwK3RzdTdxeGRIMjRBUT09
Thanks,
Shaun
Due to a mandatory network maintenance at the RDU2 (Community Cage)
facility/DC, we'll have to power off some CentOS infrastructure
components hosted in that DC.
Impacted services:
- https://cbs.centos.org (impossible to submit any build, nor push to
delivery network)
- https://bugs.centos.org
- ns1.centos.org
- https://wiki.centos.org
- all centos linux / stream 8 / stream 9 release engineering workflow
(stream 9 can be built but not pushed out, while for the rest, all will
be down)
- https://git.centos.org
- CI infra:
- while openshift in aws is self-contained, there will be no way to
request duffy nodes for tests
- tenants still on legacy openshift (hosted in that DC) will see the
whole cluster being powered down (because of Persistent Volumes hosted
in a NFS server that itself will be unavailable)
- various other services
Migration is scheduled for """"Tuesday January 31th, 1:00 pm UTC time"""".
You can convert to local time with $(date -d '2023-01-31 13:00 UTC')
The scheduled maintenance window (communicated to us) is estimated to
4h, but we'll restart infra services as soon as possible, following
ourselves the current status internally.
Thanks for your understanding and patience.
on behalf of the Infra team,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Hi, so we're working on testing some CentOS Stream 9 stuff for OpenShift, and we use openvswitch by default.
Today, the repo only seems to build for x86_64. I looked at https://wiki.centos.org/SpecialInterestGroup/NFV but I don't see anything there that gives me links to any *source code* where I could change this. I'd guess there's something like a limited set on the koji tag?
Hi CentOS team,
By the RPM spec files, (https://gitlab.com/redhat/centos-stream/rpms/systemd/-/blob/c9s/systemd.spe…) FIDO2 support is disabled in systemd. FIDO2 support is very useful for automatic decryption of LUKS partitions with systemd-cryptsetup. This would allow for external security keys (such as a Yubikey) to decrypt drives with no user interaction. Currently, the current systemd configuration supports only TPM and GPG. In older devices that don't support TPM, the only option for no-interaction FDE decryption is to use GPG (which still requires a key access password to be remotely secure).
As far as I can tell, there is no barrier to enable FIDO2 support. Please let me know if I am mistaken.
Thanks,
Ersei
I plan on making two changes to the current EPEL KDE Update Schedule.[1]
** First: EPEL 8 KDE Plasma Desktop is going to stay at the releases that
they currently are at. We will backport major security fixes. Bugs and
bugfixes will be best effort. But we will not do any across the board
updates.
This is due to the older libraries in RHEL 8. We've hit the limit that the
newer KDE versions can run on the older libraries.
EPEL 8 will have these versions (with a few exceptions)
plasma - 5.24
kf5 - 5.96
kde apps - 22.04 / 21.12 / 21.08 and some 21.04
qt5 - 5.15
**Second: We will do the across the board updates to the main epel branches
[2] every six months instead of once a year. They will coincide with each
RHEL minor release, instead of every other RHEL minor release.
With the last release, we found that KDE packages like to build on
themselves. Meaning that some 22.04 packages needed a previous version of
at least 21.08 to build. That was fine on epel-next where we had updated
each six months. But when we tried to build on plain epel8 or epel9,
things got complicated.
Doing a release every six months will allow users to get the newer updates
faster. And although it sounds counter-intuitive, it will save the
maintainers time.
We haven't officially made this change yet. So if anyone sees any issues
and/or problems. Please let us know.
Thank You
Troy Dawson
Fedora KDE SIG
[1] - https://fedoraproject.org/wiki/SIGs/KDE/EPEL#Update_Schedule
[2] - Currently epel9, but epel10 when it comes out
Hi folks,
I've just opened up registration to join CentOS Connect from the
comfort of your home. We will have a live stream and a virtual hallway
track for remote participants, and our live stream monitor will relay
questions to the speakers.
Registration details on the web:
https://connect.centos.org/
Thanks,
Shaun
Hello everyone,
Anaconda team would like to ask you for your feedback. We are trying to
design the storage partitioning for the new Web UI correctly and for
that we would like to find out how you use your storage. Please help us
by filling in this questionnaire so we can make correct decisions!
The link to the questionnaire is in the blog post here:
https://fedoramagazine.org/anaconda-web-ui-storage-feedback-requested/#comm…
Best Regards,
Jirka