/rss20.xml">
fedora

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

Migration-Guide: From Windows to Fedora Linux

Posted by Fedora Magazine on 2025-01-22 18:20:51 UTC

This article provides a step-by-step guide to transitioning from Windows to Fedora Linux.

Motivation

Switching operating systems is a big step for many people – often accompanied by uncertainties. This is exactly the situation my parents are facing right now: Windows 10 will soon stop receiving updates, and Windows 11 hasn’t won them over. The design, new hardware requirements, and overall usability of Windows 11 just don’t align with what they want. At the same time, my mother still vividly remembers a frustrating experience she had with Ubuntu years ago, which convinced her that Linux, in general, was not for her.

This is where Fedora Linux comes into play. Fedora offers a modern, user-friendly, and stable platform that is ideal for both Linux newcomers and experienced users. Unlike Ubuntu, Fedora strikes a well-balanced mix of innovation and reliability without overwhelming the user with unnecessary restrictions. Fedora avoids proprietary software and privacy concerns often associated with other operating systems and provides an open, transparent environment that can be tailored to individual needs.

In this article, I want to demonstrate how the transition can be made as smooth as possible. Ultimately, Fedora should prove that Linux is not just a powerful tool for developers but also an excellent alternative for everyday use, even for skeptical users.

Step-by-Step Guide:

Before you start, check the recommended requirements for Fedora:

  • 2GHz dual core processor or faster
  • 4GB System Memory
  • 20GB unallocated drive space

Start

Switching to Fedora Linux can breathe new life into an older PC, and the process is easier than many people think. By following these steps, you can set up Fedora quickly and efficiently, without risking existing data or running into compatibility issues.

Get a new hard disk (Preferably an SSD):

For a fresh start, it’s highly recommended to use a new hard drive for the installation. This approach ensures that any existing data or configurations on the current drive remain untouched, providing peace of mind during the transition. An SSD (Solid State Drive) is the best choice for this purpose. SSDs are faster, more reliable, and have become very affordable. A 500GB SSD, for example, costs around 35€ and provides ample space for Fedora, applications, and personal files.

Prepare a Bootable Linux USB Stick:

The next step is to create a bootable USB stick with Fedora Linux. This will be used to install the operating system onto the new drive. Tools like Fedora Media Writer make this process incredibly simple.

  • Download the Fedora Media Writer and install it on any available PC or laptop.
  • Insert a USB stick with at least 8GB of free space.
  • Use the tool to download and load the Fedora installation image onto the USB stick.

This creates a portable installer that can be used to boot directly into Fedora on the target PC.

Install the New SSD in the Old PC:

With the USB stick ready, the next step is to install the new SSD in the PC. Opening the PC case and replacing or adding a drive is a straightforward process for most systems. Generally, this involves securing the SSD in an available slot and connecting it to the motherboard and power supply using the provided cables. For those unfamiliar with this process, online guides and videos can be very helpful.

Boot from the USB Stick:

After installing the new drive, power on the PC and access the boot menu (usually by pressing a key like F12, ESC, or DEL during startup). From the boot menu, select the USB stick as the boot device. If the USB device is listed in both a legacy/BIOS mode section and a UEFI section, it is recommended to select the UEFI option, as it is the more modern and secure boot method. This will load the Fedora live environment, allowing the system to boot into Fedora directly from the USB stick.

Install Fedora Linux:

Once in the live environment, the Fedora installer will guide you through the setup process step by step. The steps include:

  • Choosing basic settings such as language, keyboard layout, and time zone.
  • Selecting the new SSD as the target drive for installation. It is crucial to ensure that Fedora is installed on the new SSD and not on the old drive, especially if the old drive still contains important data or an existing operating system. Carefully review the drive selection in the installer to avoid overwriting the wrong drive.
  • Allowing the installer to automatically partition the SSD (a user-friendly option for most cases).

The installation process is quick and straightforward. After the installation is complete, the PC will prompt you to remove the USB stick and restart. On reboot, Fedora will launch from the new SSD.

Post Install steps:

Update your system & setup auto-updates

Keeping your system up-to-date is essential to ensure security, stability, and access to the latest features Fedora Linux has to offer. Fedora provides two easy ways to manage updates: through the graphical Software application and via the command line.

Updating Your System Using the Software Application

The graphical Software application makes updating your system simple and user-friendly. Here’s how you can update Fedora and set up auto-updates:

  • Open the Software application (you can find it in the application menu, often labeled “Software” or “Software Center”).
  • Navigate to the Updates tab, usually located at the top or in a side menu.
  • If updates are available, a list will be displayed. Review the updates and click Install to apply them.
  • To enable automatic updates:
    • Click on the menu icon (usually three dots or lines) in the top-right corner of the Software application.
    • Select Software Preferences or Settings.
    • Toggle the option for Automatic Updates to enable background updates for your system.
