Rust November 2025

rust@lists.fedoraproject.org

3 participants
4 discussions

HEADS-UP: cargo-rpm-macros v28 headed to stable branches soon
by Fabio Valentini 20 Nov '25

20 Nov '25

Hi all, I am planning to submit updates for cargo-rpm-macros v28.0, rust2rpm v28.0.0, and cargo2rpm v0.3 to Fedora 43 and 42 shortly. Release notes linked below. These updates have already landed in rawhide and have not caused issues there (except for two packages that used the "%cargo_install" macro in a way that just "happened" to work previously - both of which I have submitted PRs for, and I have included a workaround in cargo2rpm v0.3.1 to avoid the issue entirely). Despite this being a "major" version bump for cargo-rpm-macros, this is mostly symbolic - there are no user-visible changes. Only some internal implementation details have changed since v26, which allow for more correct / less surprising behaviour in some cases, and easier future maintenance. More features are now implemented in Python in cargo2rpm rather than as shell scripts in the RPM macros directly. The accompanying rust2rpm v28.0.0 *does* have some user-visible changes. Some deprecated features have been removed, and a few new features have been added. The default workflow of running "rust2rpm foo" to generate a "rust-foo.spec" file for the "foo" crate is not affected by the removal of deprecated functionality. Release notes: - https://codeberg.org/rust2rpm/cargo-rpm-macros/releases/tag/v28.0 - https://codeberg.org/rust2rpm/rust2rpm/releases/tag/v28.0.0 - https://codeberg.org/rust2rpm/cargo2rpm/releases/tag/v0.3.0 - https://codeberg.org/rust2rpm/cargo2rpm/releases/tag/v0.3.1 Fabio

1 0

Request for Rust SIG Organization + Team on forge.fp.o
by Fabio Valentini 11 Nov '25

11 Nov '25

Hi all, I filed a request to create an Organization and Teams for the Rust SIG on forge.fp.o, where I intend to move the remaining projects from the pagure.io/fedora-rust namespace (that haven't already been migrated to codeberg.org) https://pagure.io/fedora-infrastructure/issue/12911 Please comment there if you spot any mistakes or missing things. Fabio

1 0

gtk-rs / gstreamer-rs packager points of contact
by Fabio Valentini 07 Nov '25

07 Nov '25

Hello packagers, I recently went over the packages related to gtk-rs / gstreamer-rs and noticed that a lot of them had "main admin"s that haven't touched the packages in years. In practice, I have already been the sole maintainer of the GTK / GLib / GStreamer Rust bindings for the past ~four years. If you are in the CC of this email, you are the "main admin" of package(s) related to gtk-rs / gstreamer-rs, and I would ask that you consider assigning the "main admin" role to me, just to reflect who is / will be (and was, for the past 4 years) actually doing the maintaining. Thank you, Fabio atim: - rust-gstreamer-sys - rust-gstreamer-audio - rust-gstreamer-audio-sys - rust-gstreamer-base - rust-gstreamer-base-sys - rust-gstreamer-pbutils - rust-gstreamer-pbutils-sys - rust-gstreamer-video - rust-gstreamer-video-sys jistone: - rust-glib-macros mclasen: - rust-ashpd - rust-gdk4-wayland - rust-gdk4-wayland-sys - rust-gdk4-x11 - rust-gdk4-x11-sys - rust-gst-plugin-gtk4 - rust-gstreamer-gl - rust-gstreamer-gl-sys - rust-gstreamer-gl-egl - rust-gstreamer-gl-egl-sys - rust-gstreamer-gl-wayland - rust-gstreamer-gl-wayland-sys - rust-gstreamer-gl-x11 - rust-gstreamer-gl-x11-sys - rust-gvdb - rust-libadwaita - rust-libadwaita-sys

1 0

Packaging "rollup"
by Gordon Messmer 05 Nov '25

05 Nov '25

Hello, rust sig, I'm trying to package a NodeJS program, "rollup". Rollup uses wasm-pack to build some internal Rust crates. Early attempts to package this fail because cargo is trying to access the network. I probably need to adapt the cargo rpm macros for this case, but that is somewhat difficult because cargo is being called by wasm-pack. I might be able to introduce a shell script called "cargo" (and put that at the beginning of PATH) that expands the rpm macros and calls the real cargo binary with a combination of the rpm macro arguments and the arguments passed by wasm-pack, but I am wondering if you might have a more elegant solution? Thanks for any suggestions you might have. https://github.com/rollup/rollup/blob/master/package.json#L43 https://github.com/drager/wasm-pack

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

Rust November 2025