fidzu : Fedora

25 Jun 2026 8:00pm GMT

Ahora te voy a contar una de esas aventuras de SysAdmin que te ponen a sudar frío, pero que al final te dejan con una sonrisa de oreja a oreja.

Acabo de migrar mi servidor físico de CentOS Stream 9 a CentOS Stream 10 usando Leapp. La neta, aunque el proceso es noble, me topé con varias broncas en el camino (desde falta de espacio en boot hasta conflictos de red) y aquí te dejo el mapa completo para que usted, ¡pare de sufrir!

dnf install leapp-upgrade-el9toel10

leapp preupgrade

# Iniciar una sesión de tmux
tmux new -s upgrade

# Correr el upgrade
leapp upgrade

reboot

cat /etc/os-release

systemctl disable --now systemd-networkd systemd-networkd-wait-online systemd-networkd.socket
systemctl reset-failed

24 Jun 2026 12:50pm GMT

Hoy me topé con un dolor de cabeza clásico de los que administramos servidores: la partición /boot de uno de mis servidores físicos (dev1.casa.g02.org) andaba agonizando. Apenas medía 1 GB y ya estaba al 65% de su capacidad. Con el upgrade que andaba haciendo, meter otro kernel iba a hacer que todo valiera madres por falta de espacio.

La primera ocurrencia lógica es: "pues le quito espacio a la raíz (/) y se lo paso a /boot". Pero, ¡oh sorpresa! Mi partición raíz está formateada con XFS y vive dentro de un volumen lógico (LVM). Para los que no sepan, XFS no se puede encoger (shrink). Así que esa idea valió madre de volada.

Investigando las entrañas del sistema, me di cuenta de que cada imagen de initramfs generada por dracut pesaba la grosería de ~235 MB. ¿Por qué tanto desmadre? Resulta que por defecto, el sistema las compila en modo "genérico", empacando todos los drivers habidos y por haber por si decides mudar el disco a otra compu.

Pero como mi servidor es una máquina física bien establecida, ¿para qué quiero drivers de Hyper-V, VMware o NVMe si mi disco es un SATA común y corriente? Ahí es donde entra la magia del modo hostonly en dracut.

24 Jun 2026 11:45am GMT

I have a 5G modem in my Lenovo x13s and t14s. I run Fedora on them, currently Fedora 44. I have had issues in the past when traveling. The 5G modem works fine when in the US but will not connect to any provider when roaming. It has worked after some time in the UK and Australia, but not in other countries. I use Google Fi for phone service, which allows roaming with the same data allowance as in the US.

After some digging during my current trip, when it wasn't connecting, I think I have found the issue and a workaround to ensure I can connect. Google Fi uses two networks, T-Mobile in the US and Three UK when roaming. It also uses T-Mobile for roaming. The issue seemed to be that the towers were rejecting the SIM card, attempting to register using T-Mobile's default APN that seems to be baked into the SIM card as a default profile. The ModemManager logs looked like the following

ModemManager[1603]: <msg> [modem0] 3GPP packet service state changed (unknown -> detached)
ModemManager[1603]: <msg> [modem0] 3GPP packet service state changed (detached -> unknown)
ModemManager[1603]: <msg> [modem0] 3GPP packet service state changed (unknown -> detached)
ModemManager[1603]: <msg> [modem0] 3GPP packet service state changed (detached -> unknown)

The trick that got it to connect was to make a change to the default profile used to connect to the phone tower was to run an mmcli command: "mmcli -m 0 -3gpp-set-initial-eps-bearer-settings="apn=h2g2,ip-type=ipv4v6" Which forces the sim to use the Google Fi APN and not the T-Mobile one

24 Jun 2026 3:45am GMT

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

Week: 15 - 19 June 2026 (Flock Week!!)

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

• Helped getting elnbuildsync moved into stg openshift (ongoing).
• A couple more services had OS upgrades to Fedora 44.
• Some more MirrorManager problems.
• Scrappers found another ostree repo. on kojipkgs, limited dir. indexing to stop the attack and then searched for any other ostree repos. Hopefully the last time it happens.

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 Infrastructure and CentOS Stream.
CentOS ticket tracker
CentOS Stream ticket tracker