Updating Your System Using the Command Line

For users who prefer the command line, Fedora’s DNF package manager makes updating and enabling auto-updates simple and efficient. Follow these steps:

Update Your System Manually:

Open a terminal and run the following command to update all installed packages:

sudo dnf update

This command will list all available updates and prompt you to confirm their installation. Once confirmed, the system will download and install the updates.

Enable Automatic Updates:

To set up automatic updates, install the dnf-automatic package, which handles updates in the background:

sudo dnf install dnf-automatic

Once installed, enable and start the automatic update service:

sudo systemctl enable --now dnf-automatic.timer

This will schedule the system to check for and apply updates automatically based on Fedora’s default timer settings.

Customize Auto-Update Behavior (Optional):

If you want more control over how automatic updates work (e.g., applying updates silently or only notifying you about them), you can edit the configuration
file:

sudo nano /etc/dnf/automatic.conf

Adjust settings like apply_updates or download_updates as needed, save the file, and restart the service:

sudo systemctl restart dnf-automatic.timer
Which Method Should You Choose?

Both the Software application and the command line offer easy ways to keep your Fedora system updated. The Software application is perfect for beginners or those who prefer a graphical interface, while the command line is ideal for users who want more control or automation over their updates. Keeping your system updated is an important habit, and Fedora makes it simple, no matter which method you choose!

Other Desktops

The default desktop environment of Fedora Workstation is GNOME. It has a modern and unique design that doesn’t resemble the traditional look and feel of Windows. For users transitioning from Windows, this might feel unfamiliar at first. Fortunately, Fedora offers a variety of alternative desktop environments through its Fedora Spins. The Spins provide a curated list of officially supported desktop environments tailored to different preferences and workflows.

I recommend the Budgie Desktop for those switching from Windows. Its layout and functionality are intuitive, offering a familiar experience while retaining the performance and stability of GNOME.

To install the Budgie desktop environment, run the following command:

sudo dnf install @budgie-desktop

After the installation is complete, log out of your current session. On the login screen, select your user and look for a gear icon in the bottom right corner. Click it, and then select Budgie from the list of available desktop environments. Once you’ve selected Budgie, enter your password and log in. Your system will now start with the Budgie desktop environment.

How to Mount your old Windows Hard Drive and Enable Auto-Mounting

If you want to access your old Windows Hard Drive, you can easily mount it using the Disks application.

  1. Open the ‘Disks’ Application:
    In the Disks application, you will see a list of all connected storage devices in the left panel. Locate your Windows hard drive in the list (it will usually be listed by its model name or size).    Click on the hard drive to see detailed information about it, including the partitions.
  2. Mount the Windows Partition:
    Under the drive, you’ll see a list of partitions. Look for the NTFS partition (Windows typically uses NTFS for its file system). Select the NTFS partition and click on the Play button (a small triangle icon) to mount it. Fedora will mount the drive, and you should now be able to access the contents of the partition.
  3. Enable Automatic Mounting on Startup:
    To make sure that the Windows drive mounts automatically every time you boot up your system, follow these steps:
    • With the partition selected in the Disks application, click the Settings (gear) icon in the top-right corner.
    • Choose Edit Mount Options from the drop-down menu.
    • In the Mount Options window, uncheck User Session Defaults if it’s enabled.
    • Then, check the box for Mount at startup to ensure the drive is automatically mounted every time Fedora starts.
    • You can also adjust the Mount Point if you want the drive to mount to a specific folder.
    • Click OK to save the changes.
  4. Access the Mounted Drive
    Open the Files (Nautilus) application from the Activities overview. In the Devices section of the left sidebar, you will see the mounted Windows drive listed. Click on it to browse the contents of the drive and access your files.

Setting Up Additional Repositories (RPM Fusion) and Installing NVIDIA Drivers

Disclaimer:
This guide will help you install additional software using the RPM Fusion repositories. Please be aware that some of the software available through RPM Fusion is proprietary and may require proprietary online services. Such software and services might employ aggressive monetization strategies and raise privacy concerns due to anti-tamper tools and user analytics. The choice to use or not to use this software and services is entirely yours.

To enhance the functionality of your Fedora system, you may want to install additional software, such as proprietary drivers (like NVIDIA graphics drivers) and multimedia codecs, which are not available in the official Fedora repositories due to licensing restrictions. This can be easily done by enabling the RPM Fusion repositories.

Enabling RPM Fusion Repositories

RPM Fusion provides free and non-free software packages for Fedora, including software for multimedia, gaming, and drivers.

  1. Open a Terminal and run the following command to enable the free RPM Fusion repository (for open-source software):

    sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm

  2. For non-free software (such as proprietary NVIDIA drivers, Flash, etc.), run:

    sudo dnf install https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm

