fidzu : Fedora

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

Week: 28th October - 1st November 2024

Infrastructure & Release Engineering

The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It's responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues

Fedora Infra

• In progress:
  • Need OIDC credentials for fedora magazine in staging
  • Retirement of `monitor-dashboard` tracker
  • Create a POC integration in Konflux for fedora-infra/webhook-to-fedora-messaging
  • Retirement of `monitor-gating` tracker
  • setup ipa02.stg and ipa03.stg again as replicas
  • Move OpenShift apps from deploymentconfig to deployment
  • RFE: fedoras container image register change
  • The process to update the OpenH264 repos is broken
  • httpd 2.4.61 causing issue in fedora infrastructure
  • Support allocation dedicated hosts for Testing Farm
  • Mailman deployment memory spikes
  • Searching mailing list archives does not work
  • EPEL minor version archive repos in MirrorManager
  • vmhost-x86-copr01.rdu-cc.fedoraproject.org DOWN
  • Update DRAC Firmware on All Dell Servers
  • Recurring issue that Bugzilla stops sending messages to fedora-messaging
  • Cleaning script for communishift
  • rhel7 eol
  • move resultsdb-ci-listener deployment pipeline
  • rhel7 EOL - github2fedmsg
  • Setup RISC-V builder(s) VM in Fedora Infrastructure
  • Move from iptables to firewalld
  • Help me move my discourse bots to production?
  • fedmsg -> fedora-messaging migration tracker
  • rhel9 adoption
  • Create monitoring tool for rabbitmq certificates
  • Replace Nagios with Zabbix in Fedora Infrastructure
  • Migration of registry.fedoraproject.org to quay.io
  • Commits don't end up on the scm-commits list
• Done:
  • Spam on devel list
  • PhD Assistance Services spam on fedora-devel
  • Block following retired packages in koji please
  • vmhost-x86-cc02.rdu-cc.fedoraproject.org has failed disk
  • Need some OIDC credentials for com blog in STG

CentOS Infra including CentOS CI

• In progress:
  • Create service account and certs needed for UMB
  • Release Improvements
  • Migrate koji infra auth from REDHAT.COM to IPA.REDHAT.COM
• Done:
  • hardware refresh for a sponsored server
  • Update Jenkins gitlab-plugin to 1.8.2

Release Engineering

• In progress:
  • Block following retired packages in koji please
  • epel10 build rejected
  • Update the Final RC SOP
  • please create epel10 based el10-openjdk tag
  • retirement processing based on age of pushed commit that adds "dead.package" is too strict
  • Please add permission for blocking for epel tags for toddlers
  • Fedora-FEX-Rootfs is missing from koji tags
  • Could we have fedoraproject-updates-archive.fedoraproject.org for Rawhide?
  • Impact check for Changes/FEX
  • Investigate and untag packages that failed gating but were merged in via mass rebuild
  • a few mass rebuild bumps failed to git push - script should retry or error
  • Drop modularity from EPEL8.
  • Renaming distribution media for Fedora Server
  • Package retirements are broken in rawhide
  • Implement checks on package retirements
  • Untag containers-common-0.57.1-6.fc40
  • orphan-all-packages.py should remove bugzilla_contact entries from fedora-scm-requests as well
  • Packages that fail to build SRPM are not reported during the mass rebuild bugzillas
  • When orphaning packages, keep the original owner as co-maintainer
  • Create an ansible playbook to do the mass-branching
  • Cleaning old stuff from koji composes directories
  • Fix tokens for ftbfs_weekly_reminder. script
  • Update bootloader components assignee to "Bootloader Engineering Team"for Improved collaboration
• Done:
  • Stalled EPEL package: adobe-source-code-pro-fonts
  • Unretirement request: rust-leb128
  • Create Fedora 41 Final candidates
  • Same subvariant for Fedora KDE Mobile spin as for Fedora KDE Desktop
  • F41 stable push requests
  • Migrate ELN away from ODCS

List of new releases of apps maintained by I&R Team

• Minor update of Bodhi from 8.1.1 to 8.2.0 on 2024-10-29: https://github.com/fedora-infra/bodhi/releases/tag/8.2.0

If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.

The post Infra and RelEng Update - Week 44 appeared first on Fedora Community Blog.

01 Nov 2024 10:00am GMT

31 Oct 2024 6:00pm GMT

Fedora Silverblue is an operating system for your desktop built on Fedora Linux. It's excellent for daily use, development, and container-based workflows. It offers numerous advantages such as being able to roll back in case of any problems. If you want to update or rebase to Fedora Linux 41 on your Fedora Silverblue system, this article tells you how. It not only shows you what to do, but also how to revert things if something unforeseen happens.

