devel-announce December 2024

devel-announce@lists.fedoraproject.org

5 participants
35 discussions

F42 Change Proposal: Deprecate gtk3-rs (self-contained)
by Aoife Moloney 12 Dec '24

12 Dec '24

Wiki - https://fedoraproject.org/wiki/Changes/Deprecate_gtk3-rs Discussion Thread - https://discussion.fedoraproject.org/t/f42-change-proposal-deprecate-gtk3-r… 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 == The Rust bindings for GTK3 (and related libraries) are unmaintained upstream, and are no longer updated in lockstep with bindings for GLib and other related libraries. This Change to mark the packages for the gtk3-rs crates as deprecated reflects this status. == Owner == * Name: [[User:Decathorpe| Fabio Valentini]] * Email: decathorpe (at) gmail (dot) com * Name: Rust SIG * Email: rust (at) lists (dot) fedoraproject (dot) org == Detailed Description == It was announced that the Rust bindings for GTK3 are on basic maintenance only in the [https://gtk-rs.org/blog/2023/02/10/new-release.html release announcement for gtk-rs 0.17]. The [https://gtk-rs.org/blog/2023/08/28/new-release.html release announcement for gtk-rs 0.18] noted that it would be the last release that included the GTK3 bindings. As expected, the [https://gtk-rs.org/blog/2024/06/01/new-release.html release announcement for gtk-rs 0.19] announces that support for the GTK3 bindings was officially dropped. Applications that rely on the Rust bindings for GTK3 continue to pull in version 0.18 of the Rust bindings for GLib, cairo, pango, etc. (which were obsoleted by version 0.19 and then 0.20) and the unmaintained bindings for atk and gdk. This also affects the Rust bindings for libhandy. These Rust bindings receive regular fixes for safety and correctness issues - continuing to depend on old versions is not ideal, since only critical fixes are backported to the Fedora packages for these obsolete versions (if that is even possible). The upstream project does not backport fixes or release new versions of older release branches at all. == Feedback == N/Y == Benefit to Fedora == The Rust bindings for GTK3 are obsolete. This Change ensures that no new packages are introduced that depend on them, and that they can eventually be removed from Fedora entirely (alongside old versions of the bindings for GLib, cairo, pango, etc. that are only still present because they are pulled in by the GTK3 bindings that are no longer updated in lockstep). == Scope == * Proposal owners: All affected packages are marked with `Provides: deprecated()` according to the [https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packa… Packaging Guidelines for deprecating packages]. rust-atk rust-atk-sys rust-gdk rust-gdk-sys rust-gtk rust-gtk-sys rust-gtk3-macros rust-libhandy rust-libhandy-sys * Other developers: N/A * Release engineering: N/A * Policies and guidelines: N/A * Trademark approval: N/A * Alignment with the Fedora Strategy: Err ... maybe? == Upgrade/compatibility impact == N/A == How To Test == Ensure that `dnf repoquery --provides rust-$crate-devel` includes `deprecated()` for all listed packages in Fedora 42+. == User Experience == N/A == Dependencies == Two packages currently depend on the Rust bindings for GTK3, and both already have open upstream issues for moving to GTK4: * squeekboard: https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/64 * system76-keyboard-configurator: https://github.com/pop-os/keyboard-configurator/issues/133 == Contingency Plan == N/A (not a System Wide Change) In the extremely unlikely event that adding `Provides: deprecated()` to any or all of the listed packages causes problems, this change can be easily reverted. * Contingency mechanism: N/A (not a System Wide Change) * Contingency deadline: F42 Final Freeze * Blocks release? N/A (not a System Wide Change) == Documentation == * https://gtk-rs.org/blog/2023/02/10/new-release.html * https://gtk-rs.org/blog/2023/08/28/new-release.html * https://gtk-rs.org/blog/2024/06/01/new-release.html == Release Notes == The Rust bindings for GTK3 are obsolete and officially unmaintained. The packages for them have been marked as deprecated to prevent new packages that depend on them from being added to Fedora, and they will be removed from a future release. -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

F42 Change Proposal: Automated Packit Onboarding (system-wide)
by Aoife Moloney 12 Dec '24

12 Dec '24

Wiki - https://fedoraproject.org/wiki/Changes/AutomatedPackitOnboarding Discussion thread - https://discussion.fedoraproject.org/t/f42-change-proposal-automated-onboar… 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 == To ease the onboarding process for package maintainers and their release workflows, we propose to automatically create pull requests with the initial [https://packit.dev/ Packit] configuration file for newly created projects at src.fedoraproject.org. Once merged, this configuration will enable Packit to automate the release process, reducing repetitive tasks for maintainers. == Owner == * Name: [[User:lbarczio| Laura Barcziová]], [[User:lachmanfrantisek| František Lachman]], [[User:nforro| Nikola Forró]], [[User:mmasari| Maja Massarini]], [[User:mfocko| Matej Focko]] * Email: lbarczio(a)redhat.com, flachman(a)redhat.com, nforro(a)redhat.com, mmassari(a)redhat.com, mfocko(a)redhat.com == Detailed Description == This proposal introduces a mechanism to simplify the onboarding of Fedora package maintainers to Packit by removing the need to create the configuration manually. When a new project is created at src.fedoraproject.org, a pull request with a default Packit configuration file will automatically be opened. Our proposal would be to add a CLI argument to the `fedpkg request-repo` command, similar to the existing argument `--monitor`. By default, this argument would be enabled and it would result in a Packit pull request being created upon the creation of a new repository. For maintainers who prefer not to have a Packit pull request created, this can be easily disabled by setting the relevant CLI argument during the repository creation request. Once the pull request is merged, this configuration will: * Automate the process of opening pull requests for updates when upstream releases occur (triggered by Upstream Release Monitoring), including necessary changes to the spec file and sources. * Handle subsequent Koji builds and Bodhi updates after the pull requests are merged by the maintainer. The automation would be configured by default to operate only on `rawhide`. This ensures that maintainers no longer need to spend time on repetitive release-related tasks. Instead, they can focus on package quality and innovation. The pull request will also contain detailed instructions explaining: * What is Packit and how the default configuration works. * How maintainers can customize it to suit their project’s needs, such as disabling certain tasks. * The steps to opt out of the automated pull request process. == Feedback == Discussions have indicated an interest in opt-out possibilities. As mentioned above, our current proposal would be implementing the opt-out via a CLI argument when requesting the repository creation. == Benefit to Fedora == This change aims to: * Simplify the initial setup process for using Packit, reducing barriers for Fedora package maintainers. * Decrease the time and effort spent on repetitive release-related tasks, allowing maintainers to focus on their packages’ quality and innovation. * Provide maintainers with clear guidance and support for customizing or opting out of automation to ensure the system is flexible and user-friendly. * Introduce Packit to maintainers as they create new packages, starting with typically simpler projects that are easier to automate, making it a good opportunity for them to learn about Packit. == Scope == * Proposal owners: # Implement automated pull request creation and integrate it into src.fedoraproject.org workflows (probably via `fedpkg request-repo` command and the related scripts for repo creation). # Document the new process thoroughly. # Followup support for users in the created PRs. * Other developers: This will be very isolated change that shouldn’t require much (if any) work done by other developers. If we contribute the code to the repo creation functionality, we would just need some guidance/review on these changes. * Release engineering: Coordination with release engineering is not required. A mass rebuild is not necessary for this change. * Policies and guidelines: Packaging guidelines should be updated to describe this process and the opt-out option, after the implementation is done. * Trademark approval: N/A (not needed for this Change) * Alignment with the Fedora Strategy: This proposal aligns with Fedora’s strategy of improving contributor experience and easing workflows, supporting a more efficient and user-friendly ecosystem. == Upgrade/compatibility impact == This change will not affect the compatibility/upgrade. == Early Testing (Optional) == Do you require 'QA Blueprint' support? N == How To Test == Requesting a new repo in src.fedoraproject.org should result in pull request with Packit configuration being created for that repo. == User Experience == With this change, package maintainers will experience: * Automated pull requests containing default Packit configuration files for newly created projects at src.fedoraproject.org. * Clear explanations and instructions within the pull requests to help them understand the configurations and make necessary adjustments. * The ability to quickly get started with Packit without needing to manually create configuration files. * An opt-out option for those who prefer not to/can’t (their packages are not suitable for this kind of automation) use Packit. Once the Packit configuration is merged, the release process will be almost fully automated. This includes: * Opening pull requests for required updates when upstream releases occur. * Performing Koji builds and Bodhi updates automatically after merging the updates by the maintainer. This automation significantly reduces the repetitive workload for maintainers, allowing them to dedicate their time to improving package quality and addressing other critical aspects of their projects. == Dependencies == N/A == Contingency Plan == This feature is technically not really tight to the new Fedora version. * Contingency mechanism: N/A * Contingency deadline: N/A * Blocks release? No == Documentation == There is no documentation for this yet, the work needed to be done by Packit maintainers is tracked in https://github.com/packit/packit-service/issues/2506. The documentation will be done as part of the work. == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

Voting is now open for the F41 election for FESCo!
by Aoife Moloney 09 Dec '24

09 Dec '24

Hi folks, Voting has now opened for the F41 election for FESCo. You can cast your votes from the elections app <https://elections.fedoraproject.org/> and read the candidates interviews from here, or go to the elections blog post <https://communityblog.fedoraproject.org/f41-elections-voting-is-now-open/> for a linked list of our candidates. Voting will close on Friday 20th december with the results announced on Monday the 23rd December. Best of luck to all of our great candidates! -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

Orphaned packages looking for new maintainers
by maxwell＠gtmx.me 06 Dec '24

06 Dec '24