These commands will install both the free and non-free RPM Fusion repositories on your system, giving you access to a wide range of additional software.

Installing NVIDIA Drivers

If you are using an NVIDIA graphics card, you can install the official proprietary drivers for better performance, particularly for gaming or heavy graphical tasks.

Important:
If your NVIDIA graphics card is older than 2014, please visit the RPM Fusion NVIDIA How-to-Page for the correct packages for your card. Follow the instructions provided on the page to ensure compatibility with your system.

  1. Enable the RPM Fusion Non-Free repository as shown in the previous section.

  2. Install the NVIDIA driver by running the following command:

    sudo dnf install akmod-nvidia

    This package will automatically build the NVIDIA kernel module on your system, ensuring compatibility with new kernel versions.

    Important:
    After installing the NVIDIA driver using akmod-nvidia, the system will build the kernel module. This process might take some time. The system typically warns you if this process is still running when you attempt a reboot, but using sudo reboot will bypass this warning, which can lead to unexpected issues. To ensure the build process has completed before rebooting, check if akmods is still running by using the commands top or ps -e | grep akmod

  3. Optional: Install additional NVIDIA packages for a more complete setup (such as utilities):

    sudo dnf install xorg-x11-drv-nvidia-cuda

  4. Reboot your system to apply the changes. The NVIDIA drivers should now be active, and you can confirm this by running:

    nvidia-smi

    This command ( provided by the xorg-x11-drv-nvidia-cuda package ) should show you the details of your NVIDIA GPU.

Further information:

Christmas Movies

Posted by Jonathan McDowell on 2025-01-22 13:32:00 UTC

I watch a lot of films. Since “completing” the IMDB Top 250 back in 2016 I’ve kept an eye on it, and while I don’t go out of my way to watch the films that newly appear in it I generally sit at over 240 watched. I should note I don’t consider myself a film buff/critic, however. I watch things for enjoyment, and a lot of the time that’s kicking back and relaxing and disengaging my brain. So I don’t get into writing reviews, just high level lists of things I’ve watched, sometimes with a few comments.

With that in mind, let’s talk about Christmas movies. Yes, I appreciate it’s the end of January, but generally during December we watch things that have some sort of Christmas theme. New ones if we can find them, but also some of what we consider “classics”. This almost always starts with Scrooged after we’ve put up the tree. I don’t always like Bill Murray (I couldn’t watch The Life Aquatic with Steve Zissou and I think Lost in Translation is overrated), but he’s in a bunch of things I really like, and Scrooged is one of those.

I don’t care where you sit on whether Die Hard is a Christmas movie or not, it’s a good movie and therefore regularly gets a December watch. Die Hard 2 also fits into that category of “sequel at least as good as the original”, though Helen doesn’t agree. We watched it anyway, and I finally made the connection between the William Sadler hotel scene and Michael Rooker’s in Mallrats.

It turns out I’m a Richard Curtis fan. Love Actually has not aged well; most times I watch it I find something new questionable about it, and I always end up hating Alan Rickman for cheating on Emma Thompson, but I do like watching it. He had a new one, That Christmas, out this year, so we watched it as well.

Another new-to-us film this year was Spirited. I generally like Ryan Reynolds, and Will Ferrell is good as long as he’s not too overboard, so I had high hopes. I enjoyed it, but for some reason not as much as I’d expected, and I doubt it’s getting added to the regular watch list.

Larry doesn’t generally like watching full length films, but he (and we), enjoyed The Grinch, which I actually hadn’t seen before. He’s not as fussed on The Muppet Christmas Carol, but we watched it every year, generally on Christmas or Boxing Day. Favourite thing I saw on the Fediverse in December was “Do you know there’s a book of The Muppet Christmas Carol, and they don’t mention that there’s muppets in it once?”

There are a various other light hearted Christmas films we regularly watch. This year included The Holiday (I have so many issues with even just the practicalities of a short notice house swap), and Last Christmas (lots of George Michael music, what’s not to love? Also it was only on this watch through that we realised the lead character is the Mother of Dragons).

We started, but could not finish, Carry On. I saw it described somewhere as copaganda, and that feels accurate. It does not accurately reflect any of my interactions with TSA at airports, especially during busy periods.

Things we didn’t watch this year, but are regularly in the mix, include Fatman, Violent Night (looking forward to the sequel, hopefully this year), and Lethal Weapon. Klaus is kinda at the other end of the spectrum, but very touching, and we’ve watched it a couple of years now.

Given what we seem to like, any suggestions for other films to add? It’s nice to have enough in the mix that we get some variety every year.

Prioritizing work in the project with the MoSCoW method

