devel December 2024

devel@lists.fedoraproject.org

145 participants
195 discussions

updates for "Change: Replace Redis with Valkey"
by Zbigniew Jędrzejewski-Szmek 03 May '25

03 May '25

Hi, For https://fedoraproject.org/wiki/Changes/Replace_Redis_With_Valkey in FESCo ticket https://pagure.io/fesco/issue/3203 we didn't make a decision and decided to wait for the situation to clarify. Has the status changed? Can we now say that Valkey is going to be the default replacement that most people will want to switch to? (If there's a clear answer, we'll want to finalize the rubberstamping of the Change Proposal. If not, we can let it sit some more.) Zbyszek

4 4

Orphaning some CLI tools (written in Rust)
by Fabio Valentini 16 Apr '25

16 Apr '25

Hi all, Doing some end-of-year "does this still spark joy?" type of chores, I decided to orphan a few packages for command-line tools (written in Rust) that I picked up at some point but which I myself don't use: - rust-git-delta - rust-gitui + rust-asyncgit - rust-sd - rust-silver Some notes for potential maintainers: Some of these don't see regular updates - sd and silver are years old at this point. rust-git-delta, rust-gitui, and rust-silver all depend on the Rust bindings for libgit2. This is a constant pain point, because they need to be patched for new libgit2 bindings versions to address security issues in the bundled libgit2. (Yes, *not* using the bundled libgit2 was considered, and was considered *worse*. The Rust bindings only ever support *one* specific minor version of libgit2, and silently / subtly break with other versions due to ABI incompatibilities.) A number of similar packages I don't use were already redistributed internally in the Rust SIG: - rust-bat - rust-fd-find - rust-lsd - rust-tokei Three of these (bat, lsd, tokei) *also* depend on the libgit2 Rust bindings, and share the maintenance annoyances of the other packages. :) Happy Holidays. Fabio

4 5

Epson inkjet printer drivers orphaned
by Susi Lehtola 11 Apr '25

11 Apr '25

Hi, I have orphaned epson-inkjet-printer-escpr and epson-inkjet-printer-escpr2 due to lack of time and as I have not had an Epson inkjet printer for over two years. Susi -- Susi Lehtola Fedora Project Contributor jussilehtola(a)fedoraproject.org

8 12

Automatic detection of unused BuildRequires
by Marián Konček 01 Apr '25

01 Apr '25

As many of you know, as packages change, so do their BuildRequires. In the current state, maintaining them requires some manual work from the maintainer. 1. So I got around the idea of a simple tool that checks file accesses during the build and using RPM queries, detects whether some package's files are not accessed at all therefore the package is not needed for the build. To my knowledge there is no such project. The project is here: https://github.com/mkoncek/unbreq It may not be completely reliable, but it also may be good enough to catch simple mistakes. 2. At least in the case of maven build system, this tool does not help with `mvn(foo:bar)` dependencies, as maven unconditionally reads all the files present in /usr/share/maven-metadata, from which it deduces the associations between jars and artifact coordinates. I imagine other build systems employ a similar strategy. 3. In the case of maven, we have a manual tool: xmvn-builddep, which reads the build.log and constructs the actual BuildRequires from it, using knowledge about the build procedure. This could be used as an additional step of this tool, having similar tools for other languages. Ultimately, I am interested in the possibility of having automated unused BuildRequires detection as part of rpmbuild / mockbuild. -- Marián Konček

6 8

F42 Change Proposal: RPM Support For Systemd Sysusers.d (system-wide)
by Aoife Moloney via devel-announce 13 Mar '25

13 Mar '25