Report started at 2024-12-06 15:00:14 UTC The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Request package ownership via the *Take* button in the left column on https://src.fedoraproject.org/rpms/<pkgname> Full report available at: https://a.gtmx.me/orphans/orphans.txt grep it for your FAS username and follow the dependency chain. For human readable dependency chains, see https://packager-dashboard.fedoraproject.org/ For all orphaned packages, see https://packager-dashboard.fedoraproject.org/orphan Package (co)maintainers Status Change ================================================================================ WoeUSB orphan 1 weeks ago aprsd orphan 2 weeks ago aterm orphan 4 weeks ago caribou0 orphan 2 weeks ago dyninst fche, jistone, lberk, mcermak, 1 weeks ago orion, orphan, wcohen fedora-business-cards orphan 0 weeks ago fedscm-admin cqi, ignatenkobrain, limb, 1 weeks ago mohanboddu, orphan, tibbs fswebcam orphan 1 weeks ago golang-github-containerd- @go-sig, orphan 1 weeks ago btrfs-2 golang-github-pin-tftp-3 @go-sig, orphan 1 weeks ago golang-github-twpayne-vfs-4 @go-sig, orphan 1 weeks ago grub-customizer cheese, orphan 3 weeks ago http-parser duck, mrunge, orphan, patches, 5 weeks ago sgallagh, vascom hyprcursor orphan 3 weeks ago hypridle orphan 3 weeks ago hyprlock orphan 3 weeks ago hyprpaper orphan 3 weeks ago hyprpicker orphan 3 weeks ago intel-cm-compiler aekoroglu, orphan 1 weeks ago intel-llvm-vc-intrinsics11 orphan 1 weeks ago ioc-writer orphan 5 weeks ago java-dirq orphan 5 weeks ago knemo orphan, rdieter 1 weeks ago lecm orphan 1 weeks ago libdirq orphan 5 weeks ago mactel-boot orphan 1 weeks ago mmlib @neuro-sig, orphan 4 weeks ago motif jexposit, orphan, twoerner 1 weeks ago mozjs102 orphan 3 weeks ago nodejs-less mrunge, orphan, patches 0 weeks ago perl-Authen-Credential orphan 5 weeks ago perl-Config-Generator orphan 5 weeks ago perl-Config-Validator orphan 5 weeks ago perl-Directory-Queue orphan 5 weeks ago perl-Messaging-Message orphan 5 weeks ago perl-Net-STOMP-Client orphan 5 weeks ago perl-No-Worries orphan 5 weeks ago perl-String-Similarity orphan 5 weeks ago php-doctrine-common orphan, remi 2 weeks ago php-doctrine-persistence orphan 2 weeks ago python-XStatic-roboto-fontface @epel-packagers-sig, 1 weeks ago @openstack-sig, hguemar, mrunge, orphan, rdopiera python-astor orphan 4 weeks ago python-auth-credential orphan 5 weeks ago python-bitmath orphan 1 weeks ago python-fedora @epel-packagers-sig, @infra- 1 weeks ago sig, orphan python-gabbi @epel-packagers-sig, 1 weeks ago @openstack-sig, apevec, orphan python-messaging orphan 5 weeks ago python-minimock @python-packagers-sig, orphan 1 weeks ago python-opentelemetry mhayden, orphan, pwouters, 3 weeks ago rominf python-opentelemetry-contrib mhayden, orphan, pwouters, 3 weeks ago rominf python-opentelemetry- mhayden, orphan, pwouters, 3 weeks ago propagator-aws-xray rominf python-opentelemetry-resource- mhayden, orphan, pwouters, 3 weeks ago detector-azure rominf python-opentelemetry-sdk- mhayden, orphan, pwouters, 3 weeks ago extension-aws rominf python-pyghmi @openstack-sig, divius, orphan 1 weeks ago python-pyroute2 @copr-sig, @python-packagers- 1 weeks ago sig, jirka, orphan python-simplevisor orphan 5 weeks ago python-singledispatch @python-packagers-sig, 5 weeks ago jcaratzas, orphan python-sphinxcontrib-github-alt @python-packagers-sig, 0 weeks ago jonathanspw, orphan python-tgscheduler orphan 1 weeks ago python-torchtext orphan 3 weeks ago python-wsgi_intercept @epel-packagers-sig, 1 weeks ago @openstack-sig, apevec, orphan python-zake @epel-packagers-sig, 1 weeks ago @openstack-sig, apevec, orphan remmina jonathanspw, orphan 1 weeks ago rubygem-http_parser.rb ilgrad, orphan 1 weeks ago rubygem-msgpack orphan 1 weeks ago rubygem-proxifier orphan 1 weeks ago rubygem-resolve-hostname orphan 1 weeks ago rust-eza @rust-sig, orphan 5 weeks ago sparse orphan 1 weeks ago spirv-llvm-translator11 orphan 1 weeks ago spooky-c orphan 1 weeks ago stompclt orphan 5 weeks ago virt-who jhnidek, orphan, ptoscano 1 weeks ago xastir orphan 2 weeks ago xdemorse orphan 2 weeks ago xpsk31 orphan 2 weeks ago xwrits orphan 1 weeks ago The following packages require above mentioned packages: Depending on: dyninst (39), status change: 2024-11-23 (1 weeks ago) systemtap (maintained by: amerey, fche, jistone, lberk, mcermak, mjw, wcohen) systemtap-5.2-1.fc42.src requires dyninst-devel = 12.3.0-7.fc41 systemtap-client-5.2-1.fc42.x86_64 requires libcommon.so.12.3()(64bit), libinstructionAPI.so.12.3()(64bit), libparseAPI.so.12.3()(64bit), libsymtabAPI.so.12.3()(64bit) systemtap-devel-5.2-1.fc42.i686 requires libcommon.so.12.3, libinstructionAPI.so.12.3, libparseAPI.so.12.3, libsymtabAPI.so.12.3 systemtap-devel-5.2-1.fc42.x86_64 requires libcommon.so.12.3()(64bit), libinstructionAPI.so.12.3()(64bit), libparseAPI.so.12.3()(64bit), libsymtabAPI.so.12.3()(64bit) systemtap-runtime-5.2-1.fc42.x86_64 requires libdyninstAPI.so.12.3()(64bit) bind9-next (maintained by: @dns-sig, pemensik, pspacek) bind9-next-32:9.21.2-4.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 gcc (maintained by: jakub, josmyers, law, mcermak, mpolacek, siddhesh) gcc-14.2.1-6.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 gcc13 (maintained by: jakub) gcc13-13.3.1-2.fc41.1.src requires systemtap-sdt-devel = 5.2-1.fc42 glib2 (maintained by: @gnome-sig, alexl, mclasen, rhughes, rstrode) glib2-2.83.0-2.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 glibc (maintained by: codonell, djdelorie, fberat, fweimer, josmyers, mcermak, mfabian, pfrankli, siddhesh, submachine) glibc-2.40.9000-21.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 java-21-openjdk (maintained by: ahughes, jandrlik, jerboaa, jvanek, pmikova, zzambers) java-21-openjdk-1:21.0.5.0.11-1.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 java-latest-openjdk (maintained by: ahughes, jerboaa, jvanek, pmikova) java-latest-openjdk-1:23.0.1.0.11-1.rolling.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 libmemcached-awesome (maintained by: remi) libmemcached-awesome-1.1.4-5.fc41.src requires systemtap-sdt-devel = 5.2-1.fc42 libvirt (maintained by: @virtmaint-sig, berrange, crobinso, laine, libvirt-maint) libvirt-10.10.0-1.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 lttng-tools (maintained by: cottsay, kstewart, ktdreyer, mjeanson) lttng-tools-2.13.14-1.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 lttng-ust (maintained by: kstewart, ktdreyer, mjeanson) lttng-ust-2.13.8-3.fc41.src requires systemtap-sdt-devel = 5.2-1.fc42 lttng-ust-devel-2.13.8-3.fc41.i686 requires systemtap-sdt-devel = 5.2-1.fc42 lttng-ust-devel-2.13.8-3.fc41.x86_64 requires systemtap-sdt-devel = 5.2-1.fc42 mariadb10.11 (maintained by: fjanus, hhorak, ljavorsk, mschorm, zmiklank) mariadb10.11-3:10.11.10-1.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 mir (maintained by: ngompa) mir-2.18.2-2.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 netatalk (maintained by: cicku, kni) netatalk-5:4.0.6-1.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 nodejs18 (maintained by: jstanek, sgallagh) nodejs18-1:18.20.2-1.fc41.src requires systemtap-sdt-devel = 5.2-1.fc42 openssl (maintained by: @crypto-team, dbelyavs, jorton, saprasad, tmraz) openssl-1:3.2.2-8.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 openvswitch (maintained by: aconole, fbl, tredaell) openvswitch-3.4.0-2.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 pcp (maintained by: agerstmayr, fberat, jkurik, lchilton, nathans, samfeifer, wcohen) pcp-6.3.2-3.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 perl (maintained by: alexl, corsepiu, iarnell, jplesnik, mspacek, ppisar, psabata, rhughes, spot) perl-4:5.40.0-512.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 perl-devel-4:5.40.0-512.fc42.i686 requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 perl-devel-4:5.40.0-512.fc42.x86_64 requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 php (maintained by: jorton, remi) php-8.4.2~RC1-1.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 postgresql15 (maintained by: anezbeda, fjanus, hhorak) postgresql15-15.8-1.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 postgresql16 (maintained by: anezbeda, fjanus, hhorak) postgresql16-16.3-6.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 postgresql17 (maintained by: fjanus) postgresql17-17.0-1.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 python3.10 (maintained by: @python-packagers-sig, churchyard, cstratak, thrnciar, torsava, vstinner) python3.10-3.10.16-1.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 python3.11 (maintained by: @python-packagers-sig, churchyard, cstratak, thrnciar, torsava, vstinner) python3.11-3.11.11-1.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 python3.12 (maintained by: @python-packagers-sig, churchyard, cstratak, thrnciar, vstinner) python3.12-3.12.8-1.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 python3.13 (maintained by: @python-packagers-sig, churchyard, ksurma) python3.13-3.13.0-1.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 python3.14 (maintained by: @python-packagers-sig, churchyard, ksurma) python3.14-3.14.0~a2-1.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 python3.6 (maintained by: @python-packagers-sig, churchyard, cstratak, torsava, vstinner) python3.6-3.6.15-39.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 python3.8 (maintained by: @python-packagers-sig, churchyard, cstratak, thrnciar, torsava, vstinner) python3.8-3.8.20-1.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 python3.9 (maintained by: @python-packagers-sig, churchyard, cstratak, thrnciar, torsava, vstinner) python3.9-3.9.21-1.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 qemu (maintained by: @virtmaint-sig, berrange, bonzini, crobinso, mcascella, rjones) qemu-2:9.2.0-0.3.rc1.fc42.src requires /usr/bin/dtrace, systemtap = 5.2-1.fc42, systemtap-sdt-devel = 5.2-1.fc42 ruby (maintained by: @ruby-packagers-sig, mtasaka, vondruch) ruby-3.3.6-17.fc42.src requires /usr/bin/dtrace, systemtap-sdt-devel = 5.2-1.fc42 sssd (maintained by: @sssd-maintainers, abbra, asn, atikhonov, lslebodn, nalin, pbrezina, sbose, sgallagh, simo) sssd-2.10.0-3.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 systemd (maintained by: daandemeyer, harald, jsynacek, lennart, lnykryn, michich, msekleta, systemd-maint, yuwata, zbyszek) systemd-257~rc3-1.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 tcl (maintained by: jskarvad) tcl-1:8.6.15-6.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42, systemtap-sdt-dtrace = 5.2-1.fc42 tuned (maintained by: jskarvad, pzacik) tuned-utils-systemtap-2.24.1-1.fc42.noarch requires /usr/bin/stap, systemtap = 5.2-1.fc42 xorg-x11-server (maintained by: airlied, ajax, alexl, bskeggs, jexposit, ofourdan, rhughes, rstrode, whot) xorg-x11-server-21.1.14-3.fc42.src requires systemtap-sdt-devel = 5.2-1.fc42 Too many dependencies for dyninst, not all listed here Depending on: golang-github-pin-tftp-3 (1), status change: 2024-11-23 (1 weeks ago) gobuster (maintained by: @go-sig, fab) gobuster-3.6.0-1.fc42.src requires golang(github.com/pin/tftp/v3) = 3.0.0-5.fc41 golang-github-oj-gobuster-devel-3.6.0-1.fc42.noarch requires golang(github.com/pin/tftp/v3) = 3.0.0-5.fc41 Depending on: http-parser (8), status change: 2024-10-30 (5 weeks ago) AusweisApp2 (maintained by: belegdol) AusweisApp2-2.2.2-1.fc42.src requires http-parser-devel = 2.9.4-12.fc41 AusweisApp2-2.2.2-1.fc42.x86_64 requires libhttp_parser.so.2()(64bit) flamethrower (maintained by: @dns-sig, pemensik) flamethrower-0.11.0-28.fc41.src requires http-parser-devel = 2.9.4-12.fc41 flamethrower-0.11.0-28.fc41.x86_64 requires libhttp_parser.so.2()(64bit) jabberd (maintained by: dmaphy) jabberd-2.6.1-28.fc41.src requires http-parser-devel = 2.9.4-12.fc41 jabberd-2.6.1-28.fc41.x86_64 requires libhttp_parser.so.2()(64bit) julia (maintained by: nalimilan) julia-1.11.0-13.rc3.fc42.src requires http-parser-devel = 2.9.4-12.fc41 slurm (maintained by: @epel-packagers-sig, neil, salimma) slurm-24.05.2-2.fc42.src requires http-parser-devel = 2.9.4-12.fc41 slurm-slurmrestd-24.05.2-2.fc42.x86_64 requires libhttp_parser.so.2()(64bit) cantor (maintained by: @kde-sig, @r-maint-sig, rdieter, than) cantor-24.11.90-1.fc42.src requires julia-devel = 1.11.0-13.rc3.fc42 cantor-24.11.90-1.fc42.x86_64 requires libjulia.so.1.11()(64bit), libjulia.so.1.11(JL_LIBJULIA_1.11)(64bit) vim-syntastic (maintained by: mhjacks) vim-syntastic-julia-3.10.0-24.fc42.noarch requires julia = 1.11.0-13.rc3.fc42 LabPlot (maintained by: @kde-sig, @scitech_sig, cicku, topazus) LabPlot-2.11.80~20241117.082905.4e770ae-2.fc42.src requires cantor-devel = 24.11.90-1.fc42 Depending on: hyprcursor (2), status change: 2024-11-10 (3 weeks ago) hyprland (maintained by: nightishaman) hyprland-0.45.2-1.fc42.src requires pkgconfig(hyprcursor) = 0.1.10 hyprland-0.45.2-1.fc42.x86_64 requires hyprcursor(x86-64) = 0.1.10-1.fc42, libhyprcursor.so.0()(64bit) hyprland-devel-0.45.2-1.fc42.x86_64 requires pkgconfig(hyprcursor) = 0.1.10 nwg-dock-hyprland (maintained by: @go-sig, nightishaman) nwg-dock-hyprland-0.3.3-1.fc42.x86_64 requires hyprland = 0.45.2-1.fc42 Depending on: intel-llvm-vc-intrinsics11 (1), status change: 2024-11-27 (1 weeks ago) intel-cm-compiler (maintained by: aekoroglu, orphan) intel-cm-compiler-1.0.144-8.20240131gitcc4f5b6.fc41.src requires intel-llvm-vc-intrinsics11-devel = 0.17.0-2.20240206git1ba2c43.fc41 Depending on: mmlib (1), status change: 2024-11-02 (4 weeks ago) eegview (maintained by: @neuro-sig, aekoroglu, ankursinha) eegview-1.1-8.fc41.src requires mmlib-devel = 1.4.2-13.fc41 eegview-1.1-8.fc41.x86_64 requires libmmlib.so.1()(64bit), libmmlib.so.1(MMLIB_1.0)(64bit) Depending on: motif (21), status change: 2024-11-23 (1 weeks ago) alliance (maintained by: cicku, corsepiu) alliance-5.1.1-34.20160506gitd8c05cd.fc41.i686 requires libXm.so.4 alliance-5.1.1-34.20160506gitd8c05cd.fc41.src requires motif-devel = 2.3.4-35.fc41 alliance-5.1.1-34.20160506gitd8c05cd.fc41.x86_64 requires libXm.so.4()(64bit) ddd (maintained by: limb) ddd-3.4.1-2.fc42.src requires motif-devel = 2.3.4-35.fc41 ddd-3.4.1-2.fc42.x86_64 requires libXm.so.4()(64bit) dx (maintained by: corsepiu) dx-4.4.4-68.fc41.src requires motif-devel = 2.3.4-35.fc41 dx-4.4.4-68.fc41.x86_64 requires libXm.so.4()(64bit) dx-libs-4.4.4-68.fc41.i686 requires libXm.so.4 dx-libs-4.4.4-68.fc41.x86_64 requires libXm.so.4()(64bit) fbb (maintained by: jskarvad) fbb-7.0.11-1.fc41.8.src requires motif-devel = 2.3.4-35.fc41 fbb-gui-7.0.11-1.fc41.8.x86_64 requires libXm.so.4()(64bit) fbida (maintained by: adrian) fbida-2.14-19.fc41.src requires motif-devel = 2.3.4-35.fc41 fbida-ida-2.14-19.fc41.x86_64 requires libXm.so.4()(64bit) geomview (maintained by: rdieter) geomview-1.9.5-27.fc41.src requires motif-devel = 2.3.4-35.fc41 geomview-1.9.5-27.fc41.x86_64 requires libXm.so.4()(64bit) grace (maintained by: jamatos, terjeros) grace-5.1.25-40.fc41.x86_64 requires libXm.so.4()(64bit) mesa-libGLw (maintained by: ajax, jexposit) mesa-libGLw-8.0.0-30.fc41.i686 requires libXm.so.4 mesa-libGLw-8.0.0-30.fc41.src requires motif-devel = 2.3.4-35.fc41 mesa-libGLw-8.0.0-30.fc41.x86_64 requires libXm.so.4()(64bit) mesa-libGLw-devel-8.0.0-30.fc41.i686 requires motif-devel = 2.3.4-35.fc41 mesa-libGLw-devel-8.0.0-30.fc41.x86_64 requires motif-devel = 2.3.4-35.fc41 nedit (maintained by: jnovy, tdawson) nedit-5.7-18.fc41.src requires motif-devel = 2.3.4-35.fc41 nedit-5.7-18.fc41.x86_64 requires libXm.so.4()(64bit) pcb-rnd (maintained by: avigne) pcb-rnd-2.4.0-8.fc39.src requires motif-devel = 2.3.4-35.fc41 pcb-rnd-hid-lesstif-2.4.0-8.fc39.x86_64 requires libXm.so.4()(64bit) polyml (maintained by: dmoerner, jjames) polyml-5.9.1-4.fc41.src requires motif-devel = 2.3.4-35.fc41 ski (maintained by: sharkcz) ski-1.4.0-5.fc41.src requires motif-devel = 2.3.4-35.fc41 ski-1.4.0-5.fc41.x86_64 requires libXm.so.4()(64bit) twlog (maintained by: hobbes1069) twlog-3.4-11.fc41.x86_64 requires libXm.so.4()(64bit) vtk (maintained by: @scitech_sig, orion) vtk-9.2.6-21.fc42.src requires motif-devel = 2.3.4-35.fc41 xastir (maintained by: orphan) xastir-1:2.2.0-6.fc42.src requires motif-devel = 2.3.4-35.fc41 xastir-1:2.2.0-6.fc42.x86_64 requires libXm.so.4()(64bit) xawtv (maintained by: buc, mchehab) xawtv-3.107-12.fc41.src requires motif-devel = 2.3.4-35.fc41 xawtv-motv-3.107-12.fc41.x86_64 requires libXm.so.4()(64bit) xawtv-mtt-3.107-12.fc41.x86_64 requires libXm.so.4()(64bit) xbae (maintained by: limb, stevetraylen) xbae-4.60.4-42.fc41.i686 requires libXm.so.4 xbae-4.60.4-42.fc41.src requires motif-devel = 2.3.4-35.fc41 xbae-4.60.4-42.fc41.x86_64 requires libXm.so.4()(64bit) xbae-devel-4.60.4-42.fc41.i686 requires motif-devel = 2.3.4-35.fc41 xbae-devel-4.60.4-42.fc41.x86_64 requires motif-devel = 2.3.4-35.fc41 xephem (maintained by: @astro-sig, mattia) xephem-4.2.0-3.fc41.src requires motif-devel = 2.3.4-35.fc41 xephem-4.2.0-3.fc41.x86_64 requires libXm.so.4()(64bit) xlockmore (maintained by: adrian, mcermak) xlockmore-5.77-2.fc41.src requires motif-devel = 2.3.4-35.fc41 xlockmore-motif-5.77-2.fc41.x86_64 requires libXm.so.4()(64bit) xmakemol (maintained by: jussilehtola) xmakemol-5.16-20.fc41.src requires motif-devel = 2.3.4-35.fc41 xmakemol-5.16-20.fc41.x86_64 requires libXm.so.4()(64bit) xmbdfed (maintained by: spot) xmbdfed-4.7-37.fc41.src requires motif-devel = 2.3.4-35.fc41 xmbdfed-4.7-37.fc41.x86_64 requires libXm.so.4()(64bit) Too many dependencies for motif, not all listed here Depending on: mozjs102 (1), status change: 2024-11-14 (3 weeks ago) erlang-js (maintained by: peter) erlang-js-1.9.3-9.fc41.src requires mozjs102-devel = 102.15.1-8.fc42 erlang-js-1.9.3-9.fc41.x86_64 requires libmozjs-102.so.0()(64bit), libmozjs-102.so.0(mozjs_102)(64bit) Depending on: perl-Authen-Credential (1), status change: 2024-10-30 (5 weeks ago) stompclt (maintained by: orphan) stompclt-1.8-8.fc41.noarch requires perl(Authen::Credential) = 1.2 Depending on: perl-Config-Validator (2), status change: 2024-10-30 (5 weeks ago) perl-Config-Generator (maintained by: orphan) perl-Config-Generator-1.1-9.fc41.noarch requires perl(Config::Validator) = 1.4 perl-Config-Generator-1.1-9.fc41.src requires perl(Config::Validator) = 1.4 stompclt (maintained by: orphan) stompclt-1.8-8.fc41.noarch requires perl(Config::Validator) = 1.4 Depending on: perl-Directory-Queue (3), status change: 2024-10-30 (5 weeks ago) perl-Messaging-Message (maintained by: orphan) perl-Messaging-Message-1.7-9.fc41.src requires perl(Directory::Queue) = 2.2 stompclt (maintained by: orphan) stompclt-1.8-8.fc41.noarch requires perl(Directory::Queue) = 2.2, perl(Messaging::Message) = 1.7, perl(Messaging::Message::Queue) = 1.7, perl(Net::STOMP::Client) = 2.5 perl-Net-STOMP-Client (maintained by: orphan) perl-Net-STOMP-Client-2.5-9.fc41.src requires perl(Messaging::Message) = 1.7 Depending on: perl-Messaging-Message (2), status change: 2024-10-30 (5 weeks ago) perl-Net-STOMP-Client (maintained by: orphan) perl-Net-STOMP-Client-2.5-9.fc41.src requires perl(Messaging::Message) = 1.7 stompclt (maintained by: orphan) stompclt-1.8-8.fc41.noarch requires perl(Messaging::Message) = 1.7, perl(Messaging::Message::Queue) = 1.7, perl(Net::STOMP::Client) = 2.5 Depending on: perl-Net-STOMP-Client (1), status change: 2024-10-30 (5 weeks ago) stompclt (maintained by: orphan) stompclt-1.8-8.fc41.noarch requires perl(Net::STOMP::Client) = 2.5 Depending on: perl-No-Worries (8), status change: 2024-10-30 (5 weeks ago) perl-Authen-Credential (maintained by: orphan) perl-Authen-Credential-1.2-9.fc41.noarch requires perl(No::Worries::Die) = 1.7 perl-Authen-Credential-1.2-9.fc41.src requires perl(No::Worries::Die) = 1.7 perl-Config-Generator (maintained by: orphan) perl-Config-Generator-1.1-9.fc41.noarch requires perl(Config::Validator) = 1.4, perl(No::Worries) = 1.7, perl(No::Worries::Die) = 1.7, perl(No::Worries::Dir) = 1.7, perl(No::Worries::Export) = 1.7, perl(No::Worries::File) = 1.7, perl(No::Worries::Log) = 1.7, perl(No::Worries::Proc) = 1.7, perl(No::Worries::Stat) = 1.7, perl(No::Worries::String) = 1.7, perl(No::Worries::Warn) = 1.7 perl-Config-Generator-1.1-9.fc41.src requires perl(Config::Validator) = 1.4, perl(No::Worries) = 1.7 perl-Config-Validator (maintained by: orphan) perl-Config-Validator-1.4-9.fc41.noarch requires perl(No::Worries::Die) = 1.7, perl(No::Worries::Export) = 1.7 perl-Config-Validator-1.4-9.fc41.src requires perl(No::Worries) = 1.7 perl-Directory-Queue (maintained by: orphan) perl-Directory-Queue-2.2-7.fc41.noarch requires perl(No::Worries) = 1.7, perl(No::Worries::Die) = 1.7, perl(No::Worries::Export) = 1.7, perl(No::Worries::File) = 1.7, perl(No::Worries::Stat) = 1.7, perl(No::Worries::Warn) = 1.7 perl-Directory-Queue-2.2-7.fc41.src requires perl(No::Worries) = 1.7 perl-Messaging-Message (maintained by: orphan) perl-Messaging-Message-1.7-9.fc41.noarch requires perl(No::Worries::Die) = 1.7, perl(No::Worries::Export) = 1.7 perl-Messaging-Message-1.7-9.fc41.src requires perl(Directory::Queue) = 2.2, perl(No::Worries) = 1.7 perl-Net-STOMP-Client (maintained by: orphan) perl-Net-STOMP-Client-2.5-9.fc41.noarch requires perl(No::Worries::Die) = 1.7, perl(No::Worries::Export) = 1.7, perl(No::Worries::File) = 1.7, perl(No::Worries::Log) = 1.7 perl-Net-STOMP-Client-2.5-9.fc41.src requires perl(Messaging::Message) = 1.7, perl(No::Worries) = 1.7 python-simplevisor (maintained by: orphan) python-simplevisor-1.3-12.fc41.src requires perl(No::Worries) = 1.7, perl(No::Worries::Die) = 1.7, perl(No::Worries::Log) = 1.7, perl(No::Worries::PidFile) = 1.7, perl(No::Worries::Proc) = 1.7, perl(No::Worries::Syslog) = 1.7, perl(No::Worries::Warn) = 1.7 python3-simplevisor-1.3-12.fc41.noarch requires perl(No::Worries) = 1.7, perl(No::Worries::Die) = 1.7, perl(No::Worries::Log) = 1.7, perl(No::Worries::PidFile) = 1.7, perl(No::Worries::Proc) = 1.7, perl(No::Worries::Syslog) = 1.7, perl(No::Worries::Warn) = 1.7 stompclt (maintained by: orphan) stompclt-1.8-8.fc41.noarch requires perl(Authen::Credential) = 1.2, perl(Config::Validator) = 1.4, perl(Directory::Queue) = 2.2, perl(Messaging::Message) = 1.7, perl(Messaging::Message::Queue) = 1.7, perl(Net::STOMP::Client) = 2.5, perl(No::Worries) = 1.7, perl(No::Worries::Die) = 1.7, perl(No::Worries::File) = 1.7, perl(No::Worries::Log) = 1.7, perl(No::Worries::PidFile) = 1.7, perl(No::Worries::Proc) = 1.7, perl(No::Worries::Syslog) = 1.7, perl(No::Worries::Warn) = 1.7 Depending on: perl-String-Similarity (1), status change: 2024-10-30 (5 weeks ago) publican (maintained by: jfearn, rlandmann) publican-4.3.2-31.fc42.noarch requires perl(String::Similarity) = 1.04 publican-4.3.2-31.fc42.src requires perl(String::Similarity) = 1.04 Depending on: php-doctrine-persistence (9), status change: 2024-11-18 (2 weeks ago) php-doctrine-common (maintained by: orphan, remi) php-doctrine-common-1:2.13.3-13.fc41.noarch requires php-composer(doctrine/annotations) = 1.14.3, php-composer(doctrine/cache) = 1.13.0, php-composer(doctrine/persistence) = 1.3.8 php-doctrine-datafixtures (maintained by: remi, siwinski) php-doctrine-datafixtures-1.6.5-2.fc39.noarch requires php-composer(doctrine/persistence) = 1.3.8 php-doctrine-datafixtures-1.6.5-2.fc39.src requires php-composer(doctrine/persistence) = 1.3.8, php-symfony4-cache = 4.4.50-8.fc41 php-symfony4 (maintained by: remi, siwinski) php-symfony4-doctrine-bridge-4.4.50-8.fc41.noarch requires php-composer(doctrine/persistence) = 1.3.8 php-symfony4-framework-bundle-4.4.50-8.fc41.noarch requires php-composer(doctrine/cache) = 1.13.0 php-symfony4-common-4.4.50-8.fc41.noarch requires php-composer(symfony/polyfill-php80) = 1.28.0 php-symfony4-config-4.4.50-8.fc41.noarch requires php-composer(symfony/polyfill-php81) = 1.28.0 php-symfony4-console-4.4.50-8.fc41.noarch requires php-composer(symfony/polyfill-php73) = 1.28.0 php-symfony4-http-client-4.4.50-8.fc41.noarch requires php-composer(symfony/polyfill-php73) = 1.28.0 php-symfony4-http-kernel-4.4.50-8.fc41.noarch requires php-composer(symfony/polyfill-php73) = 1.28.0 php-symfony4-mime-4.4.50-8.fc41.noarch requires php-composer(symfony/polyfill-mbstring) = 1.28.0 php-symfony4-var-dumper-4.4.50-8.fc41.noarch requires php-composer(symfony/polyfill-php72) = 1.28.0 php-symfony4-web-link-4.4.50-8.fc41.noarch requires php-composer(symfony/polyfill-php72) = 1.28.0 php-symfony4-twig-bridge-4.4.50-8.fc41.noarch requires php-composer(twig/twig) = 1.44.7 php-symfony4-twig-bundle-4.4.50-8.fc41.noarch requires php-composer(twig/twig) = 1.44.7 php-symfony4-web-profiler-bundle-4.4.50-8.fc41.noarch requires php-composer(twig/twig) = 1.44.7 php-doctrine-annotations (maintained by: remi, siwinski) php-doctrine-annotations-1.14.3-2.fc39.src requires php-composer(doctrine/cache) = 1.13.0, php-composer(symfony/cache) = 4.4.50 php-doctrine-cache (maintained by: remi, siwinski) php-doctrine-cache-1.13.0-4.fc39.src requires php-composer(symfony/cache) = 4.4.50, php-composer(symfony/var-exporter) = 4.4.50 php-doctrine-doctrine-cache-bundle (maintained by: remi, siwinski) php-doctrine-doctrine-cache-bundle-1.4.0-11.fc41.noarch requires php-composer(doctrine/cache) = 1.13.0, php-composer(symfony/doctrine-bridge) = 4.4.50 php-symfony-polyfill (maintained by: siwinski) php-symfony-polyfill-1.28.0-1.fc40.src requires php-symfony4-intl = 4.4.50-8.fc41, php-symfony4-var-dumper = 4.4.50-8.fc41 php-twig (maintained by: siwinski) php-twig-1.44.7-6.fc41.src requires php-composer(symfony/debug) = 4.4.50 php-doctrine-persistence (maintained by: orphan) php-doctrine-persistence-1.3.8-10.fc41.noarch requires php-composer(doctrine/annotations) = 1.14.3, php-composer(doctrine/cache) = 1.13.0 php-doctrine-persistence-1.3.8-10.fc41.src requires php-composer(doctrine/annotations) = 1.14.3, php-composer(doctrine/cache) = 1.13.0 Depending on: python-fedora (6), status change: 2024-11-23 (1 weeks ago) fedora-business-cards (maintained by: orphan) fedora-business-cards-2.3.0-12.fc41.noarch requires python3-fedora = 1.1.1-14.fc41 fedora-easy-karma (maintained by: @qa-tools-sig, kparal) fedora-easy-karma-0.53-5.fc41.noarch requires python3-fedora = 1.1.1-14.fc41 fedscm-admin (maintained by: cqi, ignatenkobrain, limb, mohanboddu, orphan, tibbs) fedscm-admin-1.1.7-9.fc41.noarch requires python3.13dist(python-fedora) = 1.1.1 fedscm-admin-1.1.7-9.fc41.src requires python3dist(python-fedora) = 1.1.1 odcs (maintained by: cqi, hlin, lsedlar, qwan) odcs-0.8.1-1.fc42.noarch requires python3-fedora = 1.1.1-14.fc41 odcs-0.8.1-1.fc42.src requires python3-fedora = 1.1.1-14.fc41 pag (maintained by: hguemar, lsedlar) pag-0.8-23.fc41.noarch requires python3-fedora = 1.1.1-14.fc41 pag-0.8-23.fc41.src requires python3-fedora = 1.1.1-14.fc41 sigul (maintained by: kevin, mitr) sigul-1.2-4.fc41.src requires python3-fedora = 1.1.1-14.fc41 sigul-bridge-1.2-4.fc41.x86_64 requires python3-fedora = 1.1.1-14.fc41 Depending on: python-minimock (2), status change: 2024-11-23 (1 weeks ago) gpodder (maintained by: limb, vpv) gpodder-3.11.4-6.fc41.src requires python3-minimock = 1.2.8-38.fc41, python3-mygpoclient = 1.10-1.fc42 gpodder-3.11.4-6.fc41.noarch requires python3-mygpoclient = 1.10-1.fc42 python-mygpoclient (maintained by: limb, vpv) python-mygpoclient-1.10-1.fc42.src requires python3-minimock = 1.2.8-38.fc41 Depending on: python-opentelemetry (9), status change: 2024-11-09 (3 weeks ago) python-elastic-transport (maintained by: aekoroglu) python-elastic-transport-8.13.1-1.fc41.src requires python3dist(opentelemetry-api) = 1.27, python3dist(opentelemetry-sdk) = 1.27 python-opentelemetry-contrib (maintained by: mhayden, orphan, pwouters, rominf) python-opentelemetry-contrib-2:1.27.0-2.fc42.src requires python3dist(elasticsearch) = 8.14, python3dist(opentelemetry-api) = 1.27, python3dist(opentelemetry-propagator-aws-xray) = 1.0.2, python3dist(opentelemetry-sdk) = 1.27, python3dist(opentelemetry-semantic-conventions) = 0.48~b0, python3dist(opentelemetry-test-utils) = 0.48~b0 python3-opentelemetry-distro-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-sdk) = 1.27 python3-opentelemetry-distro+otlp-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-exporter-otlp) = 1.27 python3-opentelemetry-exporter-richconsole-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-sdk) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-aiohttp-client-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-aiohttp-server-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-aiopg-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-asgi-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-asyncio-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-asyncpg-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-aws-lambda-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-propagator-aws-xray) = 1.0.2, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-boto-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-boto3sqs-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-botocore-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-propagator-aws-xray) = 1.0.2, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-celery-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-dbapi-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-django-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-elasticsearch-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-fastapi-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-flask-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-httpx-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-jinja2-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-kafka-python-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-logging-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-mysql-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-mysqlclient-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-pika-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-psycopg-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-psycopg2-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-pymemcache-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-pymongo-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-pymysql-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-pyramid-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-redis-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-requests-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-sqlalchemy-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-sqlite3-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-system-metrics-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-threading-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27 python3-opentelemetry-instrumentation-tornado-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-urllib-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-urllib3-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-instrumentation-wsgi-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-semantic-conventions) = 0.48~b0 python3-opentelemetry-processor-baggage-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-sdk) = 1.27 python3-opentelemetry-propagator-ot-trace-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-api) = 1.27, python3.13dist(opentelemetry-sdk) = 1.27 python3-opentelemetry-instrumentation-elasticsearch+instruments-2:0.48~b0-2.fc42.noarch requires python3.13dist(elasticsearch) = 8.14 python-opentelemetry-propagator-aws-xray (maintained by: mhayden, orphan, pwouters, rominf) python-opentelemetry-propagator-aws-xray-1.0.2-1.fc41.src requires python3dist(opentelemetry-api) = 1.27, python3dist(opentelemetry-sdk) = 1.27 python3-opentelemetry-propagator-aws-xray-1.0.2-1.fc41.noarch requires python3.13dist(opentelemetry-api) = 1.27 python-opentelemetry-resource-detector-azure (maintained by: mhayden, orphan, pwouters, rominf) python-opentelemetry-resource-detector-azure-0.1.5-4.fc41.src requires python3dist(opentelemetry-sdk) = 1.27 python3-opentelemetry-resource-detector-azure-0.1.5-4.fc41.noarch requires python3.13dist(opentelemetry-sdk) = 1.27 python-opentelemetry-sdk-extension-aws (maintained by: mhayden, orphan, pwouters, rominf) python-opentelemetry-sdk-extension-aws-2.0.2-1.fc41.src requires python3dist(opentelemetry-sdk) = 1.27 python3-opentelemetry-sdk-extension-aws-2.0.2-1.fc41.noarch requires python3.13dist(opentelemetry-sdk) = 1.27 python-elasticsearch (maintained by: aekoroglu, stevetraylen) python-elasticsearch-8.14.0-2.fc41.src requires python3dist(elastic-transport) = 8.13.1 python3-elasticsearch-8.14.0-2.fc41.noarch requires python3.13dist(elastic-transport) = 8.13.1 python-sentry-sdk (maintained by: edward-evans-aiven, italomga, orange-kao, pwouters, rominf, rommell) python-sentry-sdk-2.17.0-3.fc42.src requires python3dist(opentelemetry-distro) = 0.48~b0 python3-sentry-sdk+opentelemetry-2.17.0-3.fc42.noarch requires python3.13dist(opentelemetry-distro) = 0.48~b0 python3-sentry-sdk+opentelemetry-experimental-2.17.0-3.fc42.noarch requires python3.13dist(opentelemetry-distro) = 0.48~b0 matrix-synapse (maintained by: @epel-packagers-sig, dcallagh, jonathanspw, v02460) matrix-synapse-1.120.1-1.fc42.src requires python3dist(sentry-sdk) = 2.17 matrix-synapse+sentry-1.120.1-1.fc42.x86_64 requires python3.13dist(sentry-sdk) = 2.17 plasma-drkonqi (maintained by: @kde-sig, mkyral) plasma-drkonqi-6.2.4-1.fc42.i686 requires python3dist(sentry-sdk) = 2.17 plasma-drkonqi-6.2.4-1.fc42.x86_64 requires python3dist(sentry-sdk) = 2.17 Depending on: python-opentelemetry-contrib (3), status change: 2024-11-09 (3 weeks ago) python-sentry-sdk (maintained by: edward-evans-aiven, italomga, orange-kao, pwouters, rominf, rommell) python-sentry-sdk-2.17.0-3.fc42.src requires python3dist(opentelemetry-distro) = 0.48~b0 python3-sentry-sdk+opentelemetry-2.17.0-3.fc42.noarch requires python3.13dist(opentelemetry-distro) = 0.48~b0 python3-sentry-sdk+opentelemetry-experimental-2.17.0-3.fc42.noarch requires python3.13dist(opentelemetry-distro) = 0.48~b0 matrix-synapse (maintained by: @epel-packagers-sig, dcallagh, jonathanspw, v02460) matrix-synapse-1.120.1-1.fc42.src requires python3dist(sentry-sdk) = 2.17 matrix-synapse+sentry-1.120.1-1.fc42.x86_64 requires python3.13dist(sentry-sdk) = 2.17 plasma-drkonqi (maintained by: @kde-sig, mkyral) plasma-drkonqi-6.2.4-1.fc42.i686 requires python3dist(sentry-sdk) = 2.17 plasma-drkonqi-6.2.4-1.fc42.x86_64 requires python3dist(sentry-sdk) = 2.17 Depending on: python-opentelemetry-propagator-aws-xray (4), status change: 2024-11-09 (3 weeks ago) python-opentelemetry-contrib (maintained by: mhayden, orphan, pwouters, rominf) python-opentelemetry-contrib-2:1.27.0-2.fc42.src requires python3dist(opentelemetry-propagator-aws-xray) = 1.0.2 python3-opentelemetry-instrumentation-aws-lambda-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-propagator-aws-xray) = 1.0.2 python3-opentelemetry-instrumentation-botocore-2:0.48~b0-2.fc42.noarch requires python3.13dist(opentelemetry-propagator-aws-xray) = 1.0.2 python-sentry-sdk (maintained by: edward-evans-aiven, italomga, orange-kao, pwouters, rominf, rommell) python-sentry-sdk-2.17.0-3.fc42.src requires python3dist(opentelemetry-distro) = 0.48~b0 python3-sentry-sdk+opentelemetry-2.17.0-3.fc42.noarch requires python3.13dist(opentelemetry-distro) = 0.48~b0 python3-sentry-sdk+opentelemetry-experimental-2.17.0-3.fc42.noarch requires python3.13dist(opentelemetry-distro) = 0.48~b0 matrix-synapse (maintained by: @epel-packagers-sig, dcallagh, jonathanspw, v02460) matrix-synapse-1.120.1-1.fc42.src requires python3dist(sentry-sdk) = 2.17 matrix-synapse+sentry-1.120.1-1.fc42.x86_64 requires python3.13dist(sentry-sdk) = 2.17 plasma-drkonqi (maintained by: @kde-sig, mkyral) plasma-drkonqi-6.2.4-1.fc42.i686 requires python3dist(sentry-sdk) = 2.17 plasma-drkonqi-6.2.4-1.fc42.x86_64 requires python3dist(sentry-sdk) = 2.17 Depending on: python-pyghmi (1), status change: 2024-11-23 (1 weeks ago) python-virtualbmc (maintained by: jorti) python-virtualbmc-3.1.0-6.fc41.src requires python3-pyghmi = 1.5.69-4.fc41 python3-virtualbmc-3.1.0-6.fc41.noarch requires python3.13dist(pyghmi) = 1.5.69 Depending on: python-pyroute2 (21), status change: 2024-11-23 (1 weeks ago) mock (maintained by: @copr-sig, jcwillia, msuchy, praiskup) mock-5.9-1.fc42.noarch requires python3-pyroute2 = 0.7.12-4.fc41 mock-5.9-1.fc42.src requires python3-pyroute2 = 0.7.12-4.fc41 centos-packager (maintained by: @epel-packagers-sig, dcavalca) centos-packager-0.7.0-15.fc41.noarch requires mock = 5.9-1.fc42 copr-backend (maintained by: @copr-sig, frostyx, msuchy, praiskup) copr-backend-2.1-1.fc42.noarch requires mock = 5.9-1.fc42 copr-rpmbuild (maintained by: @copr-sig, frostyx, praiskup) copr-builder-1.2-1.fc42.x86_64 requires mock = 5.9-1.fc42 copr-rpmbuild-1.2-1.fc42.x86_64 requires mock = 5.9-1.fc42, mock-filesystem = 5.9-1.fc42 csmock (maintained by: kdudka, lzaoral, svashisht) csmock-common-3.8.0-1.fc42.noarch requires mock = 5.9-1.fc42 fedora-packager (maintained by: @epel-packagers-sig, @infra-sig, dcavalca, mohanboddu) fedora-packager-1.0-4.fc42.noarch requires mock = 5.9-1.fc42 fedora-review (maintained by: frostyx, leamas, maxamillion, ngompa, pingou, salimma) fedora-review-0.10.0-11.fc41.noarch requires fedora-packager = 1.0-4.fc42, mock = 5.9-1.fc42 fedora-review-0.10.0-11.fc41.src requires mock = 5.9-1.fc42 koji (maintained by: kevin, mikem, puiterwijk) koji-builder-1.35.1-4.fc42.noarch requires mock = 5.9-1.fc42 libvirt-test-API (maintained by: lnie) libvirt-test-API-1.1-15.fc41.src requires mock = 5.9-1.fc42 mock-core-configs (maintained by: @copr-sig, msuchy, praiskup) mock-core-configs-41.4-1.fc42.noarch requires mock = 5.9-1.fc42, mock-filesystem = 5.9-1.fc42 module-build (maintained by: mcurlej) module-build-0.2.1-9.fc41.noarch requires mock = 5.9-1.fc42, mock-scm = 5.9-1.fc42 module-build-0.2.1-9.fc41.src requires mock = 5.9-1.fc42 perl-Fedora-Rebuild (maintained by: jplesnik, ppisar) perl-Fedora-Rebuild-0.12.1-33.fc41.noarch requires mock = 5.9-1.fc42 python-prawcore (maintained by: fab) python-prawcore-2.4.0-1.fc42.src requires mock = 5.9-1.fc42 rpkg (maintained by: cqi, lsedlar, onosek) python3-rpkg-1.67-4.fc42.noarch requires mock = 5.9-1.fc42 retrace-server (maintained by: @abrt-sig, abrt-team, mmarusak) retrace-server-1.24.2-8.fc41.noarch requires mock = 5.9-1.fc42 osh (maintained by: svashisht) osh-worker-1.0.0.20240523.115004.g305cd56-3.fc41.noarch requires csmock = 3.8.0-1.fc42 R2spec (maintained by: pingou) R2spec-5.0.0-17.fc41.noarch requires fedora-packager = 1.0-4.fc42 cmake-fedora (maintained by: fujiwara) cmake-fedora-2.9.3-21.fc41.noarch requires fedora-packager = 1.0-4.fc42 fbrnch (maintained by: petersen) fbrnch-1.5-22.fc42.x86_64 requires fedora-packager-kerberos = 1.0-4.fc42 oct2spec (maintained by: jamatos) oct2spec-1.1-19.fc41.noarch requires fedora-packager = 1.0-4.fc42 tito (maintained by: frostyx, maxamillion) tito-0.6.27-1.fc42.noarch requires fedora-packager = 1.0-4.fc42 Too many dependencies for python-pyroute2, not all listed here Depending on: python-sphinxcontrib-github-alt (2), status change: 2024-12-02 (0 weeks ago) python-jupyter-console (maintained by: @python-packagers-sig, qulogic) python-jupyter-console-6.6.3-8.fc41.src requires python3dist(sphinxcontrib-github-alt) = 1.2 ilua (maintained by: @python-packagers-sig, churchyard) ilua-0.2.1-25.fc41.noarch requires python3.13dist(jupyter-console) = 6.6.3 ilua-0.2.1-25.fc41.src requires /usr/bin/jupyter-console, python3dist(jupyter-console) = 6.6.3 Depending on: python-wsgi_intercept (1), status change: 2024-11-29 (1 weeks ago) python-gabbi (maintained by: @epel-packagers-sig, @openstack-sig, apevec, orphan) python-gabbi-3.0.0-1.fc42.src requires python3dist(wsgi-intercept) = 1.13.1 python3-gabbi-3.0.0-1.fc42.noarch requires python3.13dist(wsgi-intercept) = 1.13.1 Depending on: python-zake (1), status change: 2024-11-23 (1 weeks ago) python-taskflow (maintained by: @openstack-sig, eharney, jcapitao) python-taskflow-5.9.1-1.fc42.src requires python3dist(zake) = 0.2.2 Depending on: rubygem-http_parser.rb (21), status change: 2024-11-23 (1 weeks ago) rubygem-em-http-request (maintained by: @ruby-packagers-sig, jackorp) rubygem-em-http-request-1.1.7-12.fc41.noarch requires rubygem(http_parser.rb) = 0.8.0 rubygem-em-http-request-1.1.7-12.fc41.src requires rubygem(http_parser.rb) = 0.8.0 rubygem-em-websocket (maintained by: @ruby-packagers-sig, jackorp) rubygem-em-websocket-1:0.5.3-5.fc42.noarch requires rubygem(http_parser.rb) = 0.8.0 rubygem-em-websocket-1:0.5.3-5.fc42.src requires rubygem(em-http-request) = 1.1.7, rubygem(http_parser.rb) = 0.8.0 rubygem-faraday (maintained by: vondruch) rubygem-faraday-1.0.1-15.fc42.src requires rubygem(em-http-request) = 1.1.7, rubygem(webmock) = 3.23.1 rubygem-webmock (maintained by: @ruby-packagers-sig, tdawson, vondruch) rubygem-webmock-3.23.1-2.fc42.src requires rubygem(em-http-request) = 1.1.7 rubygem-guard-livereload (maintained by: @ruby-packagers-sig, jackorp) rubygem-guard-livereload-2.5.2-18.fc41.noarch requires rubygem(em-websocket) = 0.5.3 rubygem-guard-livereload-2.5.2-18.fc41.src requires rubygem(em-websocket) = 0.5.3 rubygem-jekyll (maintained by: @ruby-packagers-sig, frantisekz, oturpe) rubygem-jekyll-4.3.4-3.fc42.noarch requires rubygem(em-websocket) = 0.5.3 rubygem-jekyll-4.3.4-3.fc42.src requires rubygem(em-websocket) = 0.5.3 rubygem-elasticsearch-transport (maintained by: sbonazzo, stevetraylen) rubygem-elasticsearch-transport-5.0.4-16.fc41.noarch requires rubygem(faraday) = 1.0.1 rubygem-typhoeus (maintained by: @ruby-packagers-sig, jaruga, vondruch) rubygem-typhoeus-1.4.0-12.fc41.src requires rubygem(faraday) = 1.0.1 vagrant-digitalocean (maintained by: kushal) vagrant-digitalocean-0.9.0-18.fc41.noarch requires rubygem-faraday = 1.0.1-15.fc42 alexandria (maintained by: mtasaka) alexandria-0.7.9-9.fc42.src requires rubygem(webmock) = 3.23.1 rubygem-actionmailbox (maintained by: pvalena, vondruch) rubygem-actionmailbox-7.0.8-4.fc41.src requires rubygem(webmock) = 3.23.1 rubygem-codeclimate-test-reporter (maintained by: ilgrad) rubygem-codeclimate-test-reporter-1.0.9-4.fc41.src requires rubygem(webmock) = 3.23.1 rubygem-coveralls (maintained by: tdawson) rubygem-coveralls-0.8.13-23.fc42.src requires rubygem(webmock) = 3.23.1 rubygem-gist (maintained by: gsauthof) rubygem-gist-6.0.0-8.fc41.src requires rubygem(webmock) = 3.23.1 rubygem-httparty (maintained by: valtri, vondruch) rubygem-httparty-0.21.0-5.fc42.src requires rubygem(webmock) = 3.23.1 rubygem-mini_magick (maintained by: pvalena, vondruch) rubygem-mini_magick-4.11.0-11.fc41.src requires rubygem(webmock) = 3.23.1 rubygem-selenium-webdriver (maintained by: @ruby-packagers-sig, vondruch) rubygem-selenium-webdriver-4.1.0-9.fc41.src requires rubygem(webmock) = 3.23.1 rubygem-thor (maintained by: @ruby-packagers-sig, besser82, ignatenkobrain, vondruch) rubygem-thor-1.2.1-8.fc42.src requires rubygem(webmock) = 3.23.1 rubygem-webrobots (maintained by: mtasaka) rubygem-webrobots-0.1.2-20.fc42.src requires rubygem(webmock) = 3.23.1 vagrant (maintained by: @ruby-packagers-sig, humaton, jackorp, pvalena, vondruch) vagrant-2.3.4-6.fc41.src requires rubygem(webmock) = 3.23.1 vagrant-vagrant_cloud (maintained by: jackorp, pvalena) vagrant-vagrant_cloud-3.0.5-7.fc41.src requires rubygem(webmock) = 3.23.1 Too many dependencies for rubygem-http_parser.rb, not all listed here Depending on: rubygem-msgpack (22), status change: 2024-11-23 (1 weeks ago) rubygem-bootsnap (maintained by: pvalena, vondruch) rubygem-bootsnap-1.15.0-9.fc41.src requires rubygem(msgpack) = 1.7.2 rubygem-bootsnap-1.15.0-9.fc41.x86_64 requires rubygem(msgpack) = 1.7.2 rubygem-railties (maintained by: pvalena, tdawson, vondruch) rubygem-railties-7.0.8-6.fc42.src requires rubygem(bootsnap) = 1.15.0 rubygem-actionmailbox (maintained by: pvalena, vondruch) rubygem-actionmailbox-7.0.8-4.fc41.src requires rubygem(railties) = 7.0.8 rubygem-actionpack (maintained by: @ruby-packagers-sig, jaruga, pvalena, vondruch) rubygem-actionpack-1:7.0.8-7.fc42.src requires rubygem(railties) = 7.0.8 rubygem-actiontext (maintained by: pvalena, vondruch) rubygem-actiontext-7.0.8-4.fc41.src requires rubygem(railties) = 7.0.8 rubygem-actionview (maintained by: @ruby-packagers-sig, jaruga, pvalena, vondruch) rubygem-actionview-7.0.8-7.fc42.src requires rubygem(railties) = 7.0.8 rubygem-activemodel (maintained by: pvalena, tdawson, vondruch) rubygem-activemodel-7.0.8-5.fc42.src requires rubygem(railties) = 7.0.8 rubygem-activestorage (maintained by: @ruby-packagers-sig, vondruch) rubygem-activestorage-7.0.8-5.fc42.src requires rubygem(railties) = 7.0.8 rubygem-ammeter (maintained by: @ruby-packagers-sig, vondruch) rubygem-ammeter-1.1.5-8.fc41.noarch requires rubygem(railties) = 7.0.8 rubygem-ammeter-1.1.5-8.fc41.src requires rubygem(railties) = 7.0.8 rubygem-apipie-rails (maintained by: @ruby-packagers-sig, vondruch) rubygem-apipie-rails-0.8.1-7.fc41.src requires rubygem(railties) = 7.0.8 rubygem-generator_spec (maintained by: ilgrad) rubygem-generator_spec-0.10.0-2.fc41.noarch requires rubygem(railties) = 7.0.8 rubygem-generator_spec-0.10.0-2.fc41.src requires rubygem(railties) = 7.0.8 rubygem-globalid (maintained by: @ruby-packagers-sig, jaruga, pvalena, vondruch) rubygem-globalid-1.1.0-5.fc41.src requires rubygem(railties) = 7.0.8 rubygem-haml (maintained by: pvalena, vondruch) rubygem-haml-5.2.2-9.fc41.src requires rubygem(railties) = 7.0.8 rubygem-importmap-rails (maintained by: pvalena, vondruch) rubygem-importmap-rails-1.0.3-8.fc42.noarch requires rubygem(railties) = 7.0.8 rubygem-jbuilder (maintained by: pvalena, vondruch) rubygem-jbuilder-2.11.5-7.fc41.src requires rubygem(railties) = 7.0.8 rubygem-rails (maintained by: @ruby-packagers-sig, mtasaka, pvalena, tdawson, vondruch) rubygem-rails-1:7.0.8-3.fc41.noarch requires rubygem(railties) = 7.0.8 rubygem-rails-controller-testing (maintained by: valtri) rubygem-rails-controller-testing-1.0.5-10.fc41.src requires rubygem(railties) = 7.0.8 rubygem-rspec-rails (maintained by: clalance, vondruch) rubygem-rspec-rails-6.0.3-4.fc41.noarch requires rubygem(railties) = 7.0.8 rubygem-rspec-rails-6.0.3-4.fc41.src requires rubygem(railties) = 7.0.8 rubygem-sassc-rails (maintained by: pvalena, vondruch) rubygem-sassc-rails-2.1.2-11.fc41.noarch requires rubygem(railties) = 7.0.8 rubygem-sassc-rails-2.1.2-11.fc41.src requires rubygem(railties) = 7.0.8 rubygem-slim (maintained by: vondruch) rubygem-slim-5.1.1-3.fc41.src requires rubygem(railties) = 7.0.8 rubygem-sprockets-rails (maintained by: @ruby-packagers-sig, jaruga, pvalena, vondruch) rubygem-sprockets-rails-3.4.2-4.fc41.src requires rubygem(railties) = 7.0.8 rubygem-web-console (maintained by: @ruby-packagers-sig, jaruga, vondruch) rubygem-web-console-4.2.0-5.fc41.noarch requires rubygem(railties) = 7.0.8 rubygem-web-console-4.2.0-5.fc41.src requires rubygem(railties) = 7.0.8 Too many dependencies for rubygem-msgpack, not all listed here Depending on: spirv-llvm-translator11 (1), status change: 2024-11-27 (1 weeks ago) intel-cm-compiler (maintained by: aekoroglu, orphan) intel-cm-compiler-1.0.144-8.20240131gitcc4f5b6.fc41.src requires spirv-llvm-translator11-devel = 11-2.20240131git2e025e4.fc41 intel-cm-compiler-libs-1.0.144-8.20240131gitcc4f5b6.fc41.i686 requires libLLVMSPIRVLib.so.11 intel-cm-compiler-libs-1.0.144-8.20240131gitcc4f5b6.fc41.x86_64 requires libLLVMSPIRVLib.so.11()(64bit) Affected (co)maintainers @abrt-sig: python-pyroute2 @astro-sig: motif @copr-sig: python-pyroute2 @crypto-team: dyninst @dns-sig: http-parser, dyninst @epel-packagers-sig: python-gabbi, python-opentelemetry-propagator-aws-xray, python-pyroute2, python-XStatic-roboto-fontface, python-opentelemetry, python-zake, python-wsgi_intercept, python-opentelemetry-contrib, http-parser, python-fedora @gnome-sig: dyninst @go-sig: golang-github-twpayne-vfs-4, golang-github-containerd-btrfs-2, golang-github-pin-tftp-3, hyprcursor @infra-sig: python-pyroute2, python-fedora @kde-sig: python-opentelemetry-propagator-aws-xray, python-opentelemetry-contrib, http-parser, python-opentelemetry @neuro-sig: mmlib @openstack-sig: python-gabbi, python-XStatic-roboto-fontface, python-zake, python-wsgi_intercept, python-pyghmi @python-packagers-sig: python-pyroute2, python-singledispatch, python-sphinxcontrib-github-alt, dyninst, python-minimock @qa-tools-sig: python-fedora @r-maint-sig: http-parser @ruby-packagers-sig: rubygem-msgpack, rubygem-http_parser.rb, dyninst @rust-sig: rust-eza @scitech_sig: http-parser, motif @sssd-maintainers: dyninst @virtmaint-sig: dyninst abbra: dyninst abrt-team: python-pyroute2 aconole: dyninst adrian: motif aekoroglu: spirv-llvm-translator11, mmlib, intel-llvm-vc-intrinsics11, python-opentelemetry, intel-cm-compiler agerstmayr: dyninst ahughes: dyninst airlied: dyninst ajax: motif, dyninst alexl: dyninst amerey: dyninst anezbeda: dyninst ankursinha: mmlib apevec: python-zake, python-gabbi, python-wsgi_intercept asn: dyninst atikhonov: dyninst avigne: motif belegdol: http-parser berrange: dyninst besser82: rubygem-http_parser.rb bonzini: dyninst bskeggs: dyninst buc: motif cheese: grub-customizer churchyard: python-sphinxcontrib-github-alt, dyninst cicku: http-parser, dyninst, motif clalance: rubygem-msgpack codonell: dyninst corsepiu: motif, dyninst cottsay: dyninst cqi: python-pyroute2, fedscm-admin, python-fedora crobinso: dyninst cstratak: dyninst daandemeyer: dyninst dbelyavs: dyninst dcallagh: python-opentelemetry-propagator-aws-xray, python-opentelemetry-contrib, python-opentelemetry dcavalca: python-pyroute2 divius: python-pyghmi djdelorie: dyninst dmaphy: http-parser dmoerner: motif duck: http-parser edward-evans-aiven: python-opentelemetry-propagator-aws-xray, python-opentelemetry-contrib, python-opentelemetry eharney: python-zake fab: python-pyroute2, golang-github-pin-tftp-3 fberat: dyninst fbl: dyninst fche: dyninst fjanus: dyninst frantisekz: rubygem-http_parser.rb frostyx: python-pyroute2 fujiwara: python-pyroute2 fweimer: dyninst gsauthof: rubygem-http_parser.rb harald: dyninst hguemar: python-XStatic-roboto-fontface, python-fedora hhorak: dyninst hlin: python-fedora hobbes1069: motif humaton: rubygem-http_parser.rb iarnell: dyninst ignatenkobrain: rubygem-http_parser.rb, fedscm-admin, python-fedora ilgrad: rubygem-msgpack, rubygem-http_parser.rb italomga: python-opentelemetry-propagator-aws-xray, python-opentelemetry-contrib, python-opentelemetry jackorp: rubygem-http_parser.rb jakub: dyninst jamatos: python-pyroute2, motif jandrlik: dyninst jaruga: rubygem-msgpack, rubygem-http_parser.rb jcapitao: python-zake jcaratzas: python-singledispatch jcwillia: python-pyroute2 jerboaa: dyninst jexposit: motif, dyninst jfearn: perl-String-Similarity jhnidek: virt-who jirka: python-pyroute2 jistone: dyninst jjames: motif jkurik: dyninst jnovy: motif jonathanspw: python-opentelemetry-propagator-aws-xray, python-sphinxcontrib-github-alt, python-opentelemetry, remmina, python-opentelemetry-contrib jorti: python-pyghmi jorton: dyninst josmyers: dyninst jplesnik: python-pyroute2, dyninst jskarvad: motif, dyninst jstanek: dyninst jsynacek: dyninst jussilehtola: motif jvanek: dyninst kdudka: python-pyroute2 kevin: python-pyroute2, python-fedora kni: dyninst kparal: python-fedora kstewart: dyninst ksurma: dyninst ktdreyer: dyninst kushal: rubygem-http_parser.rb laine: dyninst law: dyninst lberk: dyninst lchilton: dyninst leamas: python-pyroute2 lennart: dyninst libvirt-maint: dyninst limb: python-fedora, fedscm-admin, python-minimock, motif ljavorsk: dyninst lnie: python-pyroute2 lnykryn: dyninst lsedlar: python-pyroute2, python-fedora lslebodn: dyninst lzaoral: python-pyroute2 mattia: motif maxamillion: python-pyroute2 mcascella: dyninst mcermak: motif, dyninst mchehab: motif mclasen: dyninst mcurlej: python-pyroute2 mfabian: dyninst mhayden: python-opentelemetry-propagator-aws-xray, python-opentelemetry, python-opentelemetry-sdk-extension-aws, python-opentelemetry-resource-detector-azure, python-opentelemetry-contrib mhjacks: http-parser michich: dyninst mikem: python-pyroute2 mitr: python-fedora mjeanson: dyninst mjw: dyninst mkyral: python-opentelemetry-propagator-aws-xray, python-opentelemetry-contrib, python-opentelemetry mmarusak: python-pyroute2 mohanboddu: python-pyroute2, fedscm-admin, python-fedora mpolacek: dyninst mrunge: python-XStatic-roboto-fontface, http-parser, nodejs-less mschorm: dyninst msekleta: dyninst mspacek: dyninst msuchy: python-pyroute2 mtasaka: rubygem-msgpack, rubygem-http_parser.rb, dyninst nalimilan: http-parser nalin: dyninst nathans: dyninst neil: http-parser ngompa: python-pyroute2, dyninst nightishaman: hyprcursor ofourdan: dyninst onosek: python-pyroute2 orange-kao: python-opentelemetry-propagator-aws-xray, python-opentelemetry-contrib, python-opentelemetry orion: motif, dyninst oturpe: rubygem-http_parser.rb patches: http-parser, nodejs-less pbrezina: dyninst pemensik: http-parser, dyninst peter: mozjs102 petersen: python-pyroute2 pfrankli: dyninst pingou: python-pyroute2 pmikova: dyninst ppisar: python-pyroute2, dyninst praiskup: python-pyroute2 psabata: dyninst pspacek: dyninst ptoscano: virt-who puiterwijk: python-pyroute2 pvalena: rubygem-msgpack, rubygem-http_parser.rb pwouters: python-opentelemetry-propagator-aws-xray, python-opentelemetry, python-opentelemetry-sdk-extension-aws, python-opentelemetry-resource-detector-azure, python-opentelemetry-contrib pzacik: dyninst qulogic: python-sphinxcontrib-github-alt qwan: python-fedora rdieter: knemo, http-parser, motif rdopiera: python-XStatic-roboto-fontface remi: php-doctrine-common, php-doctrine-persistence, dyninst rhughes: dyninst rjones: dyninst rlandmann: perl-String-Similarity rominf: python-opentelemetry-propagator-aws-xray, python-opentelemetry, python-opentelemetry-sdk-extension-aws, python-opentelemetry-resource-detector-azure, python-opentelemetry-contrib rommell: python-opentelemetry-propagator-aws-xray, python-opentelemetry-contrib, python-opentelemetry rstrode: dyninst salimma: python-pyroute2, http-parser samfeifer: dyninst saprasad: dyninst sbonazzo: rubygem-http_parser.rb sbose: dyninst sgallagh: http-parser, dyninst sharkcz: motif siddhesh: dyninst simo: dyninst siwinski: php-doctrine-persistence spot: motif, dyninst stevetraylen: rubygem-http_parser.rb, motif, python-opentelemetry submachine: dyninst svashisht: python-pyroute2 systemd-maint: dyninst tdawson: rubygem-msgpack, rubygem-http_parser.rb, motif terjeros: motif than: http-parser thrnciar: dyninst tibbs: fedscm-admin, python-fedora tmraz: dyninst topazus: http-parser torsava: dyninst tredaell: dyninst twoerner: motif v02460: python-opentelemetry-propagator-aws-xray, python-opentelemetry-contrib, python-opentelemetry valtri: rubygem-msgpack, rubygem-http_parser.rb vascom: http-parser vondruch: rubygem-msgpack, rubygem-http_parser.rb, dyninst vpv: python-minimock vstinner: dyninst wcohen: dyninst whot: dyninst yuwata: dyninst zbyszek: dyninst zmiklank: dyninst zzambers: dyninst Orphans (77): WoeUSB aprsd aterm caribou0 dyninst fedora-business-cards fedscm-admin fswebcam golang-github-containerd-btrfs-2 golang-github-pin-tftp-3 golang-github-twpayne-vfs-4 grub-customizer http-parser hyprcursor hypridle hyprlock hyprpaper hyprpicker intel-cm-compiler intel-llvm-vc-intrinsics11 ioc-writer java-dirq knemo lecm libdirq mactel-boot mmlib motif mozjs102 nodejs-less perl-Authen-Credential perl-Config-Generator perl-Config-Validator perl-Directory-Queue perl-Messaging-Message perl-Net-STOMP-Client perl-No-Worries perl-String-Similarity php-doctrine-common php-doctrine-persistence python-XStatic-roboto-fontface python-astor python-auth-credential python-bitmath python-fedora python-gabbi python-messaging python-minimock python-opentelemetry python-opentelemetry-contrib python-opentelemetry-propagator-aws-xray python-opentelemetry-resource-detector-azure python-opentelemetry-sdk-extension-aws python-pyghmi python-pyroute2 python-simplevisor python-singledispatch python-sphinxcontrib-github-alt python-tgscheduler python-torchtext python-wsgi_intercept python-zake remmina rubygem-http_parser.rb rubygem-msgpack rubygem-proxifier rubygem-resolve-hostname rust-eza sparse spirv-llvm-translator11 spooky-c stompclt virt-who xastir xdemorse xpsk31 xwrits Orphans (dependend on) (29): dyninst golang-github-pin-tftp-3 http-parser hyprcursor intel-llvm-vc-intrinsics11 mmlib motif mozjs102 perl-Authen-Credential perl-Config-Validator perl-Directory-Queue perl-Messaging-Message perl-Net-STOMP-Client perl-No-Worries perl-String-Similarity php-doctrine-persistence python-fedora python-minimock python-opentelemetry python-opentelemetry-contrib python-opentelemetry-propagator-aws-xray python-pyghmi python-pyroute2 python-sphinxcontrib-github-alt python-wsgi_intercept python-zake rubygem-http_parser.rb rubygem-msgpack spirv-llvm-translator11 Orphans (rawhide) for at least 6 weeks (dependend on) (0): Orphans (rawhide) (not depended on) (48): WoeUSB aprsd aterm caribou0 fedora-business-cards fedscm-admin fswebcam golang-github-containerd-btrfs-2 golang-github-twpayne-vfs-4 grub-customizer hypridle hyprlock hyprpaper hyprpicker intel-cm-compiler ioc-writer java-dirq knemo lecm libdirq mactel-boot nodejs-less perl-Config-Generator php-doctrine-common python-XStatic-roboto-fontface python-astor python-auth-credential python-bitmath python-gabbi python-messaging python-opentelemetry-resource-detector-azure python-opentelemetry-sdk-extension-aws python-simplevisor python-singledispatch python-tgscheduler python-torchtext remmina rubygem-proxifier rubygem-resolve-hostname rust-eza sparse spooky-c stompclt virt-who xastir xdemorse xpsk31 xwrits Orphans (rawhide) for at least 6 weeks (not dependend on) (0): Depending packages (rawhide) (177): AusweisApp2 LabPlot R2spec alexandria alliance bind9-next cantor centos-packager cmake-fedora copr-backend copr-rpmbuild csmock ddd dx eegview erlang-js fbb fbida fbrnch fedora-business-cards fedora-easy-karma fedora-packager fedora-review fedscm-admin flamethrower gcc gcc13 geomview glib2 glibc gobuster gpodder grace hyprland ilua intel-cm-compiler jabberd java-21-openjdk java-latest-openjdk julia koji libmemcached-awesome libvirt libvirt-test-API lttng-tools lttng-ust mariadb10.11 matrix-synapse mesa-libGLw mir mock mock-core-configs module-build nedit netatalk nodejs18 nwg-dock-hyprland oct2spec odcs openssl openvswitch osh pag pcb-rnd pcp perl perl-Authen-Credential perl-Config-Generator perl-Config-Validator perl-Directory-Queue perl-Fedora-Rebuild perl-Messaging-Message perl-Net-STOMP-Client php php-doctrine-annotations php-doctrine-cache php-doctrine-common php-doctrine-datafixtures php-doctrine-doctrine-cache-bundle php-doctrine-persistence php-symfony-polyfill php-symfony4 php-twig plasma-drkonqi polyml postgresql15 postgresql16 postgresql17 publican python-elastic-transport python-elasticsearch python-gabbi python-jupyter-console python-mygpoclient python-opentelemetry-contrib python-opentelemetry-propagator-aws-xray python-opentelemetry-resource-detector-azure python-opentelemetry-sdk-extension-aws python-prawcore python-sentry-sdk python-simplevisor python-taskflow python-virtualbmc python3.10 python3.11 python3.12 python3.13 python3.14 python3.6 python3.8 python3.9 qemu retrace-server rpkg ruby rubygem-actionmailbox rubygem-actionpack rubygem-actiontext rubygem-actionview rubygem-activemodel rubygem-activestorage rubygem-ammeter rubygem-apipie-rails rubygem-bootsnap rubygem-codeclimate-test-reporter rubygem-coveralls rubygem-elasticsearch-transport rubygem-em-http-request rubygem-em-websocket rubygem-faraday rubygem-generator_spec rubygem-gist rubygem-globalid rubygem-guard-livereload rubygem-haml rubygem-httparty rubygem-importmap-rails rubygem-jbuilder rubygem-jekyll rubygem-mini_magick rubygem-rails rubygem-rails-controller-testing rubygem-railties rubygem-rspec-rails rubygem-sassc-rails rubygem-selenium-webdriver rubygem-slim rubygem-sprockets-rails rubygem-thor rubygem-typhoeus rubygem-web-console rubygem-webmock rubygem-webrobots sigul ski slurm sssd stompclt systemd systemtap tcl tito tuned twlog vagrant vagrant-digitalocean vagrant-vagrant_cloud vim-syntastic vtk xastir xawtv xbae xephem xlockmore xmakemol xmbdfed xorg-x11-server Packages depending on packages orphaned (rawhide) for more than 6 weeks (0): Not found in repo (rawhide) (1): caribou0 -- The script creating this output is run and developed by Fedora Release Engineering. Please report issues at its pagure instance: https://pagure.io/releng/ The sources of this script can be found at: https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py Report finished at 2024-12-06 15:05:59 UTC

