/rss20.xml">
fedora

Fedora People
Blog List
RSS 1.0 RSS 2.0 Atom 1.0 FOAF blogroll

What’s new in Fedora KDE 41

Posted by Fedora Magazine on 2024-10-29 14:00:00 UTC

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!

Fedora Linux 41 is here!

Posted by Fedora Magazine on 2024-10-29 13:59:59 UTC

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!

Whats new in Fedora Workstation 41

Posted by Fedora Magazine on 2024-10-29 13:59:42 UTC

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.

Looking back at Flock to Fedora 2024

Posted by Fedora Community Blog on 2024-10-28 08:00:00 UTC

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.

The "thank you to our sponsors" slide from Flock containing a happy colur mascot and the logos of the key sponsors: Red Hat, CentOS, Rocky Linux, Lenovo, Microsoft Azure, AlmaLinux, OpenSuse, Arm, and Meta

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.
A screenshot from the livestream showing the FESCo panel in the middle of a discussion. The image is inset into the livestream border with the event date and time and the AV sponsors

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.
A title slide with the text Mentorship Summit - Panel Discussion, the Fedora logo, and the speakers names inset into the livestream border with the event date and time and the AV sponsors

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.

Infra and RelEng Update – Week 43

Posted by Fedora Community Blog on 2024-10-25 10:00:00 UTC

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

Infra&Releng infographic

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

CentOS Infra including CentOS CI

Release Engineering

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.

Fedora DEI Team 2024 Q2 Report

Posted by Fedora Community Blog on 2024-10-25 08:00:00 UTC

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

Screenshot of a live moment during Fedora Week of Diversity (FWD) in June 2024. Two presenters are shown in panes to the left. One speaker is a white man titled "Justin W. Flory" and the second speaker is a white woman titled "Jona". In the slideshow pane to the right of the speakers, there is a list of names of contributors and volunteers of people who organized the event. Chris Idoko, Emma Kidney, Roseline Bassey, Tosin Doreen, Adrian Edwards, Amita Sharma, Joseph Gayoso, Nikita Tripathi, Consolation Obazee, Justin W. Flory, Jona Azizaj.

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: 

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.

PHP version 8.2.25RC1 and 8.3.13RC1

Posted by Remi Collet on 2024-10-11 07:11:00 UTC

Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for a parallel installation, the perfect solution for such tests, and also as base packages.

RPMs of PHP version 8.3.13RC1 are available

  • as base packages in the remi-modular-test for Fedora 39-41 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

RPMs of PHP version 8.2.25RC1 are available

  • as base packages in the remi-modular-test for Fedora 39-41 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-notice-24.pngPHP version 8.1 is now in security mode only, so no more RC will be released.

emblem-notice-24.pngInstallation: follow the wizard instructions.

emblem-notice-24.png Announcements:

Parallel installation of version 8.3 as Software Collection:

yum --enablerepo=remi-test install php83

Parallel installation of version 8.2 as Software Collection:

yum --enablerepo=remi-test install php82

Update of system version 8.3:

dnf module switch-to php:remi-8.3
dnf --enablerepo=remi-modular-test update php\*

Update of system version 8.2:

dnf module switch-to php:remi-8.2
dnf --enablerepo=remi-modular-test update php\*

emblem-notice-24.png Notice:

  • version 8.4.0RC2 is also available in the repository
  • EL-9 packages are built using RHEL-9.4
  • EL-8 packages are built using RHEL-8.10
  • oci8 extension uses the RPM of the Oracle Instant Client version 23.5 on x86_64 or 19.24 on aarch64
  • intl extension uses libicu 74.2
  • RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
  • versions 8.2.25 and 8.3.13 are planed for October 24th, in 2 weeks.

Software Collections (php82, php83)

Base packages (php)

PHP version 8.2.25 and 8.3.13

Posted by Remi Collet on 2024-10-24 13:57:00 UTC

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...).

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-notice-24.pngThere is no security fix this month, so no update for version 8.1.30.

emblem-important-2-24.pngPHP 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:

emblem-notice-24.pngInstallation: 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:

emblem-important-2-24.pngTo 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

emblem-notice-24.pngInformation:

Base packages (php)

Software Collections (php81 / php82 / php83)

Where should I present syslog-ng and sudo?

Posted by Peter Czanik on 2024-10-24 09:06:01 UTC

Recently I was asked the same question both at my workplace and at EuroBSDCon, the conference where I was presenting: where do you talk next? I had no definite answer. Of course, I am looking forward to the FOSDEM CfP, but I am also looking for new conferences to present syslog-ng and sudo. Do you have any recommendations?