Update your existing system

Prior to actually doing the rebase to Fedora Linux 41, you should apply any pending updates. Enter the following in the terminal:

$ rpm-ostree update

or install updates through GNOME Software and reboot.

Note

rpm-ostree is the underlying atomic technology that all the Fedora Atomic Desktops use. The techniques described here for Silverblue will apply to all of them with proper modifications for the appropriate desktop.

Rebasing using GNOME Software

GNOME Software shows you that there is new version of Fedora Linux available on the Updates screen.

First thing to do is download the new image, so select the Download button. This will take some time. When it is done you will see that the update is ready to install.

Select the Restart & Upgrade button. This step will take only a few moments and the computer will restart when the update is completed. After the restart you will end up in a new and shiny release of Fedora Linux 41. Easy, isn't it?

Rebasing using terminal

If you prefer to do everything in a terminal, then this part of the guide is for you.

Rebasing to Fedora Linux 41 using the terminal is easy. First, check if the 41 branch is available:

$ ostree remote refs fedora

You should see the following in the output:

fedora:fedora/41/x86_64/silverblue

If you want to pin the current deployment (meaning that this deployment will stay as an option in GRUB until you remove it), you can do this by running this command:

# 0 is entry position in rpm-ostree status
$ sudo ostree admin pin 0

To remove the pinned deployment use the following command:

# 2 is entry position in rpm-ostree status 
$ sudo ostree admin pin --unpin 2

Next, rebase your system to the Fedora Linux 41 branch.

$ rpm-ostree rebase fedora:fedora/41/x86_64/silverblue

Finally, the last thing to do is restart your computer and boot to Fedora Linux 41.

How to roll back

If anything bad happens (for instance, if you can't boot to Fedora Linux 41 at all) it's easy to go back. At boot time, pick the entry in the GRUB menu for the version prior to Fedora Linux 41 and your system will start in that previous version rather than Fedora Linux 41. If you don't see the GRUB menu, try to press ESC during boot. To make the change to the previous version permanent, use the following command:

$ rpm-ostree rollback

That's it. Now you know how to rebase Fedora Silverblue to Fedora Linux 41 and roll back. So why not do it today?

FAQ

Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.

Question: Can I skip versions during rebase of Fedora? For example from Fedora 38 Silverblue to Fedora 41 Silverblue?

Answer: Although it could be sometimes possible to skip versions during rebase, it is not recommended. You should always update to one version above (38->39->40 for example) to avoid unnecessary errors.

Question: I have rpm-fusion layered and I get errors during rebase. How should I do the rebase?

Answer: If you have rpm-fusion layered on your Silverblue installation, you should do the following before rebase:

$ rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release

After doing this you can follow the guide in this blog post.

Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),…?

Yes, you can follow the Rebasing using the terminal part of this guide for every Fedora Atomic Desktop. Just use the corresponding branch. For example, for Kinoite use fedora:fedora/41/x86_64/kinoite

31 Oct 2024 8:00am GMT

31 Oct 2024 12:00am GMT

30 Oct 2024 11:38am GMT

Fedora test days are events where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you've never contributed to Fedora before, this is a perfect way to get started.

During these test days, from Friday 01 November through Friday 08 November, the focus will be on testing the changes that will be coming in Fedora 41 as we move ahead with Podman 5.3. This is an opportunity for anyone to learn and interact with the Podman Community and container tools in general.

Podman 5.3 Test Days

Podman is a daemon-less, open source, Linux native tool designed to make it easy to find, run, build, share and deploy applications using Open Containers Initiative (OCI) Containers and Container Images. It provides a command line interface (CLI) familiar to anyone who has used the Docker Container Engine. As part of a recent discussion, the Rawhide Test Day efforts, and Podman Container Engine Team's collaborative efforts, we will hold test days for this minor Podman Release.

The wiki page helps the testers know and understand the scope of the test days. The Test day app helps the testers submit the results once they have tried the test cases.

How do test days work?

A test day/week is an event where anyone can help make sure changes in Fedora Linux work well in an upcoming release of specific software. Fedora community members often participate, and the public is welcome at these events. If you've never contributed before, this is a perfect way to get started.

To contribute, you only need to be able to download test materials (which include some large files) and then read and follow directions step by step.

Detailed information about all the test days is available on the wiki page mentioned above. If you're available on or around the days of the events, please do some testing and report your results. All the test day pages receive some final touches which complete about 24 hrs before the test day begins. We urge you to be patient about resources that are, in most cases, uploaded hours before the test day starts.

Come and test with us to make Fedora Linux even better!

30 Oct 2024 8:00am GMT

30 Oct 2024 7:56am GMT