Wiki - https://fedoraproject.org/wiki/Changes/RPMSuportForSystemdSysusers Discussion thread - https://discussion.fedoraproject.org/t/f42-change-proposal-rpm-support-for-… This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == RPM supports creating users and groups according to configuration provided in sysusers.d snippets shipped in package payload. The goal of the proposal is to fully integrate this RPM functionality in Fedora. == Owner == * Name: Michal Sekletar, Zbigniew Jędrzejewski-Szmek, Panu Matilainen * Email: msekleta(a)redhat.com, zbyszek(a)in.waw.pl, pmatilai(a)redhat.com == Detailed Description == This proposal consists of two parts. The first is to make sure that rpm functionality is fully enabled in Fedora. The second is to update packaging guidelines and raise awareness about the new simpler user creation method for rpm packages. The goal is a fully declarative system user and group management in all RPMs. Over time we should be able to drop all manual `useradd`/`groupadd` invocations or use of `%sysusers_create_compat` macro in rpm scriptlets. Support for sysusers was added in rpm 4.19.0. Support for group membership (`m` lines) was added in rpm 4.20.0. Support for locked-down users (`u!` lines) was added for rpm 4.21.0. The rpm package has patches to disable user/group creation ([https://src.fedoraproject.org/rpms/rpm/blob/rawhide/f/rpm-4.18.92-disable-s… rpm-4.18.92-disable-sysusers.patch]) and make user/group dependencies weak ([https://src.fedoraproject.org/rpms/rpm/blob/rawhide/f/rpm-4.19.91-weak-user… rpm-4.19.91-weak-user-group.patch]). == Feedback == [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… Discussion] about idea to submit the proposal on fedora-devel list. == Benefit to Fedora == * Declarative system user and group management by packages * Potential for spec file simplification, concretely, removal of relevant part of %pre scripts in some packages. * Ability to query what user and groups are provided by given package as well as ability to have dependencies on users/groups from different packages. * Make use of native rpm functionality in favor of current %sysusers_compat_create. == Scope == * Proposal owners: ** Change rpm so that it generates hard dependency between packages A and B in case B depends on user or group provided by package A. Rpm currently has downstream patch so that only weak dependencies are generated. ** Make sure that previous change in rpm doesn't cause package dependency loops during system installation. ** Work on fix for shadow-utils so that useradd and groupadd work correctly in chroot on SELinux enabled systems (shadow-utils [https://github.com/shadow-maint/shadow/issues/940| issue].) * Other developers: ** We would welcome any help with shadow-utils [https://github.com/shadow-maint/shadow/issues/940| issue]. * Release engineering: N/A (not needed for this Change) * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with the Fedora Strategy: == Upgrade/compatibility impact == There is no upgrade/compatibility impact. == How To Test == * Select rpm package that creates system user/group account in %pre * Remove part of %pre scriptlet that handles user/group creation * Create equivalent [https://www.freedesktop.org/software/systemd/man/latest/sysusers.d.html| sysusers.d] configuration file and ship it as part of rpm payload under /usr/lib/sysusers.d/. * Rebuild the package * Verify that package has been built correctly and it has rpm provides for installed user account and group (e.g. `user(foo) = ABUNCHOFHEXHERE`, `group(bar) = ADIFFERNTBUNCHOFHEXHERE`). Use `rpm -qP $package | awk '/(user|group)\(/ {print $3}' | base64 -d` and check that the output looks reasonable. * Verify that you can install the package and installed files have correct ownership. == User Experience == There shouldn't be any user observable change to previous state. Potential packaging related benefits are mostly of interest to package maintainers. == Dependencies == None == Contingency Plan == * Contingency mechanism: If we are not confident by mass-rebuild that we can deliver the feature we will postpone its delivery to later Fedora release. There are no explicit rollback/cleanup actions that need to taken. * Contingency deadline: Mass Rebuild of RPMs on Wed 2025-01-15. * Blocks release? No == Documentation == [https://github.com/rpm-software-management/rpm/blob/master/docs/manual/user… sysusers.d support in RPM]. == Release Notes == N/A -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

8 20

F41 Change Proposal: Anaconda as native Wayland application (System Wide)
by Aoife Moloney 12 Mar '25

12 Mar '25