• Finish rebuilding/bumping some pkgs for ppc64le libvirt/qemu-kvm stack on el10 (https://gitlab.com/CentOS/infra/tracker/-/work_items/1928)
• Start to work on debuginfo origin servers refresh with el10 instances (https://gitlab.com/CentOS/infra/tracker/-/work_items/1892)
• More coordination work with Stream team about secureboot issues (https://redhat.atlassian.net/browse/CS-3400)
• Finishing last debuginfo pool members reinstall (https://gitlab.com/CentOS/infra/tracker/-/work_items/1892)
• Decommission old openstack env for stream (https://redhat.atlassian.net/browse/CS-3404)
• Cloud SIG doc url change (migration to gitlab, from pagure) - https://gitlab.com/CentOS/infra/tracker/-/work_items/1934
• internal requests (FRCL and audit compliance)
• Move another SIG doc url (away from pagure.io) - https://gitlab.com/CentOS/infra/tracker/-/work_items/1938
• Modified the aws load-balancer settings for one ocp tenant (https://gitlab.com/CentOS/infra/tracker/-/work_items/1932)
• Migrate haproxy load-balancers to el10 for stream dc-move prep (https://redhat.atlassian.net/browse/CS-3353)

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

• Migration at 95%, the only thing left to migrate is majorly fedora-scm-requests, bug fixes, and continued releng operations.
• Migration: archive-repo-manager from pagure
• Fix: Missing permissions on releng/fedora-comps
• Bug Fix: Mass tagging script for verification bits
• F45 Change Sets reviews are in check and f45-python side tags are merged.
• Regular releng operations.

QE

This team is taking care of quality of Fedora. Maintaining CI, organizing test days
and keeping an eye on overall quality of Fedora releases.

• We've started searching for new owners/maintainers of Packager Dashboard and Oraculum

Forgejo

This team is working on introduction of https://forge.fedoraproject.org to Fedora
and migration of repositories from pagure.io.

• Completed the Flock To Fedora 2026 presentation on Fedora → Forgejo migration efforts #588, packaged and deployed Forgejo 15.0.3 #620.
• successfully ran the PR fix doctor across all migrated repositories #601 to address merge issues with Pagure imports.
• Enhanced runner infrastructure with the addition of a Testing Farm runner option #619 and docker-slim type runner #568, and improved security by deploying oauth-proxy to secure the Forge metrics endpoint #571.

EPEL

This team is working on keeping Epel running and helping package things.

• Updated caddy in rawhide, resolving 14 CVEs
• Ongoing onboarding of Pedro

UX

This team is working on improving User experience. Providing artwork, user experience,
usability, and general design services to the Fedora project

• With Flock this week, got to see how all the final designs turned out it in person!
• Emma delivered her talk on 'Why You Should Use Open Source Design in Open Source' at Flock
• Great progress on the F45 wallpaper in the final stretch!

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 25, 2026 appeared first on Fedora Community Blog.

23 Jun 2026 10:12am GMT

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

Week: 08 - 12 June 2026

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

• Request for CentOS Alternative Images SIG URL Update
• Wiki upgrade problems/patch with FedoraMessaging when editing a page
• Staging wiki down due to PluggableAuth extension issue
• Move all remaining Fedora 42 instances to 44
• Deploy DRM Panic Frontend
• Switch from session-based OIDC to Authentication Bearer
• Move the Fedora Badges static assets from Pagure to Forgejo
• badges: fix image trigger annote order on deploy metadata
• List authorization in CORS headers for API routes

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 Infrastructure and CentOS Stream.
CentOS ticket tracker
CentOS Stream ticket tracker

• Fix backup cache DB mismatch on backup machine
• Change isa riscv %dist to .el10rv
• Reinstall failed sponsored server
• rebase needed qemu-kvm/libvirt stack for ppc64le hypervisor role
• Refresh new RHEL releases on deployment server[s]
• Deploy new donated machine (and onboard new sponsor)
• Upgrade various OCP clusters to latest 4.18 minor version
• debug a acme renew issue
• Investigate crashing postgres on cbs-hub
• Degraded RAID array in sponsored machine
• CentOS-Stream-GenericCloud-x86_64-10-latest.x86_64.qcow2.SHA256SUM is a zero byte file
• cbs command aborts on Fedora 44 due to missing CA bundle path
• [reminder] : reach out to new sponsor in South Africa

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

• Change Set Review for F45
• Script improvement and feature addition (in-progress):
  • fix(orphans): handle alternative providers to eliminate false positives
  • Fixes #9841 - adds a release_type field to .composeinfo so we can tell Beta and Final releases apart.
• Regular Releng Operations
• Fedora 42 EOL Preps

AI

This is the summary of the work done regarding AI in Fedora.

• Testdays (the webapp we use for running…Test Days) has an MCP server now (not sure if it's deployed in prod yet though) - work by Jaroslav Groma

QE

This team is taking care of quality of Fedora. Maintaining CI, organizing test days
and keeping an eye on overall quality of Fedora releases.

• Executive summary: Python 3.15 and kmscon Changes landing caused some fallout, tool tech debt payoff / enhancement continues, most team members used Day of Learning for AI experimentation
• Two major Changes landed: Python 3.15 and kmscon consoles, various fallout from that:
  • CoreOS and IoT both broken by the kmscon change
  • Got on-the-fly keyboard layout changes added (important for openQA)
  • Kickstart installs broken by Python 3.15 change (sent a fix)
  • Various openQA test updates required for kmscon fixes
• openQA serial bug worked around, new packages now deployed to prod
• Tech debt repayment and new feature work continue on testdays, issuebot and blockerbugs
• Kparal continues to find bugs in Lenovo laptop support
• Work on ELN kernel gating got blocked by an unfortunate pre-existing design problem
• Worked with Cristian Le to get rpmdeplint pipeline updated so fixes from last ~year are in prod, it now runs in ~2 minutes instead of ~20
• Team did some AI agent / skills experimentation during Day of Learning

Forgejo

This team is working on introduction of https://forge.fedoraproject.org to Fedora
and migration of repositories from pagure.io.

• `testing-farm` optimized runner option provided to `ci` and `atomic-desktops` organizations
• Regular runners capacity increased from 1 to 4 concurrent jobs
• Private Issues work is ongoing.

EPEL

This team is working on keeping Epel running and helping package things.

• Executive summary:
• Completed archiving of EPEL 10.1
• Package maintenance across multiple Fedora and EPEL packages
• Quality work via bug reports and bodhi karma

UX

This team is working on improving User experience. Providing artwork, user experience,
usability, and general design services to the Fedora project

• Final stretch prepping Flock materials - Fedora badge, livestream template, sponsor splash
• Progress being made on the F45 Wallpaper
• Emma gave a talk about the Fedora Design team at the Waterford office's Fedora 44 Release Party last Wednesday

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 24, 2026 appeared first on Fedora Community Blog.

23 Jun 2026 10:07am GMT

A primary focus across many groups was the upcoming Fedora 45 release cycle, which drove the submission and discussion of several key Change Proposals, including system-wide updates to LLVM 23 and a multi-widgetset Lazarus IDE. This release preparation was accompanied by significant package maintenance, highlighted by the major OpenSSL 4.0 update and its mass rebuild, compatibility work for Python 3.15, and security-driven package replacements in EPEL. Another common thread was the evolution of core infrastructure, with teams managing the migration from Pagure.io to Forgejo and the transition from Nagios to Zabbix for system monitoring. Community testing was also a crucial activity, with efforts centered on the new KDE Plasma 6.7 release and the restoration of Google Drive integration in GNOME. Finally, improving community processes was a recurring theme, with discussions on creating a new SIG for systemd-sysexts and enhancing security by mandating 2FA for packagers.

Announcements

This week's announcements focus on the upcoming Fedora 45 release cycle and evolving infrastructure. A reminder was sent out for the upcoming deadlines for F45 Changes, with two new proposals already submitted: a system-wide update to LLVM 23 and a plan to offer the Lazarus IDE with multiple widgetsets. On the infrastructure front, a post discusses the final steps for migrating from Pagure.io to the new Forgejo-based forge, while another provides a technical guide for onboarding Forgejo-hosted projects to Fedora Konflux. The Anaconda team is also seeking community input on a new web-based remote installation feature being built for headless systems.

In community news, a new Outreachy intern shared their experience working on the Fedora Release Schedule Planner API, highlighting a valuable contributor program. For the broader Linux community, a Fedora Magazine article details a practical method for how to sandbox AI coding agents with microVMs on Fedora Linux, addressing a modern security concern for developers.

FESCo

This week, discussions focused on several Change Proposals for the upcoming Fedora 45 release. New proposals were introduced to update the system-wide LLVM toolchain to version 23 and to offer the Lazarus IDE with multiple widgetset options (including GTK3 and various Qt versions), giving developers more choice beyond the current GTK2-only package. These proposals are now open for community feedback.

Discussions continued on previously submitted proposals. Regarding the Golang 1.27 update, it was noted that a fix for DWARF5 debugging issues is unlikely to be included in this release; developers needing this functionality are directed to a dedicated COPR repository. The libxml2 2.15 update, which will require a mass rebuild and deprecates the Python bindings, is awaiting consideration of feedback from the developer mailing list. A significant debate is ongoing around the proposal for a minimal GRUB EFI for Confidential Computing. While the proposal aims to create a smaller, more stable bootloader for Unified Kernel Images (UKIs), the discussion questions the rationale for not using systemd-boot, with conflicting information about the systemd maintainers' willingness to add necessary features.

Learn more about the FESCo team.

Workstation / GNOME

The main activity for the Workstation / GNOME group this week centered on the ongoing effort to restore Google Drive integration in GNOME. In the forum discussion "[Call for Testers] Restoring Google Drive integration in GNOME", a user inquired about installing the test packages on Fedora Silverblue. In response, instructions were provided on how to use rpm-ostree to replace the necessary system components from the testing COPR repository. This provides an opportunity for Silverblue users to contribute to testing this important feature.

Learn more about the Workstation / GNOME team.

KDE

This week's focus was the release and testing of KDE Plasma 6.7.0. The new version was made available for testing on Fedora 43 and Fedora 44, and the community was encouraged to help test and report bugs. In preparation for the final release, the COPR repository for the Plasma 6.7 beta was retired.

Discussions following the release highlighted several user-reported issues. Users on Kinoite noted that the network manager repeatedly asked for Wi-Fi passwords after rebooting; a workaround was discovered which involves entering the password in the main system settings instead of the connection pop-up. Other reported issues include a login loop for some users and desktop instability after clearing the Mesa shader cache. A dependency issue affecting kdevelop on Fedora 43 was also brought up, with the team noting it is a known problem related to a gpgme issue and is expected to be fixed after the Plasma update is pushed to stable.

Learn more about the KDE team.

Infrastructure

This week's activity was light as team members recovered from the Flock 2026 conference. The primary focus was on the monitoring system transition discussed in the main Infrastructure meeting. Nagios has now been officially decommissioned, and work is underway to remove its remaining components from all hosts. The team reviewed the current alerts in the new Zabbix monitoring system, identifying several noisy checks related to mail queues, file ages, and backups that will be tuned or investigated. The Daily Standup was a brief check-in, mostly acknowledging the post-conference recovery period.

Decisions

During the Infrastructure meeting, several actions were agreed upon to refine the new Zabbix monitoring setup:

• The alert threshold for the mail queue on smtp-mm will be increased to reduce noise caused by spam bounces.
• An alert for an out-of-date MySQL backup will be investigated.
• The threshold for countme file age checks will be raised to prevent intermittent alerts.
• The cause of unusually large log files on the dl03 mirror will be investigated.

Learn more about the Infrastructure team.

Release Engineering

This week, the Release Engineering group's activity centered on a community forum discussion. A user shared their detailed experience of successfully creating a customized Fedora 44 XFCE live ISO using the kiwi-ng tool. They described a multi-hour process of trial and error, highlighting solutions for common issues like user login configuration and providing practical advice, such as avoiding the /tmp directory for build outputs to prevent space-related failures. The user also sought help from the community on how to properly format and share their working config.xml file, presenting an opportunity for others to engage and assist.

Learn more about the Release Engineering team.

Quality

This week, the Quality team discussed several technical issues affecting development releases. A significant disruption occurred when a failing test, upgrade_server_domain_controller, blocked all Rawhide updates over the weekend. Other reported problems include broken Adwaita themes in XFCE on Rawhide due to the removal of gnome-themes-extra, a libvirtd service failure on Fedora 44 related to a ZFS module, and a temporary dependency issue preventing Thunderbird installation which was already being tracked. The team also welcomed a new contributor and announced the next QA meeting for June 22.

There are several opportunities for community involvement. Testers are needed for a new Synaptic-style GTK4 frontend for DNF5, which has received positive initial feedback. Additionally, the effort to restore Google Drive integration in GNOME continues, with instructions now available for testing on Fedora Silverblue. As always, volunteers are welcome to help with the validation of Fedora 45 Rawhide nightly composes.

Learn more about the Quality team.

Docs

This week, discussion continued on the long-running topic of a design proposal for Fedora's documentation. The conversation focused on the proposal's use of a tag-based system for organizing user documentation. Contributors expressed concerns about the reliability and consistency of manual tagging, suggesting it can indicate poor search functionality and structure. A preference was noted for traditional navigation methods like Tables of Contents for better topic discovery. As a modern alternative to manual tagging, it was suggested that Large Language Models (LLMs) could be employed for automated classification, which might prove more effective and less costly over a large set of documents.

Learn more about the Docs team.

Internationalization

This week, the Internationalization team announced a significant new collaboration: the MATE Desktop project has migrated its translation work to the Fedora Weblate platform. This move invites all translators to contribute to MATE applications and documentation directly within the Fedora infrastructure, strengthening the ties between the communities.

In other news, the community welcomed a new and proactive Norwegian translator, Arvind Frøiland, who introduced himself on the mailing list. Having already completed the Norwegian Bokmål translation for systemd, Arvind expressed a keen interest in contributing to other core components and requested reviewer permissions to help maintain and improve Norwegian translations more effectively.

Learn more about the Internationalization team.

EPEL

This week in EPEL was quiet, with a sparsely attended meeting due to the Flock conference. The main focus was on several significant package changes proposed on the mailing list. A key discussion is underway to replace the end-of-life p7zip package with the modern 7zip in EPEL 8 and 9 due to numerous unfixable security vulnerabilities in the older package. This is considered a slightly incompatible update, and an issue has been filed for community feedback and future discussion.

Other proposals seeking community input include the retirement of qt6-qtwebengine from EPEL 9 due to maintenance difficulties and a high number of CVEs, and a plan to update syncthing to v2 in EPEL 10 while retiring it from EPEL 8 and 9 because older dependencies prevent necessary security updates. Contributors, especially maintainers of packages that depend on these, are encouraged to participate in the discussions.

Learn more about the EPEL team.

Atomic

This week, discussion centered on a proposal to create a new Special Interest Group (SIG) focused on systemd system extensions (sysexts). The proposal, initiated by Jean-Baptiste Trystram, follows discussions at FLOCK 2026 and aims to formalize the building, documentation, and distribution of sysexts based on Fedora content. These extensions are seen as a key method for adding functionality to atomic systems, especially for software not well-suited for containers or Flatpaks. The primary goals for the proposed SIG would be to establish an official build process, potentially using Konflux, and to solve the open questions of distribution and discoverability. The idea has received positive engagement, with several contributors expressing interest in joining the effort.

Learn more about the Atomic team.

CoreOS

During the weekly meeting, the team reviewed upcoming system-wide changes for Fedora 45. A critical issue was discovered with the proposal to relocate RPM repository configurations to /usr. Because rpm-ostree relies on DNF4, this change is expected to break client-side package layering, a significant feature for users. This will be tracked closely. The team is also seeking a volunteer to investigate a bug related to another F45 change in fedora-coreos-tracker/issues/2160.

In the forums, a proposal was made to create a new Special Interest Group (SIG) for systemd-sysexts. The goal is to establish an official process for building and distributing system extensions, which offer a way to add functionality to atomic systems for software that isn't well-suited for containers. The proposal has received positive feedback and interest from several community members, presenting a new opportunity for contribution.

Learn more about the CoreOS team.

AI & ML

The AI & ML SIG met this week to discuss preparations for the upcoming Fedora 45 release, which is scheduled to branch on August 11, 2026. A key topic was the ongoing effort to update packages for the Python 3.15 release, which is causing the usual compatibility issues with torch and triton. The group plans for F45 to ship with ROCm 7.2, and work is underway on a compatibility package set to support this version on F46 when the next major ROCm release arrives. There is a strong interest in packaging local AI tools for F45, and contributors are needed to help review packages for the pi-coding-agent (Bugzilla #2464801) and the olla local AI proxy.

The idea of creating a dnf package group for AI/ML tools was briefly discussed but was ultimately deferred. The group felt it was too early to add this, given the complexity of handling different hardware backends (like ROCm) and the desire to avoid adding process overhead for the small number of active packagers. The meeting also touched on the status of OpenVINO, confirming that no one in the SIG is actively working on it at the moment.

Learn more about the AI & ML team.

Security

The Security SIG held its weekly meeting to discuss recent events and plan future work. Following the Flock conference, the group noted a new connection with Red Hat Product Security (RH ProdSec) and discussed concerns about documentation with security implications, which will be addressed soon. A major topic was the FESCo proposal to mandate two-factor authentication (2FA) for provenpackagers, prompted by recent security incidents in the wider open-source community. The SIG offered to support this initiative by helping with documentation and communications.

The team also triaged several issues, focusing on providing better support for package maintainers dealing with CVEs. This led to a decision to create a formal process for maintainers to request assistance. The group also briefly touched on tickets related to security-optimized sysctl settings and a protocol for skipping meetings. Contributors are encouraged to review and comment on the open tickets in the Security Forge and the Security Docs Forge.

Decisions

• The SIG approved the proposal in ticket #9 to create a formal support channel for package maintainers needing help with CVEs. The plan is to add a ticket template to the security/tickets repository and announce the new process on the devel mailing list.

Learn more about the Security team.

Perl

This week's activity for the Perl group focused on routine package maintenance and an enhancement to packaging tools. The perl-PPIx-Regexp package was updated to version 0.092 via several pull requests. The perl-Net-DNS package was also updated to version 1.55, which included an update to the upstream GPG signing key. A notable improvement was merged for perl-rpm-build-perl, which now supports the package NAME VERSION; syntax to improve automated dependency generation.

PHP

A discussion was initiated by Remi Collet regarding a build issue for PHP extensions on EPEL-10.2. It was noted that extensions were incorrectly being built against the newer PHP 8.4 stack instead of the default PHP 8.3. This occurred because the build system selected php8.4-devel as the best provider for the php-devel dependency. A workaround has been implemented to ensure packages are built against the correct version.

Decisions

• To resolve a build dependency conflict on EPEL-10.2, the BuildRequires for PHP extensions will be constrained to a specific version range (php-devel >= 8.3 with php-devel < 8.4). This ensures they build against the intended default PHP 8.3 stack. All affected extensions have already been rebuilt with this fix.

Learn more about the PHP team.

Other Discussions

• A discussion was initiated by FranciscoD about improving the packaging workflow by creating a separate git repository for up-to-date .spec file templates. This would allow rpmdev-newspec to use current templates and could be integrated into a new fedpkg new command. Following the discussion, a spec-templates repository was created, and a pull request for a fedpkg new-package command was opened to implement this functionality.
• Adam Williamson posted a heads-up that all Rawhide updates were being blocked by a failure in the upgrade_server_domain_controller test. He noted the bad timing post-Flock and devconf.cz and mentioned he was actively investigating to resolve the issue as soon as possible.
• Brad Smith announced upcoming changes for the containerd package. A FESCo exception now allows all Fedora releases to have the same containerd version, constrained only by the Go version. Additionally, starting with v2.3.x, the containerd-shim-runc-v2 will be provided as a static binary, matching upstream, which should be a transparent change for users.
• A change proposal for Fedora 45 was announced to update all LLVM sub-projects to version 23. This update will involve a soname version change for LLVM libraries and the addition of an llvm22 compatibility package. The plan is to push version 23.1.0 into F45 during the Beta Freeze, with release candidates being tested in COPR beforehand.
• A change proposal for Fedora 45 was announced to offer the Lazarus IDE built with multiple widgetsets (GTK2, GTK3, Qt5, Qt6) instead of just GTK2. The lazarus-ide package will be renamed to lazarus-ide-base, and new sub-packages for each widgetset will be introduced. This will allow users to choose their preferred interface and will facilitate the eventual retirement of gtk2.
• Aoife Moloney sent a reminder about the upcoming deadlines for Fedora 45 changes. The deadline for submitting System-Wide changes is June 30, 2026, and for Self-Contained changes is July 21, 2026. All changes must be in a testable state by August 11 and complete by August 25.
• Gordon Messmer initiated a discussion on both the nodejs and devel lists about the presence of pre-built binaries in the node_modules directories of bundled Node.JS packages in Fedora. The consensus was that this is an oversight and not permitted by packaging guidelines. The conversation highlighted the fundamental difficulty of adhering to Fedora's policies with the NPM ecosystem, where dependencies often include pre-compiled or minified assets, making review and maintenance impractical. It was suggested that bugs should be filed for affected packages and a FESCo ticket opened to address the systemic issue.
• Emanuele Petriglia inquired about the fx package, which was orphaned years ago due to issues with NodeJS packaging guidelines. Ben Beasley, the former maintainer, confirmed this was the reason and noted that since the tool has been rewritten in Go, the original packaging problems are no longer relevant, and it would be welcome back in Fedora.
• Kamil Paral called for new maintainers for the Packager Dashboard and Oraculum.
• C. S. Sushi proposed the creation of a Software Engineering SIG.
• Other topics discussed this week include a request for help with a List.remove() issue inside a for-loop in Java, comments on a spam email promoting a code editor that was also sent to openSUSE lists, and the continuation of a long discussion on AI-driven contributions which pivoted to requiring 2FA for packagers. Technical discussions covered packaging guidelines for distribution conditionals, how to handle autogenerated documentation in RPMs, and the implications of swapping fedora-release on COPR compatibility for Remixes. Announcements were made regarding the sunset of pagure.io, a change proposal for libxml2 2.15, and another for a minimal GRUB EFI for Confidential Computing. Users sought help with a mockbuild failure in rawhide and a Bodhi update issue. Finally, there was a check on a non-responsive maintainer and a question about the OpenSSL 4.0 mass rebuild.

New contributor introductions

• Benson Muite introduced himself to the 3dprinting SIG, expressing interest in using FOSS for making things and mentioning his work on reviewing FreeCAD to bring it back to Fedora.
• Kenny Glowner introduced himself, seeking sponsorship to become a Fedora packager. He aims to adopt and maintain the orphaned ccze and sslh packages, with a long-term goal of rewriting them in Rust.

Package Updates

• Ankur Sinha announced that highfive 3.3.0 is being prepared for Rawhide and listed the dependent packages that will be rebuilt.
• The upgrade to openbabel 3.2.0 was announced for Rawhide, which will require several dependent packages like IQmol and avogadro2 to be rebuilt or updated.
• Gwyn Ciesla announced an upcoming libupnp 2.0.2 build which includes a soname bump, and that all dependencies except the already-FTBFS eiskaltdcpp will be rebuilt.
• František Zatloukal announced upcoming upgrades to fmt 12.1.0 and spdlog 1.17.0 in Rawhide, which will involve a soname bump and a mass rebuild of dependent packages in a side tag.
• Gwyn Ciesla announced an update to QXlsx 1.5.1, which includes a soname bump. The dependent package LabPlot builds fine, while stellarium is already failing for other reasons.
• Ben Beasley gave a heads-up about the upcoming update of abseil-cpp to version 20260526.0 in F45/Rawhide, which breaks ABI compatibility and will require a rebuild of all dependent packages in a side tag.
• Mattia Verga announced an upgrade of libbox2d from version 2.x to 3.x in Rawhide, which includes a soname bump. The main consumer, libreoffice, will be upgraded at the same time.
• Mamoru TASAKA announced an update for libetpan to 1.10.1, which involves a soname bump. The dependent packages cairo-dock-plug-ins and claws-mail will be rebuilt, but this will be postponed until after the OpenSSL 4.0 changes are merged.
• Fabio Valentini announced that the libgit2 package has been retired in Rawhide as part of the Changes/Versioned_libgit2_packages implementation, and requested reviews for pending pull requests on packages that still need to be updated.
• Milan Crha announced an upcoming evolution-data-server 3.61.1 release which includes a soname bump for libcamel. He plans to rebuild all affected packages in a side tag.
• The OpenSSL 4.0.1 update has officially landed in Rawhide, along with 734 rebuilt packages. An openssl3 compatibility package is available for packages that have not yet been updated. Maintainers are urged to make their packages compatible before the F45 mass rebuild.
• José Expósito announced plans to update mesa to v26.1.x in Fedora 44, coordinating with RPM Fusion maintainers. A discussion also started about the possibility of updating Mesa in Fedora 43 as well.

Orphaning packages

• The weekly report of orphaned packages was sent out, listing numerous packages that are available for adoption and will be retired in six weeks if no new maintainer is found.
• Fabio Valentini announced the intent to retire the rust-handlebars5 compat package in Rawhide, as the CLI tool it provides (handlebars-cli) is no longer part of the main handlebars crate in version 6.

22 Jun 2026 6:27am GMT

22 Jun 2026 12:00am GMT

21 Jun 2026 3:43pm GMT

20 Jun 2026 11:11pm GMT

20 Jun 2026 7:17pm GMT

Another wonderfull flock is in the books. This post is likely to be kind of long, and was written a few days after I got back home, so it's likely I forgot some things or misremembered them somehow. If so, it's not intentional.

TLDR version: Another great flock. Lots of good conversations, lots of good talks, good food, good friends. I'd like to give kudos to all the people who put things on. It's not easy planning a large event like this and at least from my perspective everything went very smoothly.

20 Jun 2026 5:22pm GMT

RH/entrevistador: "Qual sua pretensão salarial?"
Candidato/entrevistado: "Qual é o seu orçamento/valor aprovado/budget para a vaga?"

É assim que a entrevista deve transcorrer, a partir do número da empresa. Se há uma vaga, há um orçamento aprovado para ela.

Se o candidato fala sua pretensão às cegas, sempre sai perdendo. Se a pretensão for baixa, é só isso que vai receber. Se for muito alta, será eliminado, muitas vezes sem nem saber o motivo.

É o candidato que deve optar por continuar ou não o processo após ouvir o valor aprovado da empresa para a vaga.

O candidato controlar o valor do salário na entrevista pode lhe garantir uns bons 20% a mais de valor inicial. Se o entrevistador controlar, será os mesmos 20%, só que para menos.

É claro que nem todo candidato:

• tem condições de abrir mão de qualquer vaga que apareça, e isso é reflexo muito ruim do mercado de trabalho
• tem estômago para negociar deste jeito, e isso é coisa que as pessoas devem tentar treinar para evitar a possível manipulação por trás da pergunta "qual sua pretensão"

Um "caçador de cabeças" (head hunter) entra na primeira entrevista de um candidato com exatos 2 objetivos: 1️⃣ checar se há bom casamento financeiro entre o candidato e o valor aprovado para a vaga e 2️⃣ captar se o candidato, de uma forma geral e difusa, tem a ver com a empresa e a função da vaga. Este último pode ser previamente sondado pelo perfil publicado da pessoa e será aprofundado mais adiante no processo. Então comprovar compatibilidade financeira é o objetivo mais importante da primeira entrevista. E, por incrível que pareça, isso pode ser resolvido nos primeiros 6 minutos de entrevista, ou no chat antes de qualquer encontro.

Pense: por que o candidato tem que ter um número e revelar, mas o recrutador não? Se há uma vaga, há um orçamento aprovado para ela. E é o candidato que deve decidir se aquilo atende suas expectativas. Não o contrário.

Reescrito a partir de comentários que deixei numa publicação do Márcio Gonçalves no LinkedIn.

20 Jun 2026 11:25am GMT

19 Jun 2026 4:00am 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.8RC1 are available

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

RPMs of PHP version 8.4.23RC1 are available

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

ℹ️ The packages are available for x86_64 and aarch64.

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

ℹ️ Installation: follow the wizard instructions.

ℹ️ Announcements:

• PHP 8.5.8RC1 available for testing
• PHP 8.4.23RC1 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

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\*

ℹ️ Notice:

• version 8.5.8RC1 is in Fedora rawhide for QA
• EL-10 packages are built using RHEL-10.2 and EPEL-10.2
• EL-9 packages are built using RHEL-9.8 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.26 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.4.19 and 8.5.4 are planed for March 12th, in 2 weeks.

Software Collections (php84, php85)

Base packages (php)

19 Jun 2026 3:59am GMT

18 Jun 2026 10:00pm GMT