You can read the rest of my blog at https://www.syslog-ng.com/community/b/blog/posts/where-should-i-present-syslog-ng-and-sudo

syslog-ng logo

Sudo logo

Proposed change to the Fedora Council policy for Edition promotion

Posted by Fedora Community Blog on 2024-10-24 08:00:00 UTC

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.

Copr Modularity, the End of an Era

Posted by Jakub Kadlčík on 2024-10-23 00:00:00 UTC

Our team has put a lot of effort into the possibility of building modules in Copr. This feature went through many iterations and rewrites from scratch as the concepts, requirements, and goals of Fedora Modularity kept changing. This will be my last article about this topic because we are planning to drop Modularity and all of its functionality from Copr. The only exception are Module hotfixes, which are staying for good.

Why?

The Fedora Modularity project never really took off, and building modules in Copr even less so. We’ve had only 14 builds in the last two years. It’s not feasible to maintain the code for so few users. Modularity has also been retired since Fedora 39 and will die with RHEL 9.

Additionally, one of our larger goals for the upcoming years is to start using Pulp as a storage for all Copr build results. This requires rewriting several parts of the backend code. Factoring in reimplementation for module builds would result in many development hours wasted for very little benefit. All projects with modules will remain in the current storage until the Modularity is finally dropped.

Schedule

In the ideal world, we would keep the feature available as long as RHEL 9 is supported, but we cannot wait until 2032.

  • October 2024 - All Modularity features in Copr are now deprecated
  • April 2025 - It won’t be possible to submit new module builds
  • October 2025 - Web UI and API endpoints for getting module information will disappear
  • April 2026 - All module information will be removed from the database, and their build results will be removed from our storage

Communication

It was me who introduced all the Modularity code into Copr, so it should also be me who decommissions it. Feel free to ping me directly if you have any questions or concerns, but you are also welcome to reach out on the Copr Matrix channel, mailing list, or in the form of GitHub issues. In the meantime, I will contact everybody who submitted a module build in Copr in the past two years and make sure they don’t rely on this feature.

Announcing Webhook To Fedora Messaging

Posted by Fedora Community Blog on 2024-10-22 08:00:00 UTC

With the transition of the applications from Fedmsg to Fedora Messaging inching towards completion, today we want to introduce a new service, Webhook To Fedora Messaging. Webhook To Fedora Messaging has been researched and developed by the Fedora Infrastructure team members with the company of an Outreachy mentee over the last quarter to communicate with services using webhooks.

Webhook To Fedora Messaging takes webhook events from services and translates them into semantic messages to be sent over on the Fedora Messaging bus, to which every Fedora Project application can listen and act for automation. Currently, the project supports services like GitHub but going forward we plan on implementing support for services like Discourse, GitLab, Forgejo etc.

As this service was designed to be the successor to the existing Github2Fedmsg service, we are also announcing that the service is now deprecated and users are encouraged to migrate to the newer service. If you are an existing user of the Github2Fedmsg service, please open a private ticket in the fedora-infra/w2fm-registration repository using the template named “Github2Fedmsg Migration Request”.

Additionally, as GitHub allows for managing webhooks at an organizational level, users migrating from the GitHub2Fedmsg service can explore the functionality by visiting the page https://github.com/organizations//settings/hooks. Once the changes have been made by the owner of the GitHub organization, the activities from all repositories can be conveniently relayed on the Fedora Messaging bus.

The post Announcing Webhook To Fedora Messaging appeared first on Fedora Community Blog.

4 cool new projects to try in Copr for October 2024

Posted by Fedora Magazine on 2024-10-21 17:07:06 UTC

Copr is a build-system for anyone in the Fedora community. It hosts thousands of projects for various purposes and audiences. Some of them should never be installed by anyone, some are already being transitioned to the official Fedora Linux repositories, and the rest are somewhere in between. Copr gives you the opportunity to install 3rd party software that is not available in Fedora Linux repositories, try nightly versions of your dependencies, use patched builds of your favourite tools to support some non-standard use-cases, and just experiment freely.

This article takes a closer look at interesting projects that recently landed in Copr.

If you don’t know how to enable a repository or if you are concerned about whether is it safe to use Copr, please consult the project documentation.

Hyprland

Hyprland is a beautiful Wayland compositor for Linux, offering advanced window management, eye-candy animations, and high customizability. It gives users fine control over their desktop environment, making it perfect for those who value both aesthetics and functionality.

