fidzu : Fedora

10 Dec 2025 12:30pm GMT

08 Dec 2025 1:00pm GMT

08 Dec 2025 5:00am GMT

hey everyone, it's saturday so time for another recap of adventures in fedora infrastructure and other fedora areas.

06 Dec 2025 7:29pm GMT

06 Dec 2025 4:30pm GMT

Have not been the best health wise recently, we are enjoying life and carrying on though.

Because the Fedora Project removes access levels after 12 months of inactivity, I was required to file a ticket as a returning developer of the 'packager' group. This was processed very quickly by Kevin Fenzi and all my access level restored. Kevin is always extremely helpful though he is always busy ... busy.

Current activities are bringing packages from Fedora into Extra Packages for Enterprise Linux (EPEL) in order to have more science and astronomy packages available on Enterprise Linux (EL).

Java being a language I do prefer to code, I am also trying to get useful packages into or back into Fedora. Once done they can be looked at possible inclusion in EPEL.

I have another couple of projects in the early stages and more details will follow in future posts. One I am very excited about and will involve design, engineering and manufacture of the prototype.

Watch this space for this years Christmas sweater post.

06 Dec 2025 10:11am GMT

TL;DNR: The Fedora Linux 43 Election schedule has been extended. Voting will now take place from 15 December 2025 through 7 January 2026.

Due to unforeseen delays in the interview coordination process, we are adjusting the election timeline. To ensure all candidates have ample opportunity to present their platforms and the community has sufficient time to vote, the election period will now extend through the year-end holidays.

Please mark your calendars with the following new critical dates:

New Election Schedule

• Interview Submission Deadline (Extended): Now through Friday, 12 December 2025 at 23:59 UTC (Candidates: Please ensure your responses are submitted by this time.)
• Voting Setup & Interview Publishing: Monday, 15 December 2025 (Voter guides and interviews will be published to the community on this date.)
• Voting Period Opens: Monday, 15 December 2025
• Voting Period Closes: Wednesday, 7 January 2026 at 23:59 UTC

Context on the Schedule Change

Transparency is an important value of the Fedora Project, and I want to provide context on why this shift was necessary. I recently returned from two weeks of bereavement leave on Wednesday, 3 December. During my absence, the coordination work required to collect and process nominee interviews for the Fedora Engineering Steering Committee (FESCo) did not occur as originally planned.

Consequently, we missed the window to launch the elections today, Friday, 5 December. Rather than rushing the process, we are opting to extend the timeline. This ensures that our candidates are properly featured and that the election remains fair and accessible to all voters, despite the holiday season overlap.

The official Fedora schedule calendar is being updated to reflect these changes shortly. Thank you for your patience and understanding.

The post Important Update: Fedora Linux 43 Election Schedule Extended appeared first on Fedora Community Blog.

05 Dec 2025 3:43pm GMT

This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infratructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project.

Week: December 1 - December 5 2025

Fedora Infrastructure

This team is taking care of day to day business regarding Fedora Infrastructure.
It's responsible for services running in Fedora infrastructure.
Ticket tracker