1 0

Extended Nominations Period for FESCo - Closes Thursday December 5th
by Aoife Moloney 03 Dec '24

03 Dec '24

Hello folks, In order to hold an election for FESCo this cycle, we need more candidates! FESCo has decided to extend the nominations period until Thursday 5th December[1], which means if you or someone you know would like to run for election for FESCo, you now have until 23:23:59 UTC on Thursday 5th December to nominate yourself or someone else[2]. Please make sure you have the permission of the person you wish to nominate before nominating them. If we receive enough candidates to hold an election for FESCo, voting will start on Friday 6th December, as per the elections schedule[3]. If we do not receive enough nominations to hold an election by Thursday December 5th, the current candidates will be automatically elected to FESCo. Kindest regards., Aoife [1] https://pagure.io/fesco/issue/3292 [2] https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations [3] https://fedorapeople.org/groups/schedule/f-41/f-41-elections-tasks.html -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

F42 Change Proposal: Split opendmarc with tools subpackage (Self-Contained)
by Aoife Moloney 03 Dec '24

03 Dec '24

Wiki - https://fedoraproject.org/wiki/Changes/SplitOpendmarcTools Discussion Thread - https://discussion.fedoraproject.org/t/f42-change-proposal-split-opendmarc-… 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 == `opendmarc` package includes some supporting optional binaries that are not required to configure the service. == Owner == * Name: [[User:mikelo2| Mikel Olasagasti]] * Email: mikel(a)olasagasti.info == Detailed Description == `opendmarc` package ships some extra tools that are not required to run the `opendmarc` service. These tools are: * opendmarc-check * opendmarc-expire * opendmarc-import * opendmarc-importstats * opendmarc-params * opendmarc-reports Some of these tools are written in perl and add a lot of dependencies. I created a testing package in copr that I used for testing: * Installing `opendmarc` only: <pre> # dnf install opendmarc Updating and loading repositories: Repositories loaded. Package Arch Version Repository Size Installing: opendmarc x86_64 1.4.2-23.fc42 copr:copr.fedor 179.6 KiB Installing dependencies: libopendmarc x86_64 1.4.2-23.fc42 copr:copr.fedor 54.6 KiB libspf2 x86_64 1.2.11-15.20210922git49 rawhide 153.4 KiB sendmail-milter x86_64 8.18.1-4.fc41 rawhide 77.0 KiB Transaction Summary: Installing: 4 packages Total size of inbound packages is 220 KiB. Need to download 220 KiB. After this operation, 465 KiB extra will be used (install 465 KiB, remove 0 B). </pre> * Installing `opendmarc-tools`: <pre> # dnf install opendmarc-tools Updating and loading repositories: Repositories loaded. Package Arch Version Repository Size Installing: opendmarc-tools x86_64 1.4.2-23.fc42 copr:copr.f 76.3 KiB Installing dependencies: groff-base x86_64 1.23.0-7.fc41 rawhide 3.8 MiB libopendmarc x86_64 1.4.2-23.fc42 copr:copr.f 54.6 KiB libspf2 x86_64 1.2.11-15.20210922git49 rawhide 153.4 KiB mailcap noarch 2.1.54-7.fc41 rawhide 86.0 KiB mariadb-connector-c-config noarch 3.4.3-1.fc42 rawhide 497.0 B mysql-common noarch 8.0.40-1.fc42 rawhide 442.2 KiB mysql-libs x86_64 8.0.40-1.fc42 rawhide 6.4 MiB ncurses x86_64 6.5-2.20240629.fc41 rawhide 627.3 KiB perl-AutoLoader noarch 5.74-512.fc42 rawhide 20.5 KiB perl-B x86_64 1.89-512.fc42 rawhide 498.0 KiB perl-Carp noarch 1.54-511.fc41 rawhide 46.6 KiB perl-Class-Struct noarch 0.68-512.fc42 rawhide 25.4 KiB perl-Clone x86_64 0.47-1.fc42 rawhide 36.5 KiB perl-Compress-Raw-Bzip2 x86_64 2.213-1.fc42 rawhide 71.4 KiB perl-Compress-Raw-Zlib x86_64 2.213-1.fc42 rawhide 163.3 KiB perl-DBD-MySQL x86_64 5.010-1.fc42 rawhide 353.9 KiB perl-DBI x86_64 1.645-1.fc42 rawhide 2.2 MiB perl-Data-Dumper x86_64 2.189-512.fc41 rawhide 111.7 KiB perl-Digest noarch 1.20-511.fc41 rawhide 35.3 KiB perl-Digest-MD5 x86_64 2.59-5.fc41 rawhide 59.8 KiB perl-DynaLoader x86_64 1.56-512.fc42 rawhide 32.1 KiB perl-Encode x86_64 4:3.21-511.fc41 rawhide 4.7 MiB perl-Encode-Locale noarch 1.05-30.fc41 rawhide 19.0 KiB perl-Errno x86_64 1.38-512.fc42 rawhide 8.4 KiB perl-Exporter noarch 5.78-511.fc41 rawhide 54.3 KiB perl-Fcntl x86_64 1.18-512.fc42 rawhide 49.0 KiB perl-File-Basename noarch 2.86-512.fc42 rawhide 14.0 KiB perl-File-Path noarch 2.18-511.fc41 rawhide 63.5 KiB perl-File-Slurper noarch 0.014-6.fc41 rawhide 28.7 KiB perl-File-Temp noarch 1:0.231.100-511.fc41 rawhide 162.3 KiB perl-File-stat noarch 1.14-512.fc42 rawhide 12.5 KiB perl-FileHandle noarch 2.05-512.fc42 rawhide 9.3 KiB perl-Filter x86_64 2:1.64-512.fc41 rawhide 165.2 KiB perl-Getopt-Long noarch 1:2.58-2.fc41 rawhide 144.5 KiB perl-Getopt-Std noarch 1.14-512.fc42 rawhide 11.2 KiB perl-HTTP-Date noarch 6.06-5.fc41 rawhide 41.2 KiB perl-HTTP-Message noarch 7.00-1.fc42 rawhide 215.3 KiB perl-HTTP-Tiny noarch 0.090-1.fc42 rawhide 154.4 KiB perl-I18N-Langinfo x86_64 0.24-512.fc42 rawhide 38.8 KiB perl-IO x86_64 1.55-512.fc42 rawhide 151.1 KiB perl-IO-Compress noarch 2.213-2.fc42 rawhide 1.0 MiB perl-IO-HTML noarch 1.004-13.fc41 rawhide 45.2 KiB perl-IO-Socket-IP noarch 0.43-1.fc42 rawhide 100.3 KiB perl-IO-Socket-SSL noarch 2.089-1.fc42 rawhide 703.3 KiB perl-IPC-Open3 noarch 1.22-512.fc42 rawhide 22.5 KiB perl-JSON noarch 4.10-6.fc41 rawhide 270.5 KiB perl-LWP-MediaTypes noarch 6.04-19.fc41 rawhide 79.0 KiB perl-MIME-Base32 noarch 1.303-21.fc41 rawhide 30.7 KiB perl-MIME-Base64 x86_64 3.16-511.fc41 rawhide 46.1 KiB perl-Math-BigInt noarch 1:2.0030.03-3.fc41 rawhide 957.7 KiB perl-Math-Complex noarch 1.62-512.fc42 rawhide 85.0 KiB perl-Net-SSLeay x86_64 1.94-7.fc41 rawhide 1.3 MiB perl-POSIX x86_64 2.20-512.fc42 rawhide 235.1 KiB perl-PathTools x86_64 3.91-511.fc41 rawhide 180.0 KiB perl-Pod-Escapes noarch 1:1.07-511.fc41 rawhide 24.9 KiB perl-Pod-Perldoc noarch 3.28.01-512.fc41 rawhide 163.7 KiB perl-Pod-Simple noarch 1:3.45-511.fc41 rawhide 560.9 KiB perl-Pod-Usage noarch 4:2.03-511.fc41 rawhide 84.8 KiB perl-Scalar-List-Utils x86_64 5:1.68-1.fc42 rawhide 148.9 KiB perl-SelectSaver noarch 1.02-512.fc42 rawhide 2.2 KiB perl-Socket x86_64 4:2.038-511.fc41 rawhide 124.0 KiB perl-Storable x86_64 1:3.32-511.fc41 rawhide 232.4 KiB perl-Switch noarch 2.17-31.fc41 rawhide 38.5 KiB perl-Symbol noarch 1.09-512.fc42 rawhide 6.8 KiB perl-Term-ANSIColor noarch 5.01-512.fc41 rawhide 97.5 KiB perl-Term-Cap noarch 1.18-511.fc41 rawhide 29.3 KiB perl-Text-Balanced noarch 2.06-511.fc41 rawhide 111.4 KiB perl-Text-ParseWords noarch 3.31-511.fc41 rawhide 13.6 KiB perl-Text-Tabs+Wrap noarch 2024.001-511.fc41 rawhide 22.6 KiB perl-Time-HiRes x86_64 4:1.9777-511.fc41 rawhide 119.9 KiB perl-Time-Local noarch 2:1.350-511.fc41 rawhide 69.0 KiB perl-TimeDate noarch 1:2.33-15.fc41 rawhide 95.2 KiB perl-URI noarch 5.31-1.fc42 rawhide 257.0 KiB perl-base noarch 2.27-512.fc42 rawhide 12.5 KiB perl-constant noarch 1.33-512.fc41 rawhide 26.2 KiB perl-deprecate noarch 0.04-512.fc42 rawhide 6.5 KiB perl-if noarch 0.61.000-512.fc42 rawhide 5.8 KiB perl-interpreter x86_64 4:5.40.0-512.fc42 rawhide 122.3 KiB perl-libnet noarch 3.15-512.fc41 rawhide 289.4 KiB perl-libs x86_64 4:5.40.0-512.fc42 rawhide 9.9 MiB perl-locale noarch 1.12-512.fc42 rawhide 6.5 KiB perl-mro x86_64 1.29-512.fc42 rawhide 45.6 KiB perl-overload noarch 1.37-512.fc42 rawhide 71.5 KiB perl-overloading noarch 0.02-512.fc42 rawhide 4.8 KiB perl-parent noarch 1:0.243-1.fc42 rawhide 10.2 KiB perl-podlators noarch 1:6.0.2-2.fc41 rawhide 317.5 KiB perl-vars noarch 1.05-512.fc42 rawhide 3.9 KiB Installing weak dependencies: perl-IO-Compress-Brotli x86_64 0.004001-14.fc41 rawhide 36.1 KiB perl-NDBM_File x86_64 1.17-512.fc42 rawhide 32.5 KiB perl-PerlIO-utf8_strict x86_64 0.010-8.fc41 rawhide 42.0 KiB Transaction Summary: Installing: 91 packages Total size of inbound packages is 12 MiB. Need to download 12 MiB. After this operation, 39 MiB extra will be used (install 39 MiB, remove 0 B). </pre> As some sysadmin could be depending on the extra tools, I would like to limit the change to only new Fedora versions and later update to EPEL. `opendmarc` package would have a `Suggest` on `%{name}-tools%{?_isa} = %{version}-%{release}` == Feedback == == Benefit to Fedora == Reducing in ~90 packages the installation of opendmarc for those users that don't want to use the extra tools that are mainly for reporting. == Scope == * Proposal owners: * Other developers: * Release engineering: [https://pagure.io/releng/issues #Releng issue number] * 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 == == How To Test == == User Experience == `opendmarc` users that don't require reporting tools can remove up to 89 dependencies. == Dependencies == == Contingency Plan == * Contingency mechanism: N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == N/A (not a System Wide Change) == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

