Fedora+Lenovo
by Mark Pearson
Hi all,
Adam Williamson suggested I stick a note in the mailing list saying “hi” - so I’ve achieved that and officially upgraded myself from lurker! He also suggested I take questions from the community - and I’m very happy to do that.
So - if there are any questions from Fedora developers on the Lenovo announcement let me know and I will answer them as best I can….if I don’t know the answer I’ll do the try to find out.
I will lurk around the mailing list but generally if there is anything that might be important for Lenovo to look at/respond to/etc and I don’t respond do feel free to send me a note directly saying “Look at the mailing list” 😊
Mark
4 years, 1 month
CPE Weekly: 2020-04-26
by Aoife Moloney
# CPE Weekly: 2020-04-26
---
title: CPE Weekly status email
tags: CPE Weekly, email
---
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
* We will be tracking our progress here
https://fedoraproject.org/wiki/Git_forge_update
* Please be aware this does not contain any new information, as we
don't have any to share yet.
* However once we have more information for you, we will be posting it
to the above link, and with the URL in the weekly emails for quick
access.
* We are currently doing a technical deep-dive with our own team on
what we need from GitLab
* We are also still engaging with Fedora Council who are tracking the
Fedora Communities needs here
https://pagure.io/Fedora-Council/tickets/issue/292
* And we are looking at ways to engage closer with the CentOS
community too to share information as and when we have it
* Public Q&A sessions are still being discussed to allow for open
conversations in public forums too as we move through this journey, so
thank you for your patience with us.
## Fedora Updates
* F32 release is a Go!
* Estimated release date is April 28th - well done to everyone involved!
### Data Centre Move
* Due to Covid-19 restrictions at each datacentre, we have
unfortunately experienced a delay during the initial move.
* The need to push out our dates by 2-3 weeks was made necessary on
Thursday 23rd April, following meetings with Red Hat IT on network
connectivity status and estimate connection times for our team to
access the new datacentre.
* We will need to adjust our outage schedule and move schedule to
properly reflect the new dates of services being turned off and
reduced, and the full amended schedule will be published to hackmd,
with emails sent to the devel-announce & infra lists next week (week
ending 1st May)
* We will also include links to the updated move schedule and service
impact schedule in next weeks CPE Weekly
* Please be aware that CommuniShift is now down indefinitely until
earliest May 8th.
### AAA Replacement
* The team have begun phase two of the project and you can view their
board for more technical information on their work here
https://github.com/orgs/fedora-infra/projects/6
* They are doing amazing work :)
### 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
* 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
* Plan is still to get it deployed in staging
### Sustaining Team
* Mbbox Upgrade
* Some progress on CRD for koji-builder and koji-hub components
* Bodhi 5.2.2 released
* Some issues with celery tasks, however rawhide monitoring super useful.
* Compose tracker enhancement
* Focusing on tagging issues, and having the ability to ping maintainers
Odcs-backend-releng01 provision to enable testing in Fedora Minimal Compose
* 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
* 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 on 25th April 2020
### CentOS Stream
* Summit Videos took our attention this week
* We have a booth, so don't forget to register your attendance!
https://www.redhat.com/en/summit
* Qt5.12 pushed in response to an internal request
* NetworkManager re-imported
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 week ahead!
Aoife
Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
4 years, 1 month
games group in comps
by Kevin Fenzi
Greetings.
There's a ticket https://pagure.io/fedora-comps/issue/492 (formerly a
bug) that the games group in comps has nothing in it.
Thats not quite the case, it has a ton of games in it, but they are all
optional. ;(
I have no much horse in this race, but I thought I would see if folks
here had ideas to improve this.
Right now, 'dnf group install games' just doesn't do anything.
Should it? Which games should it have? Does someone want to curate it?
Does anyone know why they are all optional there?
kevin
4 years, 1 month
F32 s390x: ICE: attempting to access a gcc command line option that
is not stored in global_options
by Miro Hrončok
I am getting hundreds of warnings/errors on s390x on Fedora 32:
https://koji.fedoraproject.org/koji/taskinfo?taskID=44118042
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
debugging: index = 853 max = 1773
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: attempting to access a gcc command line option that is not stored in
global_options
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: Please contact the annobin maintainer with details of this problem
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
debugging: index = 853 max = 1773
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: attempting to access a gcc command line option that is not stored in
global_options
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: Please contact the annobin maintainer with details of this problem
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
debugging: index = 853 max = 1773
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: attempting to access a gcc command line option that is not stored in
global_options
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: Please contact the annobin maintainer with details of this problem
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
debugging: index = 853 max = 1773
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: attempting to access a gcc command line option that is not stored in
global_options
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: Please contact the annobin maintainer with details of this problem
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
debugging: index = 853 max = 1773
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: attempting to access a gcc command line option that is not stored in
global_options
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: Please contact the annobin maintainer with details of this problem
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
debugging: index = 853 max = 1773
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: attempting to access a gcc command line option that is not stored in
global_options
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: Please contact the annobin maintainer with details of this problem
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
debugging: index = 853 max = 1773
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: attempting to access a gcc command line option that is not stored in
global_options
annobin:
/builddir/build/BUILD/Python-3.9.0a6/Tools/peg_generator/peg_extension/peg_extension.c:
ICE: Please contact the annobin maintainer with details of this problem
annobin: /tmp/tmpznfmbwgi/parse.c: debugging: index = 853 max = 1773
annobin: /tmp/tmpznfmbwgi/parse.c: ICE: attempting to access a gcc command line
option that is not stored in global_options
annobin: /tmp/tmpznfmbwgi/parse.c: ICE: Please contact the annobin maintainer
with details of this problem
annobin: /tmp/tmpznfmbwgi/parse.c: debugging: index = 853 max = 1773
annobin: /tmp/tmpznfmbwgi/parse.c: ICE: attempting to access a gcc command line
option that is not stored in global_options
annobin: /tmp/tmpznfmbwgi/parse.c: ICE: Please contact the annobin maintainer
with details of this problem
annobin: /tmp/tmpznfmbwgi/parse.c: debugging: index = 853 max = 1773
annobin: /tmp/tmpznfmbwgi/parse.c: ICE: attempting to access a gcc command line
option that is not stored in global_options
annobin: /tmp/tmpznfmbwgi/parse.c: ICE: Please contact the annobin maintainer
with details of this problem
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
4 years, 1 month
When did journalctl change to volatile without my knowledge?
by Richard Shaw
Did I miss a change notification at some point?
I'm used to seeing a significant date range of data from journalctl but
upon checking today, well I only see today...
Digging further it said I don't have a persistent storage or something
setup.
So journalctl.conf is setup for "auto" which means that if /var/log/journal
doesn't exist, treat it as volatile, but if /var/log/journal does exist,
then treat it as persistent.
When did this change? I never removed /var/log/journal....
Thanks,
Richard
4 years, 1 month