Fedora Linux provides a wide variety of users with leading edge open source technology in a community developed and maintained operating system. The Fedora KDE Spin combines the reliable and trusted Fedora Linux base with the KDE Plasma desktop environment and a selection of KDE applications - simple by default, yet powerful when needed.

Back in April 2024, Fedora Linux 40 included the KDE "MegaRelease 6" - the Plasma desktop environment, Frameworks application libraries (with the underlying Qt platform), and Gear application suite were all upgraded to new versions in one fell swoop to deliver improved performance and reliability. Since then, continuous upstream updates by the KDE teams to fix bugs and deploy new features were quickly deployed to Fedora 40 users, including breakthroughs such as Explicit Sync in Wayland (which addressed the most prevalent graphical glitches on Nvidia devices)!

Now, as part of the Fedora Linux 41 release, the KDE Spin again includes the very latest with the recently released KDE Plasma 6.2, up-to-date KDE applications and core system packages, and new ways of using Plasma on different devices:

KDE Plasma 6.2

Plasma 6.2 features numerous bug fixes and additional features to continue building on the modern foundation of Plasma 6:

• Drawing tablet configuration, calibration and pen button binding that are built-in to the System Settings app - no extra software needed
• Color management upgrades all over - Wayland protocol improvements, better brightness handling for HDR and ICC profiles, tone mapping built-in to the KWin compositor, and faster HDR performance add up to a better desktop experience for graphic design, gaming, and multimedia
• Accessibility improvements, by adding the complete "Sticky Keys" feature on Wayland (enabling users with limited dexterity and/or mobility to use keyboard shortcuts more easily), and by providing color blindness correction filters directly in the revamped System Settings Accessibility page

Fedora KDE across devices

ARM-Based devices (AArch64)

The Fedora Project and KDE have both worked to support ARM-based devices like Raspberry Pi and Apple Silicon with high-quality experiences. Beginning with Fedora Linux 41, the KDE Spin for AArch64 will now be "release-blocking". This means that showstopper bugs impacting the KDE experience on these devices can now qualify as blockers for the overall release, helping ensure that projects such as Fedora Asahi Remix (for Apple Silicon) get the best possible support.

Please note that live ISOs for KDE on AArch64 are not yet release-blocking, and will be coming in a future release

KDE Plasma Mobile Spin & Kinoite Mobile

Built on the foundations of the Plasma Desktop, KDE Plasma Mobile brings its flexibility to devices with a mobile form factor. Although it was originally geared towards phones, the touch-friendly interface works very well on tablets and 2-in-1 laptops, and enables users with an even broader range of devices to join the Fedora community!

This experience will be available in both the traditional distribution format, as the Fedora KDE Plasma Mobile Spin, and in an Atomic Desktop bootable container image, as Kinoite Mobile.

Please note that installation ISOs have not yet been published for Kinoite Mobile on this cycle, but are coming soon!

Fedora Linux 41 general updates

Some of the key updates occurring in the core components of Fedora 41, which specifically impact the KDE Spin, include:

• New power profiles daemon: tuned replaces the old power-profiles-daemon, providing advanced users with more options to fine-tune the power consumption of their system. This change also provides API compatibility for developers, and reduces the number of different approaches for which software maintainers need to account
• Broader laptop camera support: Many recently released laptops include new IPU6 webcams that use a unique bus (instead of USB) and rely on much more software support to function. Fedora Linux 41 includes out-of-the-box support for cameras using the ov2740, ov01a10 and hi556 sensors in applications such as Firefox that can access cameras via Pipewire

Wrap-up

The Fedora Project and the KDE Community hope that you'll find Fedora KDE 41 to be an easy-to-use, reliable and powerful desktop operating system. When you're ready to check it out, click here for download links and verification instructions.

If you use and enjoy Fedora KDE, consider getting involved in the Fedora Project, the KDE Community, the Fedora KDE Special Interest Group, or all of the above!

29 Oct 2024 2:00pm GMT

I'm happy to once again announce an early release of Fedora Linux 41. Every cycle, our Quality team carefully validates candidate builds against our release criteria, and this time around, we felt confident that we were ready at our early target date. Thank you and congratulations to everyone in Fedora who worked so hard to make this possible, and to all of our upstream projects - and to everyone who helps build a better world by engaging with community-built free and open source software.

What do we have in store for you this time around? A ton of updates to thousands of packages, ranging from tiny patches to big new features. Read the highlights below to find out more. Or, just jump right in!

Upgrade

