Spec URL: https://download.copr.fedorainfracloud.org/results/ngompa/fish4/fedora-rawhide-x86_64/10130010-rust-xterm-color/rust-xterm-color.spec SRPM URL: https://download.copr.fedorainfracloud.org/results/ngompa/fish4/fedora-rawhide-x86_64/10130010-rust-xterm-color/rust-xterm-color-1.0.2-1.fc45.src.rpm Description: Parses the subset of X11 Color Strings emitted by terminals in response to OSC color queries. Fedora Account System Username: ngompa
Package was generated with rust2rpm, simplifying the review. 🫤 Summary is too long - please trim to <80 characters and add a rust2rpm.toml config file to store the new value. ✅ 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 files are included with %license in %files ✅ package complies with Rust Packaging Guidelines Package APPROVED. === 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)
The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-xterm-color
FEDORA-2026-2313357be4 (rust-xterm-color-1.0.2-1.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-2313357be4
FEDORA-2026-4fd2fbaf59 (rust-xterm-color-1.0.2-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-4fd2fbaf59
FEDORA-2026-2313357be4 (rust-xterm-color-1.0.2-1.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-4fd2fbaf59 (rust-xterm-color-1.0.2-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.