Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 2154859 [details] Configuration file for rust2rpm Spec URL: https://music.fedorapeople.org/rust-icu_locale_fallback_data.spec SRPM URL: https://music.fedorapeople.org/rust-icu_locale_fallback_data-2.3.0-1.fc44.src.rpm Description: Data for the icu_locale_fallback crate. Fedora Account System Username: music A new crate in ICU4X 2.3.
Package was generated with rust2rpm, simplifying the review. ✅ package contains only permissible content ✅ package builds and installs without errors on rawhide ✅ test suite is run and all unit tests pass ✅ latest version of the crate is packaged ✅ license matches upstream specification and is acceptable for Fedora ✅ license file is included with %license in %files ✅ package complies with Rust Packaging Guidelines Package APPROVED. Side note: It looks like debian is working on packaging these icu "data" crates in a way that allows them to re-generate the generated code at build-time (running icu_datagen?) - we might be able to adapt that (if we want?) if that works out. === Recommended post-import rust-sig tasks: - set up package on release-monitoring.org: project: $crate homepage: https://crates.io/crates/$crate backend: crates.io version scheme: semantic version filter (*NOT* pre-release filter): alpha;beta;rc;pre distro: Fedora Package: rust-$crate - set bugzilla assignee overrides to @rust-sig (optional)
(In reply to Fabio Valentini from comment #1) > Package APPROVED. Thank you! https://release-monitoring.org/project/391854/ I will follow up with the review request for rust-icu_locale_fallback shortly. You won’t be able to build it in Rawhide, but I’ll at least build it in COPR with fedora-review enabled. > Side note: It looks like debian is working on packaging these icu "data" > crates in a way that allows them to re-generate the generated code at > build-time (running icu_datagen?) - we might be able to adapt that (if we > want?) if that works out. I am intrigued! I am also aware that the data-generation pipeline involves a significant number of additional crates that we wouldn’t otherwise have to package; that there is a risk of discrepancies when re-generating the data; and that this could end up having some tension with the mandate to use only crates.io sources to build Rust library packages. I’d like to see what they come up with, but I am not sure if it will prove worthwhile for us.
The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-icu_locale_fallback_data Monitoring: Wasn't able to create project in Anitya. You can create it manually on: `https://release-monitoring.org`
FEDORA-2026-7343fa396d (rust-icu_locale_fallback_data-2.3.0-1.fc46) has been submitted as an update to Fedora 46. https://bodhi.fedoraproject.org/updates/FEDORA-2026-7343fa396d
FEDORA-2026-7343fa396d (rust-icu_locale_fallback_data-2.3.0-1.fc46) has been pushed to the Fedora 46 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-37015229f2 (rust-icu_locale_fallback_data-2.3.0-1.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-37015229f2
FEDORA-2026-37015229f2 (rust-icu_locale_fallback_data-2.3.0-1.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
(In reply to Ben Beasley from comment #2) > > I will follow up with the review request for rust-icu_locale_fallback > shortly. You won’t be able to build it in Rawhide, but I’ll at least build > it in COPR with fedora-review enabled. bug 2519638