F42 Change Proposal: Replace SDL 2 with sdl2-compat using SDL 3 (self-contained)
by Aoife Moloney 03 Dec '24

03 Dec '24

Wiki - https://fedoraproject.org/wiki/Changes/SDL2onSDL3 Discussion Thread - https://discussion.fedoraproject.org/t/f42-change-proposal-replace-sdl-2-wi… 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 == This Change proposes to replace SDL 2 with sdl2-compat, which uses SDL 3. == Owner == * Name: [[User:Ngompa| Neal Gompa]] * Email: ngompa13(a)gmail.com == Detailed Description == SDL 2 feature development ended some time ago with efforts being focused on SDL 3. However, many older games still use SDL 2 and cannot change to SDL 3. In order to continue to support SDL 2 games in the modern world, let's replace SDL 2 with sdl2-compat, which uses SDL 3. This also has the effect of moving SDL 1.2 games to SDL3 through sdl12-compat running on sdl2-compat. == Feedback == == Benefit to Fedora == Switching SDL 2 powered games to use <code>sdl2-compat</code> ensures that SDL-based applications continue to use the actively developed codebase. This also has the effect of SDL 1.2 powered games that use <code>sdl12-compat</code> to run on SDL3 as well through the fully supported path of <code>sdl12-compat</code> running on <code>sdl2-compat</code> running on SDL3. == Scope == * Proposal owners: ** Package [https://github.com/libsdl-org/sdl2-compat libsdl2-compat] (native: [https://bugzilla.redhat.com/2316576 RH#2316576], mingw: [https://bugzilla.redhat.com/2330101 RH#2330101]) ** Retire {{package|SDL2}} and {{package|mingw-SDL2}} completely * Other developers: * Release engineering: [https://pagure.io/releng/issue/12485 #12485] * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with the Fedora Strategy: N/A == Upgrade/compatibility impact == The <code>SDL2</code> package would be transparently upgraded to <code>libsdl2-compat</code> package and games using it should just transparently start using SDL 3.0. == How To Test == The testing steps are simple: 0. Enable the [https://copr.fedorainfracloud.org/coprs/ngompa/SDL2onSDL3/ <code>SDL2onSDL3</code> COPR]: <code>dnf copr enable ngompa/SDL2onSDL3</code> 1. Swap <code>SDL2</code> for <code>sdl2-compat</code>: <code>dnf swap SDL2 sdl2-compat</code> 2. Run something that uses SDL 2 like {{package|supertuxkart}} and see that it works. 3. Run something that uses SDL 1.2 like {{package|icebreaker}} and see that it works. Issues should be reported upstream for the fastest response: https://github.com/libsdl-org/sdl2-compat/issues  == User Experience == There shouldn't be a noticeable user impact, other than possibly a smoother experience because applications are using SDL 3.0. == Dependencies == == Contingency Plan == * Contingency mechanism: Revert back to shipping SDL2 / mingw-SDL2 packages * Contingency deadline: Final Freeze * Blocks release? N/A (not a System Wide Change) == Documentation == N/A (not a System Wide Change) == Release Notes == Applications that use SDL 2 will now transparently use SDL 3 through the <code>sdl2-compat</code> package. This makes it so applications that historically used SDL 2 now use SDL 3. -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