Posted by Ben Cotton on 2025-01-22 12:00:00 UTC

Open source projects typically have more work to do than time to do it. So how do you decide what to do first? The easiest way is to let everyone work on what they find most interesting. This gives your volunteer contributors autonomy, which can be an important factor in keeping them around. Often this works out fine, but sometimes you need to work in a more coordinated manner.

The MoSCoW method

When working as a team, or even putting together a wish list of what you’d like to see people work on, how do you prioritize work? There are countless methodologies to pick from, and if you already have one that works for you, great! If not, I like the MoSCoW method. In the MoSCoW method, you put the work into one of four categories:

  • Must have: the work that absolutely has to get done
  • Should have: important, but not necessary work
  • Could have: work that you’ll do if you have time
  • Won’t have: work that you know won’t get done

Typically, you do this on a regular basis with a defined time that you’re working on. So you might do it each release cycle, or each month, or something like that. If you find you have a lot of the work in one of the first two categories, you get more strict and re-iterate. In most cases, you’ll find that very few things truly fall into the “must have” category.

What I like about the MoSCoW method is that it’s conceptually simple. The categories are easy to understand, with simple language that works regardless of someone’s English proficiency. It doesn’t require calculations or estimates.

Refining priorities in a category

The downside to the MoSCoW method is that it doesn’t offer any way to prioritize the work within a category. Of all of the “should have” work, which should you do first? As I wrote in chapter 1 of Program Management for Open Source Projects, there are a few principles that can guide your decisions.

  • Prefer finishing work. If there you have multiple-stage features, it’s generally better to get one all the way done instead of starting on a new one. This fits the Unix philosophy of “do one thing well” and also gives your community a sense of accomplishment. Psychologically, it feels much better to have something done.
  • Maximize the total benefit. Think about benefits in two dimensions: the number of people who receive the benefit and the amount of benefit they receive. Something that saves 100 of your contributors an hour of effort a month is likely more important than something that saves 10 contributors three hours a month.
  • Reward the longsuffering. Of course, if the same 10 people keep not getting the benefits, they’ll get mad and go somewhere else. From time to time, you want to jump something to the top of the stack as a way to reward particularly hard-working or patient contributors.
  • Expand the community. Work that makes it easier for new users or contributors to join will have a huge payoff in the long run. Like the “prefer usability” point above, the idea is to get people into the community so that they’ll stick around to help with future work.

Ultimately, though, you don’t need to spend much time worrying about prioritizing within a category. The “must have” work all needs to get done, pick anything and start doing it. The rest is optional, so do what’s interesting and/or easy.

This post’s featured photo by airfocus on Unsplash.

The post Prioritizing work in the project with the MoSCoW method appeared first on Duck Alignment Academy.

Infrastructure & Release Engineering Summary 2024

Posted by Fedora Community Blog on 2025-01-21 10:00:00 UTC

This is a summary of the work done by Fedora Infrastructure & Release Engineering teams as of 2024. As these teams are working closely together, we will summarize the work done in one blog post by both teams.

This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.

I&R 2024 Infographic

About

Purpose of these teams is to take care of day-to-day business regarding Fedora Infrastructure and Fedora Release Engineering work. It’s responsible for developing and maintaining services running in Fedora and preparing things for the new Fedora Linux release (mirrors, mass branching, new namespaces etc.). 

Issue trackers

Closed tickets

  • Fedora Infrastructure – 609
  • Fedora RelEng – 573

Fedora Infrastructure highlights

Fedora Release Engineering highlights

ARC Investigations

ARC (Advance Reconnaissance Crew) is a part of Infra & Releng Team that is doing investigation of upcoming big infrastructure projects in Fedora.

Git forge evaluation

Description:

The investigation involved validating user stories received from multiple subprojects and SIGs within Fedora Project to understand how well GitLab CE and Forgejo fared with the needs of the community, under Fedora Council’s direction. It also involved a limited research on the resource requirements for platform migration along with the changes in the ecosystem applications. 

Status: Finished

Outcomes: 

  1. https://fedora-arc.readthedocs.io/en/latest/dist-git-comparison/index.html 
  2. https://fedoramagazine.org/fedora-moves-towards-forgejo-a-unified-decision/

The post Infrastructure & Release Engineering Summary 2024 appeared first on Fedora Community Blog.

End of Life of github2fedmsg

Posted by Fedora Community Blog on 2025-01-20 09:56:08 UTC

As was already announced in Announcing Webhook To Fedora Messaging Fedora Infrastructure team is working on replacement of github2fedmsg service. As the replacement is already deployed and users already had a few months to migrate to webhook2fedmsg we decided to say goodbye to github2fedmsg. The date that github2fedmsg will be decommissioned in fedora infra is 3rd February. 