Wiki - https://fedoraproject.org/wiki/Changes/Anaconda_As_Native_Wayland_Applicati… Discussion Thread - https://discussion.fedoraproject.org/t/f41-change-proposal-anaconda-as-nati… This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == Currently, Anaconda is still an X11 application, which we would like to fix and make Anaconda Wayland native application to allow us drop of the X11 dependencies from installation ISO images. However, this change is not just a simple switch and we need to do some adjustments during the path which will impact user experience. == Owner == * Name: Anaconda team ([[User:jkonecny| Jiří Konečný]]) * Email: jkonecny(a)redhat.com == Detailed Description == Anaconda is required to migrate to Wayland native application to drop dependencies from the installation ISO images which are deprecated. Package owners want to drop libXklavier from Fedora (see https://bugzilla.redhat.com/show_bug.cgi?id=1955025 ) but also Xorg server from CentOS Stream and RHEL. However, this change won’t be just simple switching from X11 to Wayland, we also need to change a few things in Anaconda to be able to remove the X11 dependencies. This will have two main visible impacts listed below. === VNC switch to RDP for remote GUI installations === Anaconda has to remove ‘TigerVNC' which is used for VNC connection to be able to install your machine remotely with graphical UI. Reason is that TigerVNC is built from the Xorg server sources, so we would still depend on the Xorg server with this project. As replacement, we follow the recommendation of the Fedora Workstation to switch to Gnome Remote Desktop (grd) with a better protocol Remote Desktop Protocol (RDP) which gives users better performance and security. This will have an impact on current vnc kickstart commands and kernel boot options of Anaconda. This will impact only the Anaconda installation environment (boot.iso). === Consistent keyboard control === Currently, Anaconda experiences difficulties in handling keyboard layouts in the installation environment, particularly on Wayland. Formerly, libXklavier was utilized by Anaconda to manage keyboard layout configuration, however, it proved unstable on Wayland. As a result, Anaconda has disabled keyboard handling during Wayland Live media installations due to unexpected behavior (refer to https://bugzilla.redhat.com/show_bug.cgi?id=2016613 ). This approach may lead to situations when users encountering issues while unlocking LUKS devices or using user passwords in the installed system because installation was done with a different keyboard layout. To exacerbate the situation, there is no universally applicable solution for keyboard handling on Wayland systems, as Wayland lacks a unified API for keyboard management. It means that each Fedora Desktop Environment developed their own API. Unfortunately, the Anaconda team is not able to maintain a custom solution for each Fedora spin. Some Desktop environments started to use '''systemd-localed''' DBus API to address this issue and similar issues. The systemd-localed API seems to be the best approach currently, so we want to promote it as a shared solution for all Fedora spins. The plan is: * All Fedora spins and Anaconda listen on '''org.freedesktop.locale1''' and reflect configuration on the currently running system (might be only for Live media if desired) * All Fedora spins and Anaconda reflect their configuration to org.freedesktop.locale1 * In case Fedora spin will not support '''org.freedesktop.locale1''', the keyboard configuration of Anaconda won’t be reflected in the current system and the situation will be similar to the current Live Wayland experience All the spin owners were notified about this request: * https://pagure.io/fedora-workstation/issue/430 * https://pagure.io/fedora-kde/SIG/issue/504 * https://gitlab.com/fedora/sigs/sway/SIG/-/issues/36 * https://bugzilla.redhat.com/show_bug.cgi?id=2278655 * https://bugzilla.redhat.com/show_bug.cgi?id=2278658 * https://bugzilla.redhat.com/show_bug.cgi?id=2278656 * https://bugzilla.redhat.com/show_bug.cgi?id=2278864 * https://bugzilla.redhat.com/show_bug.cgi?id=2278866 * https://bugzilla.redhat.com/show_bug.cgi?id=2278869 * https://bugzilla.redhat.com/show_bug.cgi?id=2278874 * https://pagure.io/fedora-cosmic/SIG/issue/1 * https://pagure.io/fedora-budgie/project/issue/4 * https://pagure.io/fedora-lxqt/SIG/issue/4 * https://pagure.io/i3-sig/Fedora-i3-Spin/issue/70 == Feedback == We have some feedback from the SIG owners for the keyboard handling (see the links above). We don’t have feedback for the VNC to RDP switch yet. == Benefit to Fedora == * This change will enable removal of X11 dependencies from the Anaconda which may result in reduction of installed software to the system when installing from Live ISO where ISO content is copied to the installed system (depends on the spin dependencies). * Switching from VNC to RDP allow users to use remote graphical installations which are more secure and have better performance . == Scope == * Proposal owners: The Anaconda team will implement changes required in the Anaconda project. More specifically: ** Switch Anaconda code to start Wayland environment on boot.iso instead of X11 ** Change keyboard switching logic to use systemd-localed DBus instead of libXklavier ** Switch remote graphical installations from VNC (TigerVNC) to RDP (GRD) * Other developers: Fedora SIG owners needs to add support for their environment to listen and use systemd-localed DBus API to reflect current state of the DE/WM or they won’t have support of keyboard layout switching in Anaconda. * Release engineering: [https://pagure.io/releng/issue/12138 #12138] * Policies and guidelines: Yes should be done after the implementation (https://docs.fedoraproject.org/en-US/fedora-server/installation/interactive… should switch to RDP) * Trademark approval: N/A (not needed for this Change) * Alignment with the Fedora Strategy: == Upgrade/compatibility impact == This will impact only Fedora installations so no compatibility or upgrade issues. == Early Testing (Optional) == We will reach Fedora QE to coordinate testing approach. == How To Test == # Download any installation media # Run the installation # Look for breakages during the installation Testing should be especially focused on: * Changing resolution with ''inst.resolution'' kernel boot option * Test new RDP solution (API will be clarified) ** Password can be set to the RDP ** Username can be set to the RDP * Test keyboard layout switching works correctly ** On Live media, Anaconda should react on keyboard layout change in the DE and set that to the installed system ** On Live media, Anaconda should be able to set the keyboard layout changes to the live environment ** In the network installation (boot.iso) Anaconda should correctly reflect keyboard layouts changes so text in the Anaconda is written by the correct layout ** Check if specific keyboard layouts are configured and installed as expected == User Experience == The only visible change to a user should be: * Remote graphical installations will use RDP instead of VNC. * Anaconda will be able to control keyboard layouts in the Wayland environment on Live ISOs. This will improve user experience when installing Fedora Workstation, Fedora KDE, Fedora Sway and other Wayland based environments. == Dependencies == No dependencies of this package related to this change. == Contingency Plan == * Contingency mechanism: Postpone this change to the next Fedora release. Revert landed changes in Anaconda if required. * Contingency deadline: 100% code completion deadline * Blocks release? No == Documentation == No documentation yet. However, there are a few PRs ready for merge for CentOS Stream 10: * https://github.com/rhinstaller/anaconda/pull/5463 * https://github.com/rhinstaller/anaconda/pull/5470 * https://github.com/rhinstaller/anaconda/pull/5485 * https://github.com/rhinstaller/anaconda/pull/5498 == Release Notes == TBD -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