F42 Change Proposal: Ruby 3.4 (System-Wide)
by Aoife Moloney 03 Dec '24

03 Dec '24

Wiki - https://fedoraproject.org/wiki/Changes/Ruby_3.4 Discussion Thread - https://discussion.fedoraproject.org/t/f42-change-proposal-ruby-3-4-system-… 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 == Ruby 3.4 is the latest stable version of Ruby. Many new features and improvements are included for the increasingly diverse and expanding demands for Ruby. With this major update from Ruby 3.3 in Fedora 41 to Ruby 3.4 in Fedora 42, Fedora becomes the superior Ruby development platform. == Owner == * Name: [[User:vondruch| Vít Ondruch]] * Email: vondruch(a)redhat.com * Name: [[User:mtasaka| Mamoru Tasaka]] * Email: mtasaka(a)fedoraproject.org == Detailed Description == Ruby 3.4 is upstream's new major release of Ruby. Many new features and improvements are included. === Prism === Switch the default parser from parse.y to Prism to improve maintainability, error tolerance, portability, and performance. === Language changes === * String literals in files without a `frozen_string_literal` comment now emit a deprecation warning when they are mutated. * `it` is added to reference a block parameter. * Keyword splatting `nil` when calling methods is now supported.`**nil` is treated similarly to `**{}`, passing no keywords, and not calling any conversion methods. * Block passing is no longer allowed in index. * Keyword arguments are no longer allowed in index.#20218]] === Core classes updates === * Exception ** `Exception#set_backtrace` now accepts an array of `Thread::Backtrace::Location`. `Kernel#raise`, `Thread#raise` and `Fiber#raise` also accept this new format. * Range ** `Range#size` now raises `TypeError` if the range is not iterable. === Compatibility issues === * Error messages and backtrace displays have been changed. ** Use a single quote instead of a backtick as a opening quote. ** Display a class name before a method name (only when the class has a permanent name). ** `Kernel#caller`, `Thread::Backtrace::Location`'s methods, etc. are also changed accordingly. * `Hash#inspect` rendering has changed. ** Symbol keys are displayed using the modern symbol key syntax: `"{user: 1}"` ** Other keys now have spaces around `=>`: `'{"user" => 1}'`, while previously they didn't: `'{"user"=>1}'` === C API updates === * `rb_newobj` and `rb_newobj_of` (and corresponding macros `RB_NEWOBJ`, `RB_NEWOBJ_OF`, `NEWOBJ`, `NEWOBJ_OF`) have been removed. * Removed deprecated function `rb_gc_force_recycle`. === Implementation improvements === * `Array#each` is rewritten in Ruby for better performance. === Miscellaneous changes === * Passing a block to a method which doesn't use the passed block will show a warning on verbose mode (`-w`). * Redefining some core methods that are specially optimized by the interpeter and JIT like `String.freeze` or `Integer#+` now emits a performance class warning (`-W:performance` or `Warning[:performance] = true`). == Feedback == == Benefit to Fedora == With a latest release, Ruby language is supporting the newest language features, which enables even faster and easier development of Ruby applications. == Scope == * Proposal owners: ** Finish packaging of Ruby 3.4. Current changes available in PR https://src.fedoraproject.org/rpms/ruby/pull-request/196 ** Rebuilding of Ruby packages providing native extensions (i.e. packages which depends on libruby). * Other developers: ** Rebuild of packages with binary extensions (i.e. packages which depends on libruby) will be handled automatically, but some packages might need fixes/updates to support Ruby 3.4 properly. * Release engineering: [https://pagure.io/releng/issue/12469 #12469] ** The packages are going to be rebuild in side-tag, but that does not need releng involvement nowadays. * 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 == * User specific Ruby binary extensions need to be rebuild. * Adjustments to new language features will be needed. * Ruby packages/application dependencies might need to be adjusted if newly bundled gems are used. == Early Testing (Optional) == Do you require 'QA Blueprint' support? No == How To Test == == User Experience == The Ruby programs/scripts should behave as they were used to. == Dependencies == <pre> $ dnf repoquery --disablerepo=* --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' | sort | uniq | wc -l 122 </pre> == Contingency Plan == * Contingency mechanism: We would like to get a special buildroot tag to be able to rebuild necessary the packages with Ruby 3.4. If anything goes wrong, the tag could be easily dropped and previous version of Ruby 3.3 and its dependencies stays intact. The tag would be merged into F42 after everything is rebuild. * Contingency deadline: Mass Rebuild * Blocks release? No == Documentation == * [http://www.ruby-doc.org/ Help and documentation for the Ruby programming language] * [https://github.com/ruby/ruby/blob/ruby_3_4/NEWS.md Ruby 3.4.0 NEWS] * [https://www.ruby-lang.org/en/news/2024/10/07/ruby-3-4-0-preview2-released/ Ruby 3.4.0 preview2 release announcement] == Release Notes == * The Ruby 3.4 bumps soname, therefore Ruby packages, which use binary extensions, should be rebuilt. Nevertheless, since upstream paid great attention to source compatibility, no changes to your code are needed. https://github.com/ruby/ruby/blob/ruby_3_4/NEWS.md -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