If you are using github2fedmsg and didn’t migrate to webhook2fedmsg yet, please follow the steps in the previous announcement mentioned at the beginning of this article.

Following are the reasons for the replacement of github2fedmsg:

  • Old codebase with not much test coverage
  • Last version released 10 years ago
  • Running on now EOL RHEL7 machine
  • Last service still using deprecated fedmsg (fedmsg it will go away with github2fedmsg)
  • Support only for GitHub

The post End of Life of github2fedmsg appeared first on Fedora Community Blog.

Fedora Operations Architect Report

Posted by Fedora Community Blog on 2025-01-19 23:07:57 UTC

Welcome to 2025 fellow Fedorans, and what a year it’s going to be! We are in the middle of development for the Answer to life, the universe and everything release, plus we are starting to plan our eventual migration to a new git forge. And Im sure theres a lot more ‘fun’ stuff to look forward to too, we just might not know what they are yet 😉 Below is a short roundup from some things around the project if you care to read on 🙂

Fedora Linux 42

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

  • All submission deadlines for system wide and self-contained changes have now passed. Please target F43 or later for any proposals you may have
  • February 4th – Changes need to be Testable
  • February 4th – Branching
  • February 18th – Changes need to be Complete
  • February 18th – Beta Freeze

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

Fedora Linux 43

From 8th February 2025, we will be in F43 development. Please bookmark our schedule for some key dates for Changes, mass rebuild, branching, etc.

Hot Topics

Join the Git Forge open meetings every Wednesday @ 1400 UTC in #fedora-meeting on matrix. The meeting is in Fedocal in the Fedora Release calendar and its an open meeting to join and ask questions on whats happening, and how to help with the work. The first meeting happened last week and a summary was posted to discussion.fpo. You can find all the links that were shared too from that post, or from the meetbot logs.

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

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!

Events

FOSDEM 2025 returns on Saturday 1st and Sunday 2nd February in Brussels, Belgium. If you are attending and want to connect with some folks from around the Fedora Project, you can add your name to the Fedora @ FOSDEM wiki page.

CentOS Connect also returns to Brussels on 30th and 31st January 2025. For more information and to register for the event, check out the event page.

KubeCon and CloudNativeCon Europe is coming up in London, United Kingdom from April 1st – 4th, and registration is still open to attend.

Open Source Summit North America cfp is open until February 17th, so don’t delay if you want to submit your talk idea(s) to attend this years event in Denver, Colorado on June 23rd – 25th.

Devconf.cz call for papers is open! The event will take place in Brno, Czechia on June 12th – 14th 2025. Be sure to visit their event website for more information on talk themes, tracks and general stuff about the conference.

Flock to Fedora is in Europe this year, in June! We will have more information to share with you in the coming week – cfp and event information, but be sure to earmark June (hint – the week before or after devconf.cz) as we would love to see as many folks from our wonderfully diverse and interesting community as possible there.

Media Things

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!

Missed some of Fedoras recent release watch parties? Never fear! All talks are now available on the Fedora Youtube Channel in the ‘latest’ video tab. Happy Streaming!

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

Bits from mid jan 2025

Posted by Kevin Fenzi on 2025-01-18 18:07:41 UTC
Scrye into the crystal ball

Hello again, here's some longer form doings and thoughts from from mid january 2025 in and around fedora.

rawhide repodata change

Rawhide repodata has moved over to the createrepo_c default: zstd. This shouldn't affect any dnf use, or fedora createrepo_c use, but if you are using EL8/EL9, createrepo_c there currently doesn't understand zstd. There's a issue to add that in a minor release: https://issues.redhat.com/browse/RHEL-67689 and in the mean time if you are a EL8/9 user there's a copr: https://copr.fedorainfracloud.org/coprs/amatej/createrepo_c/

dist-repos retention

On the dist-repos space issue I mentioned last week, it turns out that the expectation on dist-repos is that you would sync them somewhere you wanted to serve them from, not just serve from koji. So our use case was misalined a bit from upstream here. However, they did adjust to keep latest repos. Should be in a upcoming koji release. Thanks koji folks!

fun email infrastructure mixup between ipa and postfix

There was a pretty curious email issue that came up this last week. fedoraproject contributors (that is folks with an account that is in at least one non system group) are setup with an email alias of theiraccountlogin@fedoraproject.org. This is just a very simple alias. We accept the email and forward it to their real email address. There's no mailbox here or authentication or anything, just a simple alias. We got an alert that disk space was getting low on our mail hub, so I took a look and found that users who were not contributors were getting emails to theiraccountlogin@fedoraproject.org delivered locally to /var/spool/mail on the hub! When we switched away from fas2 to our current IPA based setup, no one realized that sssd/ipa enumerates all users, even if they do not have access to actually login or do anything. There are good reasons for this, but somehow I at least didn't realize that it worked that way. So, since all users 'existed' there, and postfix's default for local users is:

proxy:unix:passwd.byname $alias_maps

It correctly looks them up and thinks they are local. Simply changing this to just be $alias_maps fixes the issue. There wasn't a bug here in postfix or ipa, they were just doing things as they expected. The issue was our misunderstanding how these things interacted.

f42 mass rebuild underway

The mass rebuild for f42 started (all be it a bit later than planned due to a issue getting golang to work on i686 when compiled with gcc 15). This time it seems like our submitting builds is much slower than before. In past years, pretty much everything was submitted in a few days, then koji chewed on the backlog. This time koji is easily keeping up with the submissions and we are only in the 'p's after 3.5 days. Oh well, hopefully we will finish mondayish, which is in line with past mass rebuilds.

forgejo kickoff meeting/discussions

There was a kickoff meeting about forgejo in fedora infra. I'm looking forward to this, but I have so many things going on I am not sure how much work I can do on the deployment. Lots of good ideas/plans discussed. I think it's going to be not a super lot of work to stand up a staging instance, but I think integrating with all our workflows will take a lot more effort. Time will tell.

riscv secondary koji hub

I did finally submit my work in progress PR for riscv-koji hub: https://pagure.io/fedora-infra/ansible/pull-request/2435 Hopefully can finish off things and start deploying next week.

bugzilla and needinfo

I asked on mastodon what folks thought about bugzilla needinfo requests and what they meant. There were a number of opinions: https://fosstodon.org/@nirik/113822583672492457 I think in the end it's a thing that people will use for their own use cases and those will sometimes mis match with recipients. Unless we want to try and make some community wide norm or guidelines (but of course even then not everyone will see those).

Xfce-4.20 and wayland testing

News from a while ago: Xfce 4.20 was released and it's got a bunch of wayland support for various things. However, it doesn't have xfwm4 / a compositor of it's own, so by default you get a X session. If you want to play with the wayland sessions and you are running a rawhide instance, you can install: xfce4-session-wayland-session which will by default pull in labwc as your compositor. You can manually modify the session file to use wayfire if you prefer that compositor. See the testing section at https://wiki.xfce.org/releng/wayland_roadmap I tried both out and they did indeed work, but there are still a bunch of rough edges. Still, great progress!

comments? additions? reactions?

As always, comment on mastodon: https://fosstodon.org/@nirik/113850897869803740

Dealing with egl_bad_alloc error for webkit

Posted by Kushal Das on 2025-01-18 07:43:01 UTC

I was trying out some Toga examples, and for the webview I kept getting the following error and a blank screen.

Could not create EGL surfaceless context: EGL_BAD_ALLOC.

After many hours of searching I reduced the reproducer to a simple Python Gtk code.

import gi

gi.require_version('Gtk', '3.0')
gi.require_version('WebKit2', '4.0')

from gi.repository import Gtk, WebKit2

window = Gtk.Window()
window.set_default_size(800, 600)
window.connect("destroy", Gtk.main_quit)

scrolled_window = Gtk.ScrolledWindow()
webview = WebKit2.WebView()
webview.load_uri("https://getfedora.org")
scrolled_window.add(webview)

window.add(scrolled_window)
window.show_all()
Gtk.main()

Finally I asked for help in #fedora IRC channel, within seconds Khaytsus gave me the fix:

WEBKIT_DISABLE_COMPOSITING_MODE=1 python g.py

working webview

⚙️ PHP version 8.3.16 and 8.4.3

Posted by Remi Collet on 2025-01-17 05:51:00 UTC

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

RPMs of PHP version 8.3.16 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.31 and version 8.2.27.

⚠️ 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:

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

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

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

Parallel installation of version 8.4 as Software Collection

yum install php84

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

And soon in the official updates:

⚠️ To be noticed :

  • EL-10 RPMs are built using RHEL-10.0-beta
  • EL-9 RPMs are built using RHEL-9.5
  • EL-8 RPMs are built using RHEL-8.10
  • intl extension now uses libicu74 (version 74.2)
  • mbstring extension (EL builds) now uses oniguruma5php (version 6.9.10, instead of the outdated system library)
  • oci8 extension now uses the RPM of Oracle Instant Client version 23.6 on x86_64, 19.25 on aarch64
  • a lot of extensions are also available, see the PHP extensions RPM status (from PECL and other sources) page

ℹ️ Information:

Base packages (php)

Software Collections (php81 / php82 / php83)

Infra and RelEng Update – Week 03 2025

Posted by Fedora Community Blog on 2025-01-17 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: 13 – 17 January 2025

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 I&R Team