Installation instructions

The repo currently provides Hyprland and many more packages needed for your setup like ags or swww for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:

sudo dnf copr enable solopasha/hyprland
sudo dnf install hyprland

hblock

Improve your security and privacy by blocking ads, tracking, and malware domains with hBlock. This POSIX-compliant shell script compiles lists of such domains from multiple sources and creates a hosts file to block connections to them. You just need to use the following command:

hblock

This will generate an /etc/hosts file with the blocked domains. Keep in mind that hBlock replaces your system’s existing hosts file by default, so it’s a good idea to back it up before running the script.

Installation instructions

The repo currently provides hblock for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:

sudo dnf copr enable pesader/hblock
sudo dnf install hblock

Ungoogled Chromium

Ungoogled Chromium is a privacy-enhanced version of the Chromium browser, designed to remove all Google services dependencies and tracking. It offers the same speed and functionality as regular Chromium but without the built-in connections to Google. This makes it ideal for users who want more control over their data and a more private browsing experience, while still enjoying the benefits of an open-source, lightweight browser.

Installation instructions

The repo currently provides ungoogled-chromium for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:

sudo dnf copr enable wojnilowicz/ungoogled-chromium
sudo dnf install ungoogled-chromium

Floorp

Floorp is a privacy-focused web browser based on Firefox, designed to enhance user security and reduce tracking. It removes telemetry and includes built-in tools for blocking ads and trackers, providing a cleaner browsing experience. With its user-friendly interface, Floorp is an excellent choice for those looking to protect their online privacy.

Installation instructions

The repo currently provides floorp for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:

sudo dnf copr enable sneexy/floorp
sudo dnf install floorp

Posted by Mohammadreza Hendiani on 2024-10-21 13:43:31 UTC

Just learned that 🤖 can now run models directly from Hugging Face via:
`ollama hf.co/{username}/{repository}`

If you're interested in getting a natively ollama for up and running, consider helping me out at:
gitlab.com/fedora/sigs/ai-ml/g

Fedora Operations Report

Posted by Fedora Community Blog on 2024-10-21 11:05:13 UTC

Its spooky season, and also release season! Here’s a roundup of some stuff’n’things happeing in the project.

Fedora Linux 41

The F41 Go/No-Go meeting will happen on Thursday 24th October @ 1700 UTC. To join, you can find the information on the fedocal calendar entry. This meeting will determine if we can meet the early release date of Tuesday 29th October at this time or not.

There are still some proposed blockers for F41 too, so if you can help resolve some of these bus, please check out our blocker bugs app, or for a more condensed summary, please read out blocker bug report email.

Fedora Linux 42

Fedora Linux 42 is currently in development, and for the most recent set of changes planned in this rel;ease, please refer to our change set page. Our release schedule is also live, and a reminder of some key dates are below:

  • December 18th – Changes requiring infrastructure changes
  • December 24th – Changes requiring mass rebuild
  • December 24th – System Wide changes
  • January 14th – Self Contained changes
  • February 4th – Changes need to be Testable
  • February 4th – Branching
  • February 18th – Changes need to be Complete

The changes that are currently in our community feedback period are :

Changes that are awaiting FESCo voting are:

Hot Topics

For all the latest on boot-c, check out the bootc post on discourse!

Our Git Forge evaluation is continuing, with an instance of both Forgejo and GitLab CE available to try out in the Communshift app. Details of how to get access can be found on this discussion thread, and we are encouraging folks to try out each instance and report their feedback, preferably against the user stories collected, on this discussion thread.

The proposal to amend the Editions Promotion policy has now been submitted to Fedora Council, and a decision is expected this week on both this change, and on the request to grant KDE Desktop Spin edition status also.

FOSDEM 2025 returns on Saturday 1st and Sunday 2nd February! The call for devrooms has passed, but the call for stands is still open until November 7th.

Do you have an idea for an episode of the Fedora Podcast, or want to see what some of the upcoming episodes will be? Bookmark The IT Guy’s discussion post on planning for the podcast!

Did you know there are EPEL Office Hours? If not, check out the details on how to join and when they happen on the announcement post!

The post Fedora Operations Report appeared first on Fedora Community Blog.

Infra and RelEng Update – Week 42 2024

Posted by Fedora Community Blog on 2024-10-18 10:00:00 UTC

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: 14th October – 18th October 2024

I&R Infographic

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

CentOS Infra including CentOS CI

Release Engineering

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 42 2024 appeared first on Fedora Community Blog.

Power t-shirts