F42 Change Proposal: Remove fips-mode-setup (system-wide)
by Aoife Moloney 03 Dec '24

03 Dec '24

Wiki - https://fedoraproject.org/wiki/Changes/RemoveFipsModeSetup Discussion Thread - https://discussion.fedoraproject.org/t/f42-change-proposal-remove-fips-mode… 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 == Remove the `fips-mode-setup` command provided by the `crypto-policies` package. The functionality it currently performs will be partially removed, partially replaced by automation. == Owner == * Name: Clemens Lang * Email: cllang(a)redhat.com == Detailed Description == `fips-mode-setup` in the `crypto-policies` package is currently used to switch Fedora systems into FIPS mode. FIPS mode is designed to change cryptographic components in Fedora (the kernel's crypto API, OpenSSL, NSS, GnuTLS, and libgcrypt) to comply with the United States [https://en.wikipedia.org/wiki/FIPS_140 Federal Information Processing Standards requirements for cryptographic modules, better known as FIPS 140]. We propose removing this utility. Instead, systems should be placed into FIPS mode using one of the following methods: * Pass `fips=1` on the kernel command line of the Anaconda installer (i.e., install in FIPS mode) * Use the `osbuild-composer` image build functionality with the <pre>[customizations]\n fips=true</pre> customization to build an image in FIPS mode * Use `bootc` as documented at https://gitlab.com/fedora/bootc/examples/-/tree/main/fips This will remove all tooling to switching in and out of FIPS mode after installation. Switching after installation is a bad idea anyway, see below for the rationale. Switching out of FIPS mode without reinstalling does not make sense from a compliance point of view. === Context information on FIPS === For compliance with these standards, the cryptographic modules must be submitted to the [https://csrc.nist.gov/Projects/Cryptographic-Module-Validation-Program Cryptographic Module Validation Program] run by the US National Institute of Standards and Technology. Such certifications are lengthy efforts involving a company accredited to perform review and testing before submission, the so-called Cryptographic and Security Testing Laboratories (CSTLs). It takes upwards of a year to receive a certification, and costs a mid five-figure sum per CPU architecture to do this. Due to lack of funding and the fast pace of Fedora, Fedora's modules are not submitted. As a consequence, FIPS mode on Fedora is useful for testing only. Several distributions downstream of Fedora (RHEL, AlmaLinux, Oracle Linux, Amazon Linux), perform their own FIPS validations. Occasionally, users think that enabling FIPS mode improves security. While running in FIPS mode does enable some additional checks and disables some older algorithms, we see FIPS mode as a compliance tool, not as a security tool. In some situations, enabling FIPS mode actually '''decreases''' security: for example, LUKS disk encryption normally uses the modern GPU-resistant Argon2 key derivation function, but because it is not FIPS-approved, it falls back to the older and generally considered weaker PBKDF2 in FIPS mode. FIPS mode also does not allow the use of Curve25519 for key exchange (used by default in TLS 1.3), or the ChaCha20-Poly1305 authenticated encryption algorithm (again, used in TLS 1.3) both of which are considered modern and good. We do not recommend running FIPS mode to "improve security". A well-configured crypto policy is a much better tool to limit the use of legacy algorithms without the side effect of disabling newer non-US-specified algorithms. === Why remove `fips-mode-setup`? === To correctly switch a system to FIPS mode, multiple knobs need to be adjusted: * The system-wide cryptographic policy needs to be `FIPS` or based on it * The `fips` dracut initramfs module needs to be enabled to run an integrity test (a FIPS 140 requirement) on the kernel image, followed by re-generating the initramfs * The kernel command line needs to contain `fips=1` to switch the kernel to FIPS mode (which also enables a slower FIPS-compliant DRBG) * If `/boot` is on a separate partition, a `boot=UUID=<uuid-of-boot-partition>` flag needs to be added to the kernel command line for the `fips` dracut initramfs module to be able to find the expected message authentication code for the kernel binary. This process is somewhat brittle due to the number of different changes that need to be made. Additionally, `fips-mode-setup --disable`, which only exists for testing purposes because the compliance requirements do not support switching systems out of FIPS mode, does not undo adding the `fips` module to the initramfs to avoid a risk that the system will no longer boot afterwards. `fips-mode-setup --check` subsequently reports an inconsistent configuration, which is frequently confusing users. This user confusion is one of the reasons why we propose to remove this tool. Instead, we will turn the `fips=1` kernel command line flag into the single source of truth for whether FIPS mode is enabled. We have already removed or will remove some of the separate knobs and instead automate them to follow the single source of truth: * The system-wide cryptographic policy will automatically follow the `fips=1` kernel command line flag to remove the need for the manual switch previously performed by `fips-mode-setup`. This is [https://github.com/dracut-ng/dracut-ng/tree/main/modules.d/01fips-crypto-po… already implemented by a dracut module], which will add two bind-mounts before pivoting to the root filesystem if the system is in FIPS mode, but the crypto-policy is not. * For systems that are not started using dracut (e.g., containers with systemd), the `crypto-policies` package ships `fips-crypto-policy-overlay.service`, which runs early during boot and also applies these bind mounts. See https://bugzilla.redhat.com/show_bug.cgi?id=2325499. This change is independent of this change proposal, and we will pursue this regardless of whether the community agrees that this change is a good idea, since it does make sense as a separate incremental improvement. * Containers started using `podman` on hosts in FIPS mode did already create these bind mounts, but we are also modernizing that, see [https://github.com/containers/common/issues/2130 containers/common#2130] and [https://github.com/containers/common/pull/2174 containers/common#2174]. * The `crypto-policies` package has been adjusted to detect and handle this situation during upgrades and when `update-crypto-policies --set` is called manually. This also improves the behavior of `update-crypto-policies --set` in containers in FIPS mode, which was a lot more brittle before. * We will enable the dracut `fips` module on all systems. This is required for unified kernel images anyway. The `fips` dracut module does nothing if the system is not in FIPS mode (i.e., `fips=1` is not on the kernel command line). The other big reason for removing `fips-mode-setup` is that it allows switching to FIPS mode after installation, which means that certain algorithmic choices have already been made. For example, `cryptsetup` will use PBKDF2 as key derivation function in FIPS setup, but Argon2 otherwise. A system with LUKS disk encryption initially set up outside of FIPS mode but switched into FIPS mode later using `fips-mode-setup` would end up in one of two states: either, non-compliant due to the use of Argon2, or unbootable in case the cryptographic library refuses the attempt to use Argon2. OpenSSH is also affected during installation or first system boot with its hostkey algorithm choices. Additionally, even keys that would be usable in FIPS mode must be considered tainted on systems switched to FIPS mode after installation, because key generation behaves different in FIPS mode (e.g., all RSA keys would have to be thrown away and re-generated). For these reasons, we have come to the conclusion that the only sane way to create a system in FIPS mode, is to install it in FIPS mode. `fips-mode-setup` is therefore actively harmful. == Feedback == Users that do not care about compliance but only run Fedora in FIPS mode for testing may not want to reinstall from scratch just for that purpose. For these cases, and when the above limitations are well understood, the `fips=1` kernel command line flag can be modified directly, e.g. using <pre>grubby --update-kernel=ALL --args="fips=1 boot=UUID=$(blkid --output value --match-tag UUID "$(findmnt --first --noheadings -o SOURCE /boot)")"</pre> The `boot=UUID=<partition-uuid>` part of this command is only required if `/boot` is a separate partition, because the `fips` dracut initramfs module will otherwise not be able to locate the message authentication code to verify the integrity of the kernel image. Users that do not care about compliance that want to switch systems out of FIPS mode can equally use grubby to remove the `fips=1` kernel command line flag. == Benefit to Fedora == * Upstream testing on systems in FIPS mode will use consistent algorithm choices everywhere. * Misconfigurations such as the use of the Argon2 key derivation function for LUKS disk encryption in FIPS mode will be reduced. * Misconfigurations such as the use of a non-FIPS system-wide cryptographic policy in FIPS mode will automatically be avoided * Maintenance for `fips-mode-setup` can be stopped, freeing up resources for other changes == Scope == * Proposal owners: Most of the changes mentioned above are incremental improvements that made sense on their own and have already landed. Removal of the `fips-mode-setup` tool is the remaining step that could not be done without a change proposal and TBD. * Other developers: No further changes are expected from other developers. From a user point of view, FIPS mode will continue to work as it did before. The only change is on how to enable FIPS mode. The anaconda installer that used to invoke `fips-mode-setup` has already been changed to call `/usr/libexec/fips-setup-helper` provided by the `crypto-policies` package instead. * Release engineering: [https://pagure.io/releng/issue/12472 #12472] * Policies and guidelines: not needed for this Change * Trademark approval: not needed for this Change * Alignment with the Fedora Strategy: This simplifies the ecosystem connections because it reduces the number of downstream changes. == Upgrade/compatibility impact == Systems in FIPS mode that were configured to not use the FIPS system-wide cryptographic policy will see their policy automatically be changed to FIPS mode. Running in FIPS mode with a non-FIPS crypto-policy is considered a misconfiguration. Scripts that used `fips-mode-setup` will stop working after the upgrade. == Early Testing (Optional) == Do you require 'QA Blueprint' support? No == How To Test == Testers that will try the three methods outlined above to switch to FIPS mode are welcome. From downstream testing, we expect no issues. Using `dnf reinstall crypto-policies` on a system that has the two bind-mounts for the FIPS crypto-policy (i.e., that's in FIPS mode but its crypto-policy was not manually switched to `FIPS`) should pass without issue, and the files in `/etc/crypto-policies/back-ends` should correspond to those in `/usr/share/crypto-policies/back-ends/FIPS`. We also expect no issues here from downstream testing. Testers that run Fedora containers with systemd on hosts in FIPS mode (i.e., `/proc/sys/crypto/fips_enabled` contains `1`) both with `podman` and with other container runtimes are very welcome. == User Experience == Users will notice that `fips-mode-setup` no longer exists. Users that want to switch systems to FIPS mode need to follow different steps. At the same time, switching to FIPS mode now comes with fewer pitfalls and fewer possibilities for misconfigurations and inconsistencies. == Dependencies == The following packages have already adapted to this potential change and will continue to work: * `anaconda` * `dracut` * `podman` * `crypto-policies` (in particular `update-crypto-policies` and the package `%pre` and `%post` scriptlets) == Contingency Plan == * Contingency mechanism: We will keep `fips-mode-setup` and try again next release * Contingency deadline: beta freeze (or even later, if required) * Blocks release? No == Documentation == * https://github.com/dracut-ng/dracut-ng/pull/576 * https://github.com/containers/common/issues/2130 * https://github.com/containers/common/pull/2174 * https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/merge_requests/205 == Release Notes == The `fips-mode-setup` command that could be used to switch systems to FIPS mode after installation has been removed. Switching to FIPS mode after installation has subtle bugs and is no longer recommended. To switch systems to FIPS mode, * add `fips=1` to the kernel command line of the installer * use `osbuild-composer` with the following customization to build a FIPS-enabled image: [customizations] fips = true * use `bootc` and add the `fips=1` kernel command line flag in your `Containerfile` as documented in the example at https://gitlab.com/fedora/bootc/examples/-/tree/main/fips To disable FIPS mode, re-install your system without enabling FIPS mode. Disabling FIPS mode without reinstalling does not make sense from a compliance point of view. -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