• Pagure.io migration happened earlier in the week, expected disruption during that (https://status.fedoraproject.org for details)
• RDU2-CC -> RDU3 DC move next week
• OpenID finally has a date to be retired - we have a separate OpenID instance of Ipsilon that serves a warning (ticket)
• Weblate legal issues raised by the community to the Council
• Survived Thanksgiving without major fires
• Ongoing work on the Keycloak migration

CentOS Infra including CentOS CI

This team is taking care of day to day business regarding CentOS Infrastructure and CentOS Stream Infrastructure.
It's responsible for services running in CentOS Infratrusture and CentOS Stream.
CentOS ticket tracker
CentOS Stream ticket tracker

• Migrate dev repo to rdu3
• Mirror: Update CERN IPs
• Decommission RDU2 hardware (unused)
• Modify backup script to cover new Netapp NFS storage plan
• [SN#1579] Migrate CentOS Infra/services running from community cage to new DC
• Create calligrabot pull request with signing fix
• Migrate calligrabot

Release Engineering

This team is taking care of day to day business regarding Fedora releases.
It's responsible for releases, retirement process of packages and package builds.
Ticket tracker

• Please update f43-image-builder target to use an appropriate Destination Tag.
• set released_on date field in Bodhi Release metadata

RISC-V

• (Things are chugging along.)
• F43 rebuild is still ongoing. The diff with primary arch is now about ~1K packages. Still ironing out some rough edges. (A bug with "debugedit" is affecting a number of packages.)
• Jason Montleon published some board-specific F43 kernels.
• We're working on putting together the RISC-V devroom at FOSDEM.

Forgejo

Updates of the team responsible for Fedora Forge deployment and customization.
Ticket tracker

• Handled empty dates in Pagure milestone migration in the Forgejo upstream [Issue] [PR]
• Initial preparation work being carried out to deploy the Forgejo "dist-git" instance - konflux pipelines for distgit are ready, with images with stable fedora available on quay.
• 5+ new teams have organizations on Forge now.
• Forgejo runners can be scoped to global/organization/individual on staging.
• [Docs] Starting to migrate select repositories, first one to be the Release Notes

QE

• A first QE repo got migrated from Pagure to Fedora Forge production server, as a guinea pig. A set of helper scripts were created to perform necessary post-migration tasks (see more in the AI section).
• New test suite for Fedora Media Writer has been finished and is waiting for review
• FreeIPA webUI test day is ongoing
• Finally fixed a longstanding bug that broke all openQA encrypted install test cases on aarch64 (with an assist from Jeremy Linton)

If you have any questions or feedback, please respond to this report or contact us on #admin:fedoraproject.org channel on matrix.

The post Community Update - Week 49 appeared first on Fedora Community Blog.

05 Dec 2025 2:00pm GMT

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 parallel installation, the perfect solution for such tests, and as base packages.

RPMs of PHP version 8.5.1RC1 are available

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

RPMs of PHP version 8.4.16RC1 are available

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

RPMs of PHP version 8.3.29RC1 are available

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

ℹ️ The packages are available for x86_64 and aarch64.

ℹ️ PHP version 8.2 is now in security mode only, so no more RC will be released.

ℹ️ Installation: follow the wizard instructions.

ℹ️ Announcements:

• PHP 8.5.1RC1 available for testing
• PHP 8.4.16RC1 available for testing
• PHP 8.3.29RC1 available for testing

Parallel installation of version 8.5 as Software Collection:

yum --enablerepo=remi-test install php85

Parallel installation of version 8.4 as Software Collection:

yum --enablerepo=remi-test install php84

Parallel installation of version 8.3 as Software Collection:

yum --enablerepo=remi-test install php83

Update of system version 8.5:

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

Update of system version 8.4:

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

Update of system version 8.3:

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

ℹ️ Notice:

• version 8.5.1RC1 is in Fedora rawhide for QA
• EL-10 packages are built using RHEL-10.1 and EPEL-10.1
• EL-9 packages are built using RHEL-9.7 and EPEL-9
• EL-8 packages are built using RHEL-8.10 and EPEL-8
• oci8 extension uses the RPM of the Oracle Instant Client version 23.9 on x86_64 and 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.3.29, 8.4.16 and 8.5.1RC1 are planed for December 18th, in 2 weeks.

Software Collections (php83, php84, php85)

Base packages (php)

05 Dec 2025 8:58am GMT

05 Dec 2025 5:00am GMT

Wait, what? RISC-V? In 'the diary of AArch64 porter'? WTH?

Yes, I started working on Fedora packaging for the 64-bit RISC-V architecture port.

All started with discussion about Mock

About a week ago, one of my work colleagues asked me about my old post about speeding up Mock. We had a discussion, I pointed him to the Mock documentation, and gave some hints.

It turned out that he was working on RISC-V related changes to Fedora packages. As I had some spare cycles, I decided to take a look. And I sank…

State of the RISC-V Fedora port

The 64-bit RISC-V port of Fedora Linux is going quite well. There are over 90% of Fedora packages already built for that architecture. And there are several packages with the riscv64 specific changes, such as:

• patches adding RISC-V support
• disabling some parts of test suites
• disabling some build options due to bootstrapping of some languages being in progress (like Java)
• disabling of debug information due to some toolchain issues (there is a work-in-progress now to solve them)

Note that these changes are temporary. There are people working on solving toolchain issues, languages are being bootstrapped (there was a review of Java changes earlier this week), patches are being integrated upstream and in Fedora, and so on.

There is the Fedora RISC-V tracker website showing the progress of the port:

• package name
• current status (new, triaged, patch posted, patch merged, done)
• version in RISC-V port Koji
• version in Fedora Koji (F43 release is tracked now)
• version in CentOS Stream 10
• notes

This is a simple way to check what to work on. And there are several packages, not built yet due to use of "ExclusiveArch" setting in them.

My work

The quick look at work needed reminded me of the 2012-2014 period, when I worked on the same stuff but for AArch64 ports (OpenEmbedded, Debian/Ubuntu, Fedora/RHEL). So I had a knowledge, I knew the tools and started working.

In the beginning, I went through entries in the tracker and tried to triage as many packages as possible, so it will be more visible which ones need work and which can be ignored (for now). The tracker went from seven to over eighty triaged packages in a few days.

Then I looked at changes done by current porters. Which usually meant David Abdurachmanov. I used his changes as a base for the changes needed for Fedora packaging, while trying to minimise the amount of them to the minimum required.

I did over twenty pull requests to Fedora packages during a week of work.

Hardware?

But which hardware did I use to run those hundreds of builds? Was it HiFive Premier P550? Or maybe Milk-V Titan or another RISC-V SBC?

Nope. I used my 80-core, Altra-based, AArch64 desktop to run all those builds. With the QEMU userspace helper.

You see, Mock allows to run builds for foreign architectures - all you need is the proper qemu-user-static-* package and you are ready to go:

$ fedpkg mockbuild -r fedora-43-riscv64

You can extract the "fedora-43-riscv64" Mock config from the mock-riscv64-configs.patch hosted on Fedora RISC-V port forge. I hope that these configuration files may be found in the "mock-core-configs" in Fedora soon.

At some point I had 337 qemu-user-static-riscv processes running at same time. And you know what? It was still faster than a native build on 64-bit RISC-V hardware.

But, to be honest, I only compared a few builds, so it may be better with other builders. Fedora RISC-V Koji uses wide list of SBCs to build on:

• Banana Pi BPI-F3
• Milk-V Jupiter
• Milk-V Megrez
• SiFive HiFive Premier P550
• StarFive VisionFive 2

Also note that using QEMU is not a solution for building a distribution. I used it only to check if package builds, and then scrap the results.

Future

Will I continue working on the RISC-V port of Fedora Linux? Probably yes. And, at some point, I will move to integrating those changes into CentOS Stream 10.

For sure I do not want to invest in RISC-V hardware. Existing models are not worth the money (in my opinion), incoming ones are still old (RVA20/RVA22) and they are slow. Maybe in two, three years there will be something fast enough.

04 Dec 2025 5:47pm GMT

This article explores how to turn Fedora machines into Spotify Connect devices.

What is Spotify Connect?

Spotify Connect is a protocol and means by which one device can remotely control playback on another device over your home network or wifi.

If you have a device that supports Spotify Connect then no longer are you limited to listening to Spotify on your phone or computer - you can instead use your phone or computer to control music playback on your Spotify Connect compatible smart speaker, TV sound bar, car stereo, etc.

You can see what Spotify Connect devices are available on your network by hitting the button in an official Spotify client. It will show a list of devices on which you can play music remotely:

My problem is that I don't have a smart speaker or other Spotify Connect compatible device here in my office capable of driving my big floor standing speakers. What I do have however, is an old stereo amplifier with spare inputs in the same rack as my server equipment:

The server machine in the bottom of that rack happens to have an integrated USB audio adapter so why not connect that to the AUX-in on the amplifier and teach the server how to stream music from Spotify?

Installing Spotifyd

Spotifyd is an open source Spotify client that you can run as a daemon and also supports the Spotify Connect protocol, which makes it show up as a device that can be controlled from the official Spotify client.

An RPM packaged version of Spotifyd can be found in my COPR repo at mbooth/spotifyd. It's straightforward to enable the COPR repo and install it:

# dnf copr enable mbooth/spotifyd
# dnf install spotifyd

Spotifyd uses the Avahi mDNS for service discovery, which allows the official Spotify clients to find it on your network. So we need to make sure the mDNS port is open, as well as the port used by the Spotify Connect protocol. On a default installation of Fedora Server, it may be necessary to open both ports using the firewall-cmd command like this:

# firewall-cmd --permanent --add-service=mdns
# firewall-cmd --permanent --add-service=spotify-connect
# systemctl reload firewalld

Finally, enable and start the Spotifyd service in the normal systemd way:

# systemctl enable spotifyd.service
# systemctl start spotifyd.service

The server will now show up in official Spotify clients as a device named "spotifyd." Choosing it from the list will begin playback on that device:

If you want to run Spotifyd on a Fedora Workstation install, or any setup where you have user sessions with the audio being managed by Wireplumber/Pipewire, then you will need to start it as a user service instead:

$ systemctl --user enable spotifyd.service
$ systemctl --user start spotifyd.service

Configuration

The configuration file for Spotifyd can be found at /etc/spotifyd.conf where the first thing you probably want to do is customise the name that shows in the device list:

device_name = "Mat's Office"

All the configuration options are explained further in the upstream documentation.

Reporting Issues

For issues directly relating to the RPM packaging of Spotifyd or installation from my COPR repo, please file bugs at github.com/mbooth101/spotifyd-rpm/issues.

04 Dec 2025 3:30pm GMT

03 Dec 2025 9:00pm GMT

We are happy to announce that the GNOME Foundation is sponsoring an Outreachy project for the December 2025 Outreachy cohort.

Outreachy provides internships to people subject to systemic bias and impacted by underrepresentation in the tech industry where they are living.

Let's welcome Malika Asman! Malika will be working with Lucas Baudin on improving document signing in Papers, our document viewer.

The new contributor will soon get their blogs added to Planet GNOME making it easy for the GNOME community to get to know them and the projects that they will be working on. We would like to also thank our mentor, Lucas for supporting Outreachy and helping new contributors enter our project.

If you have any questions, feel free to reply to this Discourse topic or message us privately at soc-admins@gnome.org.

03 Dec 2025 11:03am GMT

02 Dec 2025 1:05pm GMT

FreeIPA Web UI Test Week

The FreeIPA WebUI became new interface for freeipa

How to Participate during testday

1. Test the WebUI - Follow the installation instructions on the Test Day wiki page
2. Explore and experiment - Try different features and workflows
3. Share your thoughts here - Post your comments, ideas, and UX findings in this discussion
4. File bugs - If you encounter actual bugs, please file them in the upstream bug tracker

The post Test Day:2025-12-02 FreeIPA-WebUI Test Day appeared first on Fedora Community Blog.

02 Dec 2025 12:00pm GMT