Posted by Peter Czanik on 2024-10-15 07:12:21 UTC

I love t-shirts, especially those that you’d call logowear. But it’s not the kind of big name fashion logos that I’m referring to. Rather, it’s logowear from my favorite IT companies. I have well over a hundred of these t-shirts, and except when I’m preparing for a special event, I pull a random t-shirt from my collection. Yesterday I happened to wear a power.org t-shirt, while today I’m wearing an OpenPOWER t-shirt, two POWER t-shirts in two days :-) Both of these brought back some nice memories.

power.org t-shirt

The first t-shirt is really old, I got it probably around 2008, while working for Genesi. One of my tasks was moderating the forums on the power.org website. It was a website focusing on IBM POWER server products, but it also included some generic POWER information. Besides sharing information, it also provided a meeting point for like-minded engineers, where they could discuss anything related to POWER. You can read my history with POWER-based computers in one of my opensource.com articles at https://opensource.com/article/20/10/power-architecture.

OpenPOWER t-shirt

The t-shirt I had on today is a lot more recent, but still cannot be called new. It is a t-shirt by the OpenPOWER Foundation from the golden era of open source on POWER: the POWER9 years. Those years have seen the most active open source development on POWER ever since the Pegasos / PowerMac years. Many applications were ported to POWER, both for the server and the desktop. Hopefully there will be another wave of open source activity on POWER soon, fingers crossed :-)

Do you have any interesting POWER t-shirts? Share with me on your preferred social network! My accounts are listed in the top right corner of this page.

Fedora Operations Report

Posted by Fedora Community Blog on 2024-10-13 22:53:58 UTC

Happy October folks! In this post you’ll find some information on our F41 and F42 releases, plus a few lines on a couple of topics happening around the project lately. Read on to find out more!

Fedora Linux 41

We are nearing the end of the Fedora Linux 41 release cycle! Our Go/No-Go meeting will happen next Thursday 17th October @ 1700 UTC. To join, you can find the information on the fedocal calendar entry.

There are still some proposed blockers for F41 too, so if you can help resolve some of these bus, please check out our blocker bugs app, or for a more condensed summary, please read out blocker bug report email.

Fedora Linux 42

Fedora Linux 42 is currently in development, and for the most recent set of changes planned in this rel;ease, please refer to our change set page. Our release schedule is also live, and a reminder of some key dates are below:

  • December 18th – Changes requiring infrastructure changes
  • December 24th – Changes requiring mass rebuild
  • December 24th – System Wide changes
  • January 14th – Self Contained changes
  • February 4th – Changes need to be Testable
  • February 4th – Branching
  • February 18th – Changes need to be Complete

The changes that are currently in our community feedback period are :

Hot Topics

For all the latest on boot-c, check out the bootc post on discourse!

Our Git Forge evaluation is taking shape. We have an instance of both Forgejo and GitLab CE available to try out in the Communshift app. Details of how to get access can be found on this discussion thread, and we are encouraging folks to try out each instance and report their feedback, preferably against the user stories collected, on this discussion thread. Directly linked to the git forge evaluation, following Wednesdays council meeting, we have decided to extend the report comparing both Forgejo and GitLab CE to be due by December 5th to allow our QA team, and other teams impacted by the F41 release, time to properly validate their use cases against each forge option. This means the council decision may not happen until early January, but we do hope to proceed with a decision as early as possible so the CPE team can help create a migration plan for affected workflows that can be shared and agreed to in good time to allow minimal disruption to the project as a whole as possible.

There is still time to share feedback on the proposal to amend the Editions Promotion policy. You can read the current policy, and what the council would like to change, in this discussion thread.

FOSDEM 2025 returns on Saturday 1st and Sunday 2nd February! The call for devrooms has passed, but the call for stands is still open until November 7th.

A new episode of The Fedora Podcast is now available! Details of episode 38 and how to listen can be found on the discussion post and by visiting the audio post for the latest, and all episodes.

The post Fedora Operations Report appeared first on Fedora Community Blog.

Redis: The Powerhouse Behind Modern Databases

Posted by Piju 9M2PJU on 2024-10-13 11:33:41 UTC

In today’s rapidly evolving tech world, the need for fast and efficient data management is more critical than ever. One name that frequently stands out in the NoSQL database world is Redis. Since its introduction in 2009, Redis has become a go-to choice for real-time applications that require exceptional speed and flexibility in handling data.

In this article, we’ll explore the history of Redis, how it’s used, and the benefits it offers to various modern applications.