Major update of Anitya from 1.10.0 to 2.0.0 on 2025-01-10: https://github.com/fedora-infra/anitya/releases/tag/2.0.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 03 2025 appeared first on Fedora Community Blog.

Changing Plymouth’s theme

Posted by Alejandro Sáez Morollón on 2025-01-17 09:09:50 UTC

This is a quick note for my future self and for anyone who runs a system with Plymouth (Fedora for example). It’s the thingy that makes appear the Fedora logo and the spinner instead of a cold & dry log of what the system is doing.

The thing is… I like the cold & dry log. So I usually enable it when I reinstall my machines. And this is what I do:

$ sudo plymouth-set-default-theme -l
bgrt
details
spinner
text
tribar
$ sudo plymouth-set-default-theme -R details
$ sudo plymouth-set-default-theme 
details
$

Side note: Yes, my prompt is just a $. It’s also good for examples.

details prints the logs, bgrt is the default one. The -R will rebuild for you the initrd which is mandatory to see the changes. And that’s what leads me to the second thing.

What about Atomic versions like Fedora Silverblue? Isn’t the whole thing managed by rpm-ostree in a non-mutable manner? Yes, and if you try to do the same in a rpm-ostree based system, you’ll find yourself with this:

$ sudo plymouth-set-default-theme -R details
dracut[F]: Can't write to /boot/efi/1582e7b46c3b44de9db824dd6aacd62d/6.13.0-0.rc7.20250114gitc45323b7560e.56.fc42.x86_64: Directory /boot/efi/1582e7b46c3b44de9db824dd6aacd62d/6.13.0-0.rc7.20250114gitc45323b7560e.56.fc42.x86_64 does not exist or is not accessible
$

That’s what makes me write the post. Because I always keep writing it with -R.

The solution is easy. Just don’t ask Plymouth to rebuild the initrd and do it after it with rpm-ostree:

$ sudo plymouth-set-default-theme details
$ sudo rpm-ostree initramfs --enable
Checking out tree fabf6f9... done
Generating initramfs... done
Writing OSTree commit... done
Staging deployment... done
Freed: 2.8 GB (pkgcache branches: 0)
Initramfs regeneration is now: enabled
$

Reboot and that’s it.

As you can see, I’m boring, and I like to see the logs, so I don’t play with customization that much, but I found this repo with plenty of cool themes in case that’s your thing.

🛡️ PHP version 8.1.30, 8.2.24 and 8.3.12

Posted by Remi Collet on 2024-09-27 06:33:00 UTC

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

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

RPMs of PHP version 8.1.30 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-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.

security-medium-2-24.pngThese Versions fix 4 security bugs (CVE-2024-8925, CVE-2024-8926, CVE-2024-8927, CVE-2024-9026), so update is strongly recommended.

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)

🎲 PHP 8.4 as Software Collection

Posted by Remi Collet on 2024-07-05 13:59:00 UTC

Version 8.4.0alpha1 has been released. It's still in development and will enter soon in the stabilization phase for the developers, and the test phase for the users (see the schedule).

RPM of this upcoming version of PHP 8.4, are available in remi repository for Fedora ≥ 38 and Enterprise Linux ≥ 8 (RHEL, CentOS, Alma, Rocky...) in a fresh new Software Collection (php84) allowing its installation beside the system version.

As I (still) strongly believe in SCL's potential to provide a simple way to allow installation of various versions simultaneously, and as I think it is useful to offer this feature to allow developers to test their applications, to allow sysadmin to prepare a migration or simply to use this version for some specific application, I decide to create this new SCL.

I also plan to propose this new version as a Fedora 42 change (as F41 should be released a few weeks before PHP 8.4.0).

Installation :

yum install php84

emblem-important-2-24.pngTo be noticed:

  • the SCL is independent from the system and doesn't alter it
  • this SCL is available in remi-safe repository (or remi for Fedora)
  • installation is under the /opt/remi/php84 tree, configuration under the /etc/opt/remi/php84 tree
  • the FPM service (php84-php-fpm) is available, listening on /var/opt/remi/php84/run/php-fpm/www.sock
  • the php84 command gives simple access to this new version, however, the module or scl command is still the recommended way.
  • for now, the collection provides 8.4.0-alpha1, and alpha/beta/RC versions will be released in the next weeks
  • some of the PECL extensions are already available, see the extensions status page
  • tracking issue #258 can be used to follow the work in progress on RPMS of PHP and extensions
  • the php84-syspaths package allows to use it as the system's default version

emblem-notice-24.pngAlso, read other entries about SCL especially the description of My PHP workstation.

$ module load php84
$ php --version
PHP 8.4.0alpha1 (cli) (built: Jul  2 2024 13:43:13) (NTS gcc x86_64)
Copyright (c) The PHP Group
Zend Engine v4.4.0-dev, Copyright (c) Zend Technologies
    with Zend OPcache v8.4.0alpha1, Copyright (c), by Zend Technologies

