New crates for Firecracker 1.4
by David Michael
Hi,
I tried the Firecracker 1.4 branch which depends on new crates that
will need to be added to Fedora. Should I wait for the release before
adding crates, or can they be packaged early while nothing depends on
them? (I don't know when the actual release will happen.) Here are
specific crate package changes:
A couple things depend on bindgen-0.65 now (and 0.66.1 is available),
although they have workarounds, e.g. ExclusiveArch for pregenerated
files. This update isn't necessary yet, but it would be nice to have.
Both bindgen-0.65 and firecracker-1.4 depend on bitflags-2, so that
update is required. The new bitflags depends on the unpackaged
zerocopy and zerocopy-derive for tests. (They have license file
issues that are fixed in Git for the upcoming 0.7.0 version but not in
stable releases on crates.io, and zerocopy-derive tests have a dep
loop on zerocopy.) Fabio, you own bitflags-1, do you want to own the
new API package and its deps, or should I submit their package review
requests?
The firecracker-1.4 branch relies on an AWS crypto library for VirtIO
RNG support. The main aws-lc-rs crate depends on aws-lc-sys and
mirai-annotations which will need to be added. The aws-lc library is
a separate C++ project which is bundled into the aws-lc-sys crate.[0]
Since nothing else in Fedora is using the aws-lc C++ library, my
preference would be to leave it as an implementation detail in the
crate and not unbundle it or worry about dynamic linking. Is that
acceptable for the package?
Thanks.
David
[0] https://github.com/aws/aws-lc-rs/tree/main/aws-lc-sys
3 months, 1 week
Upcoming retirement of unused compat packages for Rust crates
by Fabio Valentini
Hi all,
I'm planning to do another round of removals of unused Rust crates -
at first. focusing only on compat packages which are no longer useful
since they have no remaining dependent packages in Rawhide.
This includes the gtk-rs v0.16 / gtk4-rs v0.5 compat packages:
- rust-atk0.16
- rust-atk-sys0.16
- rust-cairo-rs0.16
- rust-cairo-sys-rs0.16
- rust-gdk0.16
- rust-gdk-sys0.16
- rust-gdk-pixbuf0.16
- rust-gdk-pixbuf-sys0.16
- rust-gio0.16
- rust-gio-sys0.16
- rust-glib0.16
- rust-glib-sys0.16
- rust-glib-macros0.16
- rust-gobject-sys0.16
- rust-graphene-rs0.16
- rust-graphene-sys0.16
- rust-gtk0.16
- rust-gtk-sys0.16
- rust-gtk3-macros0.16
- rust-pango0.16
- rust-pango-sys0.16
- rust-pangocairo0.16
- rust-pangocairo-sys0.16
- rust-gdk4_0.5
- rust-gdk4-sys0.5
- rust-gsk4_0.5
- rust-gsk4-sys0.5
- rust-gtk4_0.5
- rust-gtk4-sys0.5
- rust-gtk4-macros0.5
- rust-libadwaita0.2
- rust-libadwaita-sys0.2
Side note: The compat packages for the even older gtk-rs v0.15 /
gtk4-rs v0.4 / libadwaita-rs v0.1 cannot be removed yet, since
squeekboard and system76-keyboard-configurator still depend on these
obsolete versions ... :sad face:
Additional (unrelated to gtk-rs) compat packages which are no longer needed:
- rust-libudev0.2
- rust-memmap2_0.3
- rust-cargo_metadata0.12
- rust-tui0.9
- rust-ansi-str0.5
All listed packages are compat packages with newer versions of these
projects already being available in Fedora 37+, and all listed
packages have no dependent packages left. If anybody has objections to
retiring any of these packages despite this, please notify me within
the next 7 days, as I plan to process the retirement of all packages
listed in this email next Monday (June 5).
Fabio
3 months, 2 weeks