The History of Redis: Origins and Evolution

Redis, which stands for Remote Dictionary Server, was developed by Salvatore Sanfilippo in 2009. Initially launched as an open-source project to address scalability issues faced by large-scale systems, Redis quickly gained popularity among developers for its ability to process data at lightning speeds.

Redis operates as an in-memory database, meaning it stores all data in RAM rather than on disk. This design enables Redis to deliver significantly faster performance compared to traditional databases, making it ideal for applications that demand real-time speed.

How is Redis Used?

One of the primary reasons Redis is so popular is its flexibility, allowing it to be used in various scenarios. Here are some real-world examples of how Redis is utilized:

  1. Caching
    Redis is well-known for its use in caching due to its speed. By storing data in memory, Redis drastically reduces the time it takes to retrieve data. This is especially useful in web applications where users need instant access to information such as previously loaded pages, images, or API data.
  2. Session Management
    Many large platforms use Redis to store user session information. When users log into a system, Redis can store their session data in memory, ensuring quick access. This is crucial for maintaining a smooth user experience without delays.
  3. Real-Time Analytics
    In a data-driven world, companies need instant analytics to make informed decisions. Redis enables companies to process and analyze data in real time, such as tracking user behavior on websites, monitoring IoT devices, or analyzing financial transactions as they occur.
  4. Message Queuing
    Redis is also widely used for message queuing via its Pub/Sub (Publisher/Subscriber) feature. This is particularly helpful in systems where real-time communication between services or applications is required, such as notification systems or instant messaging services.

The Benefits of Redis: What Makes It Great?

Incredible Speed
Redis stands out because of its speed. As an in-memory database, Redis delivers sub-millisecond response times, making it one of the fastest technologies available for data management. This is why it is often the preferred choice for real-time applications.

Versatile Data Structures
Another feature that sets Redis apart is its support for various data structures like strings, lists, sets, and hashes. This versatility allows developers to use Redis in a wide range of scenarios, from storing user information to managing complex data in e-commerce systems.

Persistence Options
Even though Redis stores data in memory, it also offers persistence options, allowing users to periodically save data to disk. This provides an added layer of security in case of system failures, ensuring that data is backed up and recoverable.

Easy Scalability
Redis is easily scalable, whether vertically (by adding more RAM) or horizontally (by adding more Redis servers). This is essential for growing applications where the need to process more data increases over time.

Conclusion

Redis has proven itself to be one of the most powerful tools in modern data management. Its incredible speed, support for multiple data types, and scalability make it the top choice for real-time applications. Whether you’re a developer building web apps or a company looking to process real-time analytics, Redis is a technology worth exploring.

There you have it—a brief guide to Redis and the benefits it brings. This technology not only accelerates application performance but also provides a flexible and reliable solution for managing data at scale.

The post Redis: The Powerhouse Behind Modern Databases appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

Infra and RelEng Update – Week 41 2024

Posted by Fedora Community Blog on 2024-10-11 10:00:00 UTC

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contains updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.

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: 7th October – 10th October 2024

I&R infographic

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

CentOS Infra including CentOS CI

Release Engineering

List of new releases of apps maintained by CPE

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

NOTE: There are currently internal changes happening in CPE Team (we will see if the name even remains), which caused that the last week update didn’t came out (it was also caused by the login issue in community blog, but that was just a coincidence) and caused change in the content (some sections are currently missing). We apologize for that and we see how the format will look in the future.

The post Infra and RelEng Update – Week 41 2024 appeared first on Fedora Community Blog.

🚀 PM2 Process Manager 🚀

Posted by Piju 9M2PJU on 2024-10-11 00:09:06 UTC

In the past, users with Linux/Unix accounts often relied on various tools such as at, setsid, nohup, screen, and tmux to manage their processes. However, with technological advancements, there is now a more sophisticated and effective process manager available: PM2.

What Is PM2?

PM2 is a modern solution that simplifies application management. It offers a range of features that make it a top choice for developers looking to ensure their applications run smoothly and continuously. PM2 is also compatible with various frameworks and environments, making it versatile for different application types.