As always, your feedback is welcome on the tracking ticket, a SCL dedicated forum is also open.

Software Collections (php84)

🎲 PHP on the road to the 8.4.0 release

Posted by Remi Collet on 2024-09-27 08:31:00 UTC

Version 8.4.0 Release Candidate 1 is released. It's now enter the stabilisation phase for the developers, and the test phase for the users.

RPMs are available in the php:remi-8.4 stream for Fedora ≥ 39 and  Enterprise Linux ≥ 8 (RHEL, CentOS, Alma, Rocky...) and as Software Collection in the remi-safe repository (or remi for Fedora)

 

emblem-important-4-24.pngThe repository provides development versions which are not suitable for production usage.

Also read: PHP 8.4 as Software Collection

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

Replacement of default PHP by version 8.4 installation, module way (simplest way):

dnf module reset php
dnf module install php:remi-8.4
dnf update

Parallel installation of version 8.4 as Software Collection (recommended for tests):

yum install php84

emblem-important-2-24.pngTo be noticed :

emblem-notice-24.pngInformation, read:

Base packages (php)

Software Collections (php84)

⚙️ PHP version 8.2.21 and 8.3.9

Posted by Remi Collet on 2024-07-05 05:17:00 UTC

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

RPMs of PHP version 8.2.21 are available in the remi-modular repository for Fedora ≥ 38 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.29.

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 libicu73 (version 73.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 21.13 on x86_64, 19.23 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)

⚙️ PHP version 8.2.22 and 8.3.10

Posted by Remi Collet on 2024-08-02 05:37:00 UTC

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

RPMs of PHP version 8.2.22 are available in the remi-modular repository for Fedora ≥ 38 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.29.

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 libicu73 (version 73.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.23 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)

⚙️ PHP version 8.2.23 and 8.3.11

Posted by Remi Collet on 2024-08-30 05:59:00 UTC

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

RPMs of PHP version 8.2.23 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.29.

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 libicu73 (version 73.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.23 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)

⚙️ 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)

🎲 PHP version 8.2.22RC1 and 8.3.10RC1

Posted by Remi Collet on 2024-07-19 05:54: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.10RC1 are available

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

RPMs of PHP version 8.2.23RC1 are available

  • as base packages in the remi-modular-test for Fedora 38-40 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.3.10RC1 is also in Fedora rawhide for QA
  • version 8.4.0alpha2 is also available in the repository
  • EL-9 packages are built using RHEL-9.4
  • EL-8 packages are built using RHEL-8.10
  • EL-7 packages are built using RHEL-7.9
  • oci8 extension uses the RPM of the Oracle Instant Client version 23.4 on x86_64 or 19.23 on aarch64
  • intl extension uses libicu 73.2
  • RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
  • versions 8.2.22 and 8.3.10 are planed for August 1st, in 2 weeks.

Software Collections (php82, php83)

Base packages (php)

🎲 PHP version 8.2.23RC1 and 8.3.11RC1

Posted by Remi Collet on 2024-08-16 05:36: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.11RC1 are available

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

RPMs of PHP version 8.2.23RC1 are available

  • as base packages in the remi-modular-test for Fedora 38-40 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.3.11RC1 is also in Fedora rawhide for QA
  • version 8.4.0beta4 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.4 on x86_64 or 19.24 on aarch64
  • intl extension uses libicu 73.2
  • RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
  • versions 8.2.23 and 8.3.11 are planed for August 29th, in 2 weeks.

Software Collections (php82, php83)

Base packages (php)

🎲 PHP version 8.2.24RC1 and 8.3.12RC1

Posted by Remi Collet on 2024-09-13 08:59: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.12RC1 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.24RC1 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.3.11RC1 is also in Fedora rawhide for QA
  • version 8.4.0beta5 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.24 and 8.3.12 are planed for September 26th, in 2 weeks.

Software Collections (php82, php83)

Base packages (php)

🎲 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.26RC1 and 8.3.14RC1

Posted by Remi Collet on 2024-11-08 05:52: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.14RC1 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.26RC1 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.0RC4 is in Fedora rawhide for QA
  • version 8.4.0RC4 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.1.31, 8.2.26 and 8.3.14

Posted by Remi Collet on 2024-11-21 08:46:00 UTC

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

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

RPMs of PHP version 8.1.31 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-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.

security-medium-2-24.pngThese Versions fix 6 security bugs (CVE-2024-11233, CVE-2024-11234, CVE-2024-11236, CVE-2024-8929, CVE-2024-8932), so update is strongly recommended.

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-10 RPMs are built using RHEL-10.0-beta
  • 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.6 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)

© 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