F42 Change Proposal: Intel SGX Software Stack (Self-Contained)
by Aoife Moloney 03 Dec '24

03 Dec '24

Wiki - https://fedoraproject.org/wiki/Changes/IntelSGX Discussion Thread - https://discussion.fedoraproject.org/t/f42-change-proposal-intel-sgx-softwa… 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 == The Intel SGX technology enables creation of execution enclaves, whose memory is encrypted and thus protected from all other code running on the CPU, including SMM, firmware, kernel and userspace. This proposal is to introduce the SGX host software stack, architectural enclaves and development packages to Fedora, to enable future introduction applications and features which have a dependency on SGX technology. The primary feature that will leverage SGX in a subsequent Fedora release is expected to be Intel TDX, which provides confidential virtual machines, and is in the process of being integrated with QEMU and Linux/KVM. == Owner == * Name: [[User:berrange| Daniel Berrange]] * Email: berrange(a)redhat.com == Detailed Description == The Intel SGX technology enables creation of execution enclaves, whose memory is encrypted and thus protected from all other code running on the machine, including SMM, firmware, kernel and userspace. While it has many potential use cases, this proposal is focused around the infrastructure needed to enable support for attestation of TDX confidential virtual machines. The SGX software stack that is to be introduced can be categorized into a number of distinct areas: * Support for developing new enclaves ** Header files for the enclave code (a minimalist C library, C++ library, crypto and some other misc libraries) ** Static library archives for linking into the enclave binaries. ** Build helper tools (for signing enclaves, generating code enclave API entrypoints) * Support for developing applications that use enclaves, eg to be able to load and communicate with enclaves. ** Header files for platform code ** Dynamic libraries for platform code * Support for deploying applications that use enclaves ** Enclave service daemon - assists unprivileged applications in loading enclaves ** Registration tools - assists platform administrator in acquiring certificates from Intel servers to identity the platform ** Quote generation daemon - assists QEMU in acquiring signed attestation reports for TDX VMs. The code and binaries related to the host OS platform components will be installed in the normal filesystem locations common to all Fedora packages. e.g. libraries in '''/usr/lib64''', headers in '''/usr/include''' and binaries in '''/usr/bin'''. For the purposes of packaging, the enclaves will be [https://fedoraproject.org/wiki/Virt/SGXEnclaves#Enclaves_as_a_platform_buil… treated as cross-compilation target]. While the compiler build architecture target is '''x86_64''', the runtime has custom C / C++ libraries that must be used, and requires a separate code loader, all completely separate from any existing Fedora libraries. Enclaves cannot be directly linked to applications, they are strictly independent & self-contained ELF binaries. With this in mind, following the example of MinGW64 packages living under '''/usr/x86_64-w64-mingw''', all enclave related headers and libraries are proposed to be placed under '''/usr/x86_64-intel-sgx''', specifically the '''lib64''' and '''include''' sub-directories. There is no concept of executable binaries for enclaves, only libraries, nor ancillary data files. Thus no '''bin''' or '''share''' directories are required under this location. The installation tree locations will be defined in RPM macros provided by the '''sgx-srpm-macros''' package The generated binary packages will generally all have an ''sgx-'' prefix to their name, with those containing exclusively enclave related content having the more specialized ''sgx-enclave-'' name prefix. For reasons of brevity, this change proposal does not go far into all technical details of SGX. For a deeper understanding of SGX enclaves beyond this proposal, [https://fedoraproject.org/wiki/Virt/SGXEnclaves consult this companion document]. == Feedback == * '''Feedback:''' ''The SGX technology can be used as a way to implement DRM. Notable example has been BluRay playback.''. '''Answer:''' As with many technologies, it is possible to use SGX in ways that are both positive and negative, wrt the owner / users of a machine. Use of SGX for DRM in BluRay playback is hostile to the owner/user of a machine. This change is '''NOT''' proposing to introduce / support any such usage/applications in Fedora. The fact that bad uses of SGX may exist outside of Fedora, is no justification for rejecting the use of SGX in Fedora when applied to scenarios that can offer features directly benefiting Fedora's users. * '''Feedback:''' ''The SGX enclave code is not open source, because it requires a vendor signature on output binaries''. '''Answer:''' All of the SGX code is made available under a variety open source licenses (Apache, BSD, MIT, GPL & more), which are fully approved by Fedora. One of the architectural enclaves, '''pce''', requires an Intel signature because it is used to establish the root of trust with the hardware. In their role of bootstrapping use of SGX hardware, the architectural enclaves are a type of firmware, and it is normal for firmware to have a vendor signature. In contrast to almost all firmware which is proprietary, the architectural enclave code is all under Fedora approved OSS licenses. All of the architectural enclaves, can be rebuilt from source by a user, with customizations, signed with a user specified key and then loaded if desired. There are some subtle limitations if attempting this, documented in [[Virt/SGXEnclaves#Rebuilding_&_self-signing_architectural_enclaves | the companion document]], but the code is none the less all OSS. == Benefit to Fedora == As a general purpose infrastructure technology, SGX can be applied to / used by a wide variety of scenarios / applications. In the context of this change proposal, '''no application''' usage is intended to be introduced, the focus is around general software infrastructure enablement. A followup change proposal (for a subsequent Fedora release) will be made to introduce Intel TDX confidential virtual machines, which is anticipated to be the first end user facing application of SGX technology. Attestation is the means by which a guest VM owner can prove that their VM machine is running in confidential mode on genuine Intel hardware, as opposed to in a faked "blue pill" environment. All currently shipping Intel CPUs which support TDX build attestation on top of SGX with OSS enclave code (the '''tdqe''' enclave), as opposed to embedding attestation in proprietary firmware which is the approach taken by other vendors for confidential computing. NB, the '''tdqe''' enclave and '''qgs''' daemon will be included in this proposal, but will remain unused until this followup TDX support is integrated with Fedora. It is well known that SGX technology can be applied is to build DRM systems which allow 3rd party organizations to control what users do with their machines. This proposal '''MUST NOT''' be interpreted as endorsing such use cases. Such DRM systems would almost certainly rely on close source enclaves signed exclusively by a 3rd party org, and could not be considered hardware enablement firmware. As such they would not be eligible for inclusion in Fedora. == Scope == === Proposal owners=== The proposal owners will be introducing a number of new packages to Fedora. Initially, no existing packages are likely to gain dependencies on the new SGX packages. At a future date when TDX is integrated into Fedora, one or more of the libvirt/qemu sub-RPMs may gain a dependency on certain SGX packages needed to support TDX. The important new packages will be * '''sgx-srpm-macros''': this will produce a binary RPM of the same name, containing RPM macros that define the directory locations for SGX enclaves under '''/usr/x86_64-intel-sgx'''. These macros will be consumed by other RPMs that deal with enclave pacakging * '''linux-sgx''': this provides the full SGX software stack, including the enclave development libraries and headers, host OS development libraries and headers, supporting host OS build tools, and various host OS runtime daemons/binaries. This package will include '''unsigned''' builds of the architectural enclaves built using the standard Fedora toolchain. Users could choose to sign these with their own keys and deploy them, with the caveat noted earlier wrt the '''pce''' enclave in particular. This package will result in creation of many binary sub-RPMs for distinct components. * '''linux-sgx-enclaves-prebuilt''': this provides solely the pre-built, signed architectural enclaves. While they could be provided as part of the '''linux-sgx''' package, it is split off to make it simpler to update the architectural enclave independently of the main software stack. This ability will be important if needing to ship a new release of SGX enclaves for a security fix in stable Fedora branches, without being forced to introduce updates of the host OS software stack that may have inappropriate changes for pushing into an existing stable branch. ==== Optional extra: reproducible builds ==== The SGX pre-built, signed architectural enclaves are built from code entirely under Fedora approved OSS licenses and support a reproducible build process. The upstream implementation of this process involves an Ubuntu dockerfile that populates a NixOS build environment. With some skilled work, it is possible to replicate an equivalent build environment in the context of Fedora. It requires providing custom builds of GCC, binutils, nasm, glibc (headers only) and kernel (uapi headers only) at specific release versions, with specific build configuration options and certain patches. Given such packages in Fedora, it is then possible to perform a reproducible build that successfully validates as matching the code payload of the pre-built, signed architectural enclaves. Maintaining such a reproducible build process in Fedora would have a non-negligible maintenance overhead if done on an ongoing basis. Originally it was thought that a reproducible build could be performed in the same package that provides the pre-built enclave binaries, as a way to block shipping of the pre-built binaries, unless proved to match the source. Given the requirements for specific toolchain versions, however, this would impose considerable delays when shipping CVE updates in stable Fedora branches. eg a newly issued pre-built enclave binary containing a CVE fix, may imply use of newer GCC, binutils, nasm versions than are currently available in the Fedora stable release. It is highly undesirable to go through the new package process to add new toolschain versions to stable Fedora, as a pre-requisite to ship CVE fixes in a stable branch, even if the new package process were expedited to avoid full re-review. If a reproducible build were to be mandated, it would involve the following additional packages in Fedora: * '''sgx-compat-gccXXXX''' - one (or more) GCC builds at specified designated versions required by the reproducible build * '''sgx-compat-binutilsXXXX''' - one (or more) binutils builds at specified designated versions required by the reproducible build * '''sgx-compat-nasmXXXX''' - one NASM build at specified designated versions required by the reproducible build * '''sgx-compat-glibc-headersXXXX''' - one glibc build at specified designated versions required by the reproducible build. Note only the header files are required, no library build. * '''sgx-compat-kernel-headersXXXX''' - one kernel build at specified designated versions required by the reproducible build. Note only the uapi header files are required, no vmlinux build * '''sgx-enclaves-reproducibleXXX''' - one (or more) reproducible builds of SGX architectural enclaves Note, the need for multiple versions of GCC & binutils in the reproducible build is an [https://github.com/intel/linux-sgx/issues/1045 upstream build environment bug]. Note, the need for glibc & header headers is also a likely [https://github.com/intel/linux-sgx/pull/1062 upstream build environment bug]. Note, the need for multiple '''sgx-enclaves-reproducibleXXX''' versions in parallel is because not all enclaves re-issued on each release. Only enclaves which have CVE fixes or functional changes get re-issued as new pre-built, signed binaries. IOW to validate all binary enclaves potentially requires doing reproducible builds of multiple SGX releases. === Other developers=== Maintainers of the '''fedora-release''' package will need to review a merge request that proposes new systemd unit file presets. See later in this document for the details of units. ===Release engineering=== N/A - does not impact deliverables for releng ===Policies and guidelines=== Agreement is needed around the designation of the pre-built, signed SGX architectural enclaves as firmware. Note, "'''architectural enclaves'''" are being considered distinct from "'''application enclaves'''" - the latter should be expected to build from source in the normal manner & be signed by Fedora, if any such enclaves are ever added to Fedora. ==== Architectural enclaves as firmware ==== Normal Fedora practice requires building everything from source. There is a general exception to this for firmware blobs, which don't need to be built from source and don't need to be under an OSS compliant license as long as the binaries can be freely distributed. Hardware firmware binaries almost always include a digital signature from the vendor, to ensure that only trusted firmware is loaded onto the device. Thus even if source code is available for a given firmware binary, Fedora would still need to be shipping it as a pre-built vendor supplied signed binary, in order to pass the cryptographic verification checks typically performed by hardware when loading firmware. Another example of shipping pre-built vendor binaries would be CPU microcode. This could be considered firmware for the core CPU, and again are vendor supplied, signed binaries, with no source code available. The architectural enclaves satisfy the classical role of firmware, in the context of the SGX technology, providing enablement for application usage. Unusually for firmware they are made available with 100% of their code under Fedora approved OSS licenses. The architectural enclaves, however, are still consumed as pre-built signed binaries due to the need to establish a chain of trust rooted back to Intel as the CPU hardware vendor. '''Overall''', the architectural enclaves meet the definition of firmware documented in the [https://docs.fedoraproject.org/en-US/legal/license-approval/#_technical_fir… Fedora licensing guidelines]: # ''The files must be non-executable within the Fedora Linux context (note: this means that the files cannot run on their own, not that they are just chmod -x).'' ✅ enclave ELF binarjies must be loaded into memory using the specialized SGX loader. # ''The files must not be libraries, within the Fedora Linux context.'' ✅ enclave ELF binaries must be loaded into memory using as specialized SGX loader, the glibc ELF loader can not be used for this. # ''The files must be standalone, not embedded in executable or library code (within the Fedora Linux context).'' ✅ enclave binaries are always standalone, self-contained files. They are consumed by regular host software, but cannot be linked to Fedora platform binaries/libraries. # ''The files must be necessary for the functionality of open source code being included in Fedora Linux or to enable Fedora Linux to boot on a specific device, where no other reliable and supported mechanisms exist.'' ✅ the pre-built, signed '''architectural enclaves''' shipped by Intel, serve to bootstrap the use of SGX technology by applications. ❌ as higher level software services, other '''application enclaves''' would not qualify. Thus it should be permissible to ship the pre-built, signed '''architectural enclaves''' binaries with no policy changes. Conversely '''application enclaves''' should NOT be considered firmware, and thus be required to follow the full Fedora packaging guidelines. No '''application enclaves''' are anticipated for inclusion in Fedora with this change proposal. ==== Reproducible build validation policy ==== Even if the view of '''architectural enclaves''' as firmware were to be rejected, there is an alternative precedent that can justify inclusion of the pre-built signed enclaves in Fedora. In this case we consider the '''shim''' package, where Fedora builds a binary from known good source, possibly with local patches, and sends it off for signing by Microsoft, packaging the binary that is sent back into an RPM. Microsoft has various requirements before it will permit signing a vendor's shim. Consider if the requirements on shim signing were tightened a little more to require a designated toolchain version, such that all shim builds became 100% reproducible on any platform. There would be no need to send the binary to Microsoft for signing, as any binary built in Fedora would inherently match a standard pre-published signed binary from that shim release + toolchain. It would be impossible to distinguish Microsoft signing & returning Fedora's reproducible build, from Microsoft sending back their original pre-signed build. This is effectively the situation SGX architectural enclaves are in. None the less, there are some differences between the shim & SGX scenarios. The first is that today Fedora has the ability to add arbitrary local patches to shim & build with arbitrary toolchain versions, which would be in conflict with a hypothetical requirement for reproducible builds & fixed toolchain. The second is that on most (but not all) hardware, users can enroll personal certificates in the firmware to allow it to trust a shim binary signed by the user, rather than Microsoft. In the case of SGX enclaves, it is strictly possible from a technical POV for a user to build & load & run their own self-signed SGX architectural enclaves. From a practical POV, however, it is inescapable for the '''pce''' enclave to have an Intel signature. Without that signature, no certificate proving authenticity of the hardware can be obtained from Intel, which would thus undermine the goal of SGX technology. The certificate is the mechanism for the Fedora user to prove to themselves that their platform contains genuine Intel CPUs. The other enclaves do have ways to be used with user supplied signatures, provided the consuming applications allow sufficient flexibility in their verification mechanisms. From a practical POV, all usage will be expecting Intel signatures again because these signatures are a means for users to establish trust in their hardware platform, but users do have the freedom to diverge if needed. ===Trademark approval=== N/A ===Alignment with the Fedora Strategy=== This aligns with * '''"Reaching the world"'''. Including SGX will make the Fedora support for hosting Intel TDX confidential virtual machines feature complete, by enabling attestation by the guest owner * '''"Innovation & leadership in technology"'''. SGX is a general purpose infrastructure technology which enables application developers to build systems to securely run sensitive workloads. Confidential virtual machines are expected to become a standard part of the public cloud in the coming years, as well as make inroads into private clouds in large organizations. As noted earlier, SGX unlocks the ability to ship TDX confidential VM technology in future Fedora. == Upgrade/compatibility impact == This is a new package set which should not have any upgrade impact, as it will not initially be a dependency of other software. In future it may be pulled in automatically as a dependency in certain KVM deployment scenarios. Even when installed, using anything related to SGX first requires host firmware changes to enable use of the technology. The systemd services provided have their unit files conditionalized on the existence of '''/dev/sgx_enclave''' device nodes. == Early Testing (Optional) == Do you require 'QA Blueprint' support? N The proposed new packages are available for testing via Copr, until such time as they are reviewed & built in Fedora koji: * https://copr.fedorainfracloud.org/coprs/berrange/sgx-ng/ These should work on any Intel Xeon class platform which has a suitable HW configuration. NB there may be specific DIMM population requirements. == How To Test == * [https://fedoraproject.org/wiki/Virt/SGX Documentation on host setup] is available but that's a fairly minimalist test. It does not do much that's interesting to an end user, but is at least proving that the '''pce''' and '''ide''' enclaves are usable. This is the limit of the anticipated testing of SGX in Fedora. More extensive testing will be performed when TDX is integrated at a later date, though some of this may be performed early on an adhoc basis using development snapshots of TDX. == User Experience == Initially the will be minimal real world user experience impact, since on its own this proposal doesn't deliver noticeable end user features. No existing applications in Fedora are known to have support for SGX and none are being proposed yet. The conceptual user benefit will be that users can bootstrap trust in SGX on their Fedora host. This will facilitate users in deploying 3rd party applications of their choosing that utilize SGX. It will facilitate testing by engineers working on TDX support and its integration into Fedora. At a later time, when support for Intel TDX is integrated into KVM and QEMU, the real world Fedora user benefit will significantly expand. == Dependencies == The primary functional dependency for use of SGX is kernel support, which has been enabled in Fedora for some time. See "'''CONFIG_X86_SGX=y'''" in the kconfig files. The packages include some new systemd unit files, two of which should be configured to be started by default. This will require changes to the systemd presets in the 'fedora-release' package. * '''mpa_registration.service''' - this is conditionalized on SGX being enabled, as witnessed by existence of '''/dev/sgx_eclave.''' Thus enabling it by default will be a no-op on any existing machines which have not had SGX turned on in the firmware. It is expected to be installed on all SGX installations * '''qgs.socket''' (as a trigger for '''qgs.service''') - this is likewise conditionalized on SGX being enabled. This will may be pulled in as a dependency of either libvirt or QEMU RPMs, TBD in the future TDX change proposal. == Contingency Plan == * Contingency mechanism: The new packages have no ill effects on existing Fedora usage. Any outstanding work can be postponed to a later release if required. * Contingency deadline: Beta freeze * Blocks release? No == Documentation == [https://fedoraproject.org/wiki/Virt/SGX Documentation on host setup] is available which is pretty much all that this change is expected to enable. A change proposal in future Fedora will cover usage of SGX with TDX confidential virtual machines, which is more interesting to end users. == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce December 2024