21 57

Orphaning java-diff-utils
by Christiano Anderson 20 Feb '25

20 Feb '25

Hi, I have orphaned the java-diff-utils package, which fails to build due to broken and unmaintained dependency jgit. Thanks Christiano

2 2

libnfs soname bump
by Xavier Bachelot 18 Feb '25

18 Feb '25

Hi, libnfs 6.0.0 bumps its soname from 14 to 16. Affected packages are: gvfs qemu vlc xine-lib kodi (RPM Fusion) mpd (RPM Fusion) Affected packagers are all CC'ed. I have requested a side tag and built libnfs there. One can use it with: fedpkg build --target=f42-build-side-102002 I'll try and take care of vlc and xine-lib asap. Regards, Xavier

3 8

Heads-up: rapidyaml 0.7.2 and c4core 0.2.2 coming to F42/Rawhide and F41/Branched
by Ben Beasley 15 Feb '25

15 Feb '25

In one week (2024-09-05), or slightly later, I plan to update the rapidyaml package to 0.7.2[1] in F42/Rawhide and F41/Branched; I will also update its support library c4core to 0.2.2[2]. Both are ABI-breaking updates with SONAME version bumps. I will also update the unversioned support library c4fs to its latest snapshot[3] and rebuild c4log. An impact check in COPR did not reveal any problems[4]. I will use side tags for these updates, using provenpackager privilege to rebuild the sole dependent package, jsonnet. I’m also planning to use these versions for the initial EPEL10 releases[5] of these packages. [1] https://src.fedoraproject.org/rpms/rapidyaml/pull-request/3 [2] https://src.fedoraproject.org/rpms/c4core/pull-request/10 [3] https://src.fedoraproject.org/rpms/c4fs/pull-request/4 [4] https://copr.fedorainfracloud.org/coprs/music/rapidyaml/packages/ [5] https://bugzilla.redhat.com/show_bug.cgi?id=2307084

1 1

Heads-up: updating flatbuffers to 24.12.24 in Rawhide
by Ben Beasley 11 Feb '25

11 Feb '25

In one week, 2025-01-02, or slightly later, I plan to merge and build https://src.fedoraproject.org/rpms/flatbuffers/pull-request/12 to update flatbuffers to 24.12.24 in Rawhide. As always, this is an ABI-incompatible update that bumps the SONAME version. I impact-checked the dependent packages, hyperhdr, onnxruntime, qdigidoc in COPR, https://copr.fedorainfracloud.org/coprs/music/flatbuffers/packages/ and did not observe any problems. Unless I’m asked to do otherwise, I will use provenpackager privilege to rebuild all three dependent packages in the same side tag.

1 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel December 2024