If you have an existing system, Upgrading Fedora to a New Release is easy, and in most cases not much more of a process than rebooting for regular updates (except you'll have more time to go get some coffee).

Fresh installation

If you're new to Fedora Linux (welcome!) or just want to start fresh, download the install media for our flagship Editions (Workstation, Cloud, Server, CoreOS, IoT), for one of our Atomic Desktops (including Silverblue and Kinoite), or for alternate desktop options (like KDE Plasma, Xfce, or the new "Miracle" spin).

What's new?

DNF 5

Fedora Linux 41 defaults to a new major release of the command-line package management tool DNF. This version is faster, smaller and requires fewer supporting packages. This eliminates the need for "microdnf" for containers and memory-constrained systems - now, the same DNF can be used across containers, servers, desktops and devices.

Desktop Updates

Fedora Workstation 41 is based on GNOME 47. Read What's New in Fedora Workstation 41? for details. Notably for command-line users, we've changed the default terminal to Ptyxis. It's more lightweight, but has some nice new features as well. (GNOME Terminal is still there if you need some of the flexibility it offers.)

Fedora KDE Plasma Desktop ships with the latest KDE 6.2 release. See What's New in Fedora KDE 41? for more. We also have a new Spin featuring KDE Plasma Mobile.

If you're interested in trying something new, take a look at Fedora Miracle! Miracle is a new desktop environment built on Mir and Wayland. It features tiling window management and flashy graphics and smooth window animations.

New options for image mode

We're shipping image-based Fedora variants (such as Atomic Desktops, CoreOS and Fedora IoT) with a new tool called "bootc". This is the successor to rpm-ostree, building on those ideas in a more flexible way - and letting you use container patterns to define your personal flavor of Fedora. (Shout out to our friends over at Universal Blue, a Fedora downstream project which pioneered this approach!)

If you're eager to try this, it's easy to switch from rpm-ostree to bootc. For example, for Fedora IoT, run the following command:

sudo bootc switch quay.io/fedora/fedora-iot

Soon, you'll be able to use DNF 5 to seamlessly manage locally-installed packages, instead of needing to call rpm-ostree or bootc directly. (This is work in progress!)

Image-mode systems also now benefit from bootupd, which allows users to apply bootloader updates more easily - for example, if there is an update to the Secure Boot database.

Secure Boot support for systems which need the proprietary Nvidia driver

Although we don't ship proprietary software, we want people to actually be able to use the hardware they have, so we worked to make it easy to install the proprietary drivers from third-party repositories. However, as more and more systems are shipping with Secure Boot enabled, we temporarily removed that option. Now it's back. When you install the driver, GNOME Software will create a Machine Owner Key which you can manually enable.

MIPI, and Pipewire camera support in Firefox

This is exciting! The cameras shipping in new laptops use an interface called "MIPI", which expects a lot more from the operating system. Previously, these were a pain to get working. Now we have integrated support for Intel IPU6 attached MIPI cameras. We're also shipping Firefox with PipeWire for video enabled by default. The new cameras need this - and as an added bonus, you get a nice clear indicator in the GNOME top bar when your camera is on.

Zero-day updates

There are several important release-day bugfix and security updates available today as well. If you upgrade from an earlier Fedora Linux release, you'll get them as part of that. For new installations, please make sure to check for and apply updates as soon as possible.

In the unlikely event of a problem…

If you run into a problem, visit our Ask Fedora user support forum. This includes a category where we collect common issues and solutions or work-arounds.

Or if you just want to say "hello"…

Drop by our "virtual watercooler" on Fedora Discussion and join a conversation, share something interesting, and introduce yourself. We're always glad to see new people!

29 Oct 2024 1:59pm GMT

Fedora Workstation 41 is the latest release of one of the leading providers of free, open source software, The Fedora Project. This article describes some of the user-facing changes in the newest version of Fedora Workstation. Upgrade today from the official website, or upgrade your existing install using GNOME Software or through the terminal with dnf system-upgrade.

GNOME 47

In Fedora 41 workstation, you can enjoy the latest features the GNOME software release has to offer, plus benefit from an array of system enhancements! Check out the GNOME 47 release notes for more details.

Accent Colors

One of the biggest features to land in GNOME 47, and Fedora Workstation 41, is the option to customize the standard blue accent color of GNOME interfaces. You can now choose from an array of vibrant colors, and customizing couldn't be simpler - just select a color from the Appearance setting, and enjoy a uniquely-your desktop!

Enhanced Small Screen Support

This added support means user who have lower resolution screens will have a better experience as icons will be optimized and scaled for easier interaction and better visibility on smaller screens.

New Style Dialogue Windows

In GNOME 47, the dialogue windows have a new style. This is intended to enhance usability across many screen sizes. This benefits everyone, but especially users who work on compact laptops and mobiles, and this upgrade means the dialogues work more effectively and they can adapt seamlessly to different environments. For added fun, try it out with custom accent colors!

IPU6 Camera support

In Fedora Workstation 41, we have added integrated support into Fedora Linux for Intel IPU6 attached MIPI cameras using the IPU6 CSI-receiver together with libcamwera's 0.3 software ISP support in Firefox through PipeWire. This means a much better experience for users with newer camera models, and users will be able to see the camera icon in the top bar in GNOME if and when your camera is on.

IBus Chewing for Traditional Chinese (Taiwan) Desktop enabled by Default

The default input method for Traditional Chinese has changed to ibus-chewing in Fedora Workstation 41. This change makes Fedora Linux more friendly to users as ibus-chewing is maintained by native speakers and the upstream is active. Much less reliance on Google Translate when reporting issues! It even has multi dictionary so users can load domain specific dictionaries.

Nvidia Driver Install Support

Returning to Fedora Workstation in Fedora Linux 41 is support for installing Nvidia drivers with secureboot. By using mokutil, users can install the drivers, create a key with mokutil to self-sign the drivers, and provide a password for the key. On the next reboot the user is presented with the mokutil interface to enroll the key. For a how-to on using mokutil, please refer to the docs page. With this support now added, installation of Nvidia drivers on Fedora Linux 41 is now more accessible than ever!

Ptyxis as the new Terminal App

Ptyxis is a terminal for GNOME with first-class support for containers, and works really well for Flatpaks as this is the intended distribution mechanism. This is now the default terminal app in GNOME 47 and Fedora Workstation 41 and brings features such as terminal inspector to help you debug issues when writing applications for the terminal, native support for light/dark mode and user-customizable keyboard shortcuts.

29 Oct 2024 1:59pm GMT

Flock to Fedora 2024, held in Rochester, New York from August 7th to 10th, soared to new heights, bringing together Fedora contributors and enthusiasts for four days of immersive learning, dynamic collaboration, and vibrant community building. The event seamlessly blended in-person interactions with live stream and recorded sessions via YouTube for the first two days, ensuring accessibility for a wider audience. Using Matrix Chat for seamless communication and a well-structured online schedule, Flock 2024 successfully fulfilled its mission of uniting the Fedora community, fostering connections, and sparking a wave of innovation.

Target Audience

The primary target audience was Fedora contributors, encompassing developers, packagers, designers, documentation writers, and anyone actively involved in the Fedora Project. The event also welcomed newcomers and those curious about Fedora and open source.

Attendees

Rochester welcomed a diverse and passionate group of attendees, including, but not limited to:

• The majority of the Fedora Council, FESCo, and Mindshare Committee members.
• Fedora Project Leader Matthew Miller, Fedora Operations Architect Aoife Moloney, Fedora Community Architect Justin W. Flory
• Representatives from sponsor communities, like Rocky Linux, Lenovo, Microsoft Azure, AlmaLinux, CentOS, openSUSE, ARM, Meta, and SureStep.
• Numerous passionate Fedora community members. See badge scans for a full list.

Key Highlights From The Event

• Engaging Keynotes: Matthew Miller's "State of Fedora" keynote provided valuable insights into the project's trajectory. Other impactful keynotes included Pat Riehecky's "It is OK not to know things" and Anita Zhang's "How (Not) To Get Into Tech," offering diverse perspectives on the open source journey.
• Dynamic Sessions and Workshops: The event featured many sessions catering to diverse interests, with popular choices including panel discussions from the Fedora Council and FESCo, "What does Red Hat want?", and numerous talks on Bootc.
• Diverse Tracks: Attendees explored three tracks, including the Flock general track, the CentOS track, and the Mentor Summit track. These tracks tool place across several rooms, like the Red Hat main stage, and the breakout rooms sponsored by Lenovo, Rocky Linux, and Microsoft Azure. Topics ranged from technical deep dives (OpenQA, Konflux, eBPF, AI/ML, RISC-V) to community-building initiatives and DEI efforts.
• International Candy Swap: This unique tradition fostered cross-cultural connections as attendees shared sweets and stories from their home countries.

Fedora Community Engagement

• The Fedora community was actively involved throughout the event.
• Community members contributed as speakers, workshop leaders, and attendees, driving discussions and knowledge sharing.
• Topics like Bootc and the future of Fedora sparked lively conversations and collaboration.

Community Participation and Recognition

• Booth Staff/Volunteers: The dedicated volunteer team, including those listed on the Flock 2024 - Volunteers sign-up sheet, ensured a smooth and welcoming experience for all attendees. Their tireless efforts were critical to the event's success.
• Speakers: A diverse group of speakers shared their expertise and insights, fostering learning and inspiring attendees. Myself and two of my fellow interns, Adrian Edwards and Roseline Bassey, presented a hybrid presentation of pre-recorded and live sessions as part of the Mentored Projects Showcase. You can see the full speaker list on the conference schedule.

Virtual Events

• Livestream & Recordings: The event's first two days were live-streamed and recorded, allowing virtual participants to engage with the content.
• Viewership Data:
  • Day 1:
    • Red Hat Room: Over 1,000 views
    • Lenovo Room: 888 views
    • Rocky Linux Room: 427 views
    • Microsoft Azure Room: 324 views
  • Day 2:
    • Red Hat Room: 674 views
    • Lenovo Room: 288 views
    • Rocky Linux Room: 286 views
    • Azure Room: 213 views
• Online Engagement: Social media platforms buzzed with activity, with attendees and virtual participants sharing their experiences and insights using the official hashtags #FlockToFedora, and #FlockRochester.

Challenges, Lessons Learned, and Recommendations

• Streaming Capabilities: Available resources constrained our ability to live stream the entire event, while the impact of this for virtual attendees was minimized with creative scheduling, the hope is to explore improvements to the event streaming setup in the future.
• Weather Disruption: The scavenger hunt was unfortunately affected by a storm, highlighting the importance of contingency plans for outdoor or weather-dependent activities.
• Survey Feedback: We conducted a post-event attendee survey to collect feedback from attendees and speakers. This valuable input has guided us and will continue to guide us in implementing improvements and addressing areas of concern for future Flock events.

Conclusion

Flock to Fedora 2024 was a success, showcasing the strength and vibrancy of the Fedora community. We are already looking forward to Flock to Fedora 2025! To stay informed about future events and opportunities to get involved, visit the Fedora Project website, join the Fedora Matrix room, and follow us on social media!

Special Thanks to Our Sponsors

We extend our deepest gratitude to all our sponsors, whose generous support made Flock to Fedora 2024 possible. Your commitment to open source and the Fedora community is invaluable.

Edited by Adrian Edwards and Justin W. Flory

The post Looking back at Flock to Fedora 2024 appeared first on Fedora Community Blog.

28 Oct 2024 8:00am GMT

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

Week: 21st October - 25th October 2024

Infrastructure & Release Engineering

The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It's responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues

Fedora Infra

• In progress:
  • Need some OIDC credentials for com blog in STG
  • setup ipa02.stg and ipa03.stg again as replicas
  • Move OpenShift apps from deploymentconfig to deployment
  • RFE: fedoras container image register change
  • The process to update the OpenH264 repos is broken
  • httpd 2.4.61 causing issue in fedora infrastructure
  • Support allocation dedicated hosts for Testing Farm
  • Mailman deployment memory spikes
  • Searching mailing list archives does not work
  • EPEL minor version archive repos in MirrorManager
  • vmhost-x86-copr01.rdu-cc.fedoraproject.org DOWN
  • Update DRAC Firmware on All Dell Servers
  • Recurring issue that Bugzilla stops sending messages to fedora-messaging
  • Cleaning script for communishift
  • rhel7 eol
  • move resultsdb-ci-listener deployment pipeline
  • rhel7 EOL - github2fedmsg
  • Setup RISC-V builder(s) VM in Fedora Infrastructure
  • Move from iptables to firewalld
  • Help me move my discourse bots to production?
  • fedmsg -> fedora-messaging migration tracker
  • rhel9 adoption
  • Create monitoring tool for rabbitmq certificates
  • Replace Nagios with Zabbix in Fedora Infrastructure
  • Migration of registry.fedoraproject.org to quay.io
  • Commits don't end up on the scm-commits list
• Done:
  • src.fedoraproject.org reports 502 Bad Gateway
  • Need OIDC credentials for fedora magazine in staging
  • Increase quota of ngompa.fedorapeople.org to 10G
  • New copr group for RHEL Lightspeed
  • RFE: Cloud download page should provide older links to AMI images
  • bvmhost-x86-03 error on boot
  • Unable to login to pagure using SSO, says "authentication failure"
  • OIDC client credentials for image builder
  • CNAME record request for image builder community deployment
  • [CommOps] Communishift - Datanommer
  • anaconda-devel list archive prior to 2021 missing
  • Duplicated https,https in HTTP_X_FORWARDED_PROTO since sometime this year

CentOS Infra including CentOS CI

• In progress:
  • Create service account and certs needed for UMB
  • Release Improvements
  • Migrate koji infra auth from REDHAT.COM to IPA.REDHAT.COM
• Done:
  • building through infra tags needed pkgs for UMB consumption
  • Decommission unused koji builders
  • CentOS Stream AWS images not being pushed out to all regions
  • [NFV SiG] Enable s390x arch for nfv10s-openvswitch-2-* tags
  • New group for the automotive SIG - automotive-docs-contributors
  • please add EPEL repos to my storage10s-* tags or targets
  • CentOS Stream 9's `crb-source` repo has broken checksums
  • [Cloud SIG] Create OpenStack Epoxy tags for CentOS Stream 10 in CBS
  • Provide CentOS Stream 10 as an option for CI/Duffy env
  • Renew TLS certs (LetsEncrypt) but also consolidate various automation tools around it

Release Engineering

• In progress:
  • Need some OIDC credentials for com blog in STG
  • setup ipa02.stg and ipa03.stg again as replicas
  • Move OpenShift apps from deploymentconfig to deployment
  • RFE: fedoras container image register change
  • The process to update the OpenH264 repos is broken
  • httpd 2.4.61 causing issue in fedora infrastructure
  • Support allocation dedicated hosts for Testing Farm
  • Mailman deployment memory spikes
  • Searching mailing list archives does not work
  • EPEL minor version archive repos in MirrorManager
  • vmhost-x86-copr01.rdu-cc.fedoraproject.org DOWN
  • Update DRAC Firmware on All Dell Servers
  • Recurring issue that Bugzilla stops sending messages to fedora-messaging
  • Cleaning script for communishift
  • rhel7 eol
  • move resultsdb-ci-listener deployment pipeline
  • rhel7 EOL - github2fedmsg
  • Setup RISC-V builder(s) VM in Fedora Infrastructure
  • Move from iptables to firewalld
  • Help me move my discourse bots to production?
  • fedmsg -> fedora-messaging migration tracker
  • rhel9 adoption
  • Create monitoring tool for rabbitmq certificates
  • Replace Nagios with Zabbix in Fedora Infrastructure
  • Migration of registry.fedoraproject.org to quay.io
  • Commits don't end up on the scm-commits list
• Done:
  • Stalled EPEL package: aalib
  • Block following retired packages in koji please
  • Create Fedora 41 Final candidates
  • Block following retired packages in koji please
  • Unretirement request: rust-crypto-hash
  • Deletion of two side tags
  • Stalled EPEL packages: zeromq and openpgm
  • perl-Crypt-PBKDF2 missing from EPEL-10 repo
  • Unretire rust-inflate
  • Change Impact: Python 3.14
  • Please delete accidental v0.40.0 branch from python-starlette
  • Block retired packages in koji for epel9 tag please
  • F41 stable push requests
  • Migrate ELN away from ODCS

If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.

The post Infra and RelEng Update - Week 43 appeared first on Fedora Community Blog.

25 Oct 2024 10:00am GMT

This post is a brief summary of the team's highlights over the course of the second quarter of 2024 (April to June). These highlights include:

• Fedora Week of Diversity
• Flock Hackfest preparations
• Fedora Mentor Summit preparations
• Improvements to the team onboarding workflow
• Our new repository for DEI event media e.g. picture, videos, slides, etc.

These highlights will be summarised below.

Fedora Week of Diversity

https://gitlab.com/fedora/dei/home/-/issues/19 & https://gitlab.com/fedora/dei/week-of-diversity

Fedora Week of Diversity took place June 17-22, 2024. This week is the successor to Fedora Women's Day, originally started in 2016 as a celebration of the diverse people who make up our Fedora community.

From inspiring interviews to engaging virtual sessions hosted on Matrix, this year's Fedora Week of Diversity showcased the strength and spirit of the community. Attendees registered for the event through Pretix, and session recordings were made available on YouTube for wider access.

You can find out more on the 2024 recap blog post of the event by Oluwatosin Olatunji.

Flock Hackfest preparations

https://gitlab.com/fedora/dei/home/-/issues/44

For this year's Flock, the team planned a half-day hackfest. This session was designed to welcome newcomers, provide insight into the DEI team's ongoing efforts, and outline our plans for the future.

The agenda for the session included:

• Introduction to the DEI team, including our GitLab workflow and team meetings
• Retrospective on the Fedora Week of Diversity
• Ticket triage on GitLab and collaboration on pending tickets
• Next steps for the DEI team

Goals of the hackfest were:

• Provide a clear understanding of our team's mission, vision, and workflow to new people interested in learning more about the DEI team.
• Outline upcoming events and gather input on event ideas/themes. Ideally, create a team with interested people in organizing the events.
• Identify strategies to better support DEI initiatives and regional communities.

Flock was held from Wednesday, August 7th to Saturday, August 10th at the Hyatt Regency Rochester in Rochester, New York, USA. You will have to wait for our Q3 report to see how it went!

Fedora Mentor Summit preparations

https://gitlab.com/fedora/dei/home/-/issues/25

Planning took place for the half-day event focused on mentoring best practices. This year's Mentor Summit aimed to focus on workshops and sessions to promote mentorship best practices and to connect mentors and mentees across the Fedora community.

FMS was held together with Flock and took place on Saturday, August 10th. You will have to wait for our Q3 report to see how it went!

Improvements to the team's onboarding workflow

https://gitlab.com/fedora/dei/home/-/issues/2

Given the influx of new team members the last few months, the team decided it would be good to standardize how we onboard new members. Two changes were made:

• Create a new member template for GitLab
• Update the team's onboarding documentation

If you would like to get involved, you can check out our updated process here.

DEI Media Assets

https://gitlab.com/fedora/dei/home/-/issues/30

A repository was created for the team to store pictures, videos and slides from DEI events. This was created to help us with future content creation for the team.

Looking ahead to 2024 Q3!

As mentioned above, you can look forward to summaries of how the DEI Hackfest and the Fedora Mentor Summit went.

Want to get involved? Join the DEI Team Matrix chat room (#dei:fedoraproject.org) and follow the Fedora Discussion tag. We meet twice monthly. Our next meeting can be found on the Fedora Calendar.

The post Fedora DEI Team 2024 Q2 Report appeared first on Fedora Community Blog.

25 Oct 2024 8:00am GMT

RPMs of PHP version 8.3.13 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

RPMs of PHP version 8.2.25 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

The packages are available for x86_64 and aarch64.

There is no security fix this month, so no update for version 8.1.30.

PHP version 8.0 has reached its end of life and is no longer maintained by the PHP project.

These versions are also available as Software Collections in the remi-safe repository.

Version announcements:

• PHP 8.3.13 Release Annoucement
• PHP 8.2.25 Release Annoucement

Installation: use the Configuration Wizard and choose your version and installation mode.

Replacement of default PHP by version 8.3 installation (simplest):

dnf module switch-to php:remi-8.3/common

Parallel installation of version 8.3 as Software Collection

yum install php83

Replacement of default PHP by version 8.2 installation (simplest):

dnf module switch-to php:remi-8.2/common

Parallel installation of version 8.2 as Software Collection

yum install php82

And soon in the official updates:

• Fedora Rawhide now has PHP version 8.4.0RC3
• Fedora 41 - PHP 8.3.13
• Fedora 40 - PHP 8.3.13
• Fedora 39 - PHP 8.2.25

To be noticed :

• EL-9 RPMs are built using RHEL-9.4
• EL-8 RPMs are built using RHEL-8.10
• EL-7 repository is closed
• intl extension now uses libicu74 (version 74.2)
• mbstring extension (EL builds) now uses oniguruma5php (version 6.9.9, instead of the outdated system library)
• oci8 extension now uses the RPM of Oracle Instant Client version 23.5 on x86_64, 19.24 on aarch64
• a lot of extensions are also available, see the PHP extensions RPM status (from PECL and other sources) page

Information:

• Migrating from PHP 8.0.x to PHP 8.1.x
• Migrating from PHP 8.1.x to PHP 8.2.x
• Migrating from PHP 8.2.x to PHP 8.3.x

Base packages (php)

Software Collections (php81 / php82 / php83)

24 Oct 2024 1:57pm GMT

24 Oct 2024 9:06am GMT

The Fedora Council is considering a change to our policy for promotion of a Fedora deliverable to "Edition" status. Please read that entire document for context before commenting.

This change is being made to reflect actual practice. For example, there is clear overlap between the use-cases and potential user-bases for the current Server, Cloud, and CoreOS Editions, but each takes a different approach. We are currently considering adding an exception for a KDE Desktop Edition, which would overlap with Fedora Workstation.

Currently part of the policy currently reads in a way that prevents this exception from being possible:

A Fedora Edition:

• addresses a distinct, relevant, and broad use-case or user-base that a Fedora Edition is not currently serving;
• is a long term investment for the Fedora Project; and
• is consistent with all of Fedora's Four Foundations.

We propose an additional line:

The Council may make exceptions to the "distinct" rule when we determine that doing so best fits the Project's Mission and Vision.

This topic is open for community discussion, following our Policy Change Policy. After two weeks, the Council will vote in a new ticket, and if approved, the policy will be updated.

Approval of this change would not automatically mean the approval of a KDE Desktop Edition, but would allow that possibility.

The post Proposed change to the Fedora Council policy for Edition promotion appeared first on Fedora Community Blog.

24 Oct 2024 8:00am GMT