Advantages of Using PM2

  1. Start and Stop Processes: With PM2, you can easily manage your applications using simple commands. It supports various types of applications, whether they are Node.js, Python, Go, Java, or others. No more hassle of managing applications manually!
  2. Keep Applications Alive: One of the best features of PM2 is its ability to automatically restart your applications if they crash. This means your applications will always be active and available for users.
  3. Performance Monitoring: PM2 provides real-time metrics on CPU and memory usage, allowing you to optimize your applications more effectively. With this information, you can make better decisions to enhance your application’s performance.
  4. Manage Clusters: PM2 makes it easy to scale your applications with built-in cluster support. You can run multiple instances of your application on a single server to maximize capacity and performance.
  5. Compatibility: PM2 is compatible with various frameworks, such as Express, Koa, NestJS, and more, making it a flexible choice for developers across different environments.
  6. Operating Systems Supported: PM2 runs seamlessly on multiple operating systems, including Linux, macOS, and Windows. This cross-platform support ensures that you can use PM2 in your preferred development environment without any issues.

Conclusion

Given these numerous advantages, it’s no surprise that PM2 has become the go-to choice for many developers to manage their applications. If you’re still using outdated tools like at or nohup, it might be time to consider switching to PM2. With PM2, you’ll experience a significant difference in how you manage your processes and applications.

So, if you’re looking for a modern and efficient process manager that supports various frameworks and operating systems, PM2 is the answer! 🌟

The post 🚀 PM2 Process Manager 🚀 appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

Debugging Jekyll posts locally

Posted by Pavel Raiskup on 2024-10-11 00:00:00 UTC

Just a quick post about a small side-project. For a few years now, I’ve been maintaining a Jekyll Container image. Mostly for my own convenience—whether I’m working on posts for this blog or writing documentation for Mock (or other). I thought I’d share a few words about it now.

Keep My Box Clean! (and DRY)

The motivation was simple: to be able to debug Jekyll/GitHub Pages posts locally before pushing them to GitHub. I wanted to do this consistently across multiple pages, and I didn’t want to repeat myself in the future (following the DRY principle).

Back then, I realized that running Jekyll locally wasn’t a trivial task—at least not on Fedora, if, like me, you prefer staying on a “pure” Fedora system (meaning you only install software distributed through Fedora repositories). Notably, installing the GitHub Pages additions from gems wasn’t easy either, and it still isn’t (as of autumn 2024). Building your own container can also cause some headaches.

Jekyll made easy

So here we are—assuming you have a blog post or any documentation root directory, you can run the Jekyll server in a container, and available on http://localhost:4000/, using just:

$ jekyll-host ./your-jekyll-root
Installing deps, may take several minutes
=========================================
 Server listens on http://127.0.0.1:4000
 Jekyll Log: /tmp/jekyll-server.log (in container)
 Install logs: /tmp/bundler-install.log (in container)
=========================================

The jekyll-host script (which must be in your $PATH) is just a one-line wrapper around a podman run command that uses a pre-built container image hosted and built by https://quay.io/.

I prefer to stay 100% focused on writing, not on the infrastructure. After a quick chat with my colleagues, it seems this setup could be helpful to others as well. If that’s the case, enjoy!

Switch Upgrade

Posted by Fedora Infrastructure Status on 2024-10-10 15:00:00 UTC

A 10G switch in our main datacenter needs upgrades. Many machines may drop off the network and come back during the outage window.

Gaming on Fedora Asahi Remix

Posted by Fedora Magazine on 2024-10-10 14:30:00 UTC

Better support for gaming on Fedora Asahi Remix has been a long standing user request. Today at XDC 2024, we announced the preliminary availability of our game playing toolkit, integrating x86 emulation with MS Windows compatibility. This toolkit, with the conformant Vulkan 1.3 and OpenGL 4.6 drivers, enables playing commercial AAA games on Apple Silicon Macs running Fedora Asahi Remix 40. For more details, see Alyssa’s talk and blog post , or head over to our documentation.

Fedora Asahi Remix is developed in close collaboration with the Fedora Asahi SIG and the Asahi Linux project. As part of our work on the Remix, we’ve also been working on a Change to integrate the FEX emulator into Fedora Linux 42. The goal is to provide a delightful out-of-box experience for users that want to run x86_32 and x86_64 binaries on their AArch64 systems. Today’s release provides a preview of this work. It allows us to perfect the integration and improve the experience on Apple Silicon systems. The aim is for Fedora KDE systems, on AArch64, to offer this functionality out of the box for all supported Fedora ARM desktop systems.

Please report any Remix-specific issues in our tracker. You may also reach out in our Discourse forum or our Matrix room for user support.

© 2016 Red Hat, Inc. and others. Please send any comments or corrections to the websites team.

The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community maintained site. Red Hat is not responsible for content.

Your words are your own, duh. Nothing here represents Fedora™, Red Hat, Inc, or pretty much anything else. If you think it does then you are badly misled