Spec URL: https://dcavalca.fedorapeople.org/review/rust-rusty-forkfork/rust-rusty-forkfork.spec SRPM URL: https://dcavalca.fedorapeople.org/review/rust-rusty-forkfork/rust-rusty-forkfork-0.4.0-1.fc41.src.rpm Description: Cross-platform library for running Rust tests in sub-processes using a fork-like interface. Fedora Account System Username: dcavalca
This package built on koji: https://koji.fedoraproject.org/koji/taskinfo?taskID=118170392
> rust-rusty-forkfork+timeout-devel.noarch: E: summary-too-long Cross-platform library for running Rust tests in sub-processes using a fork-like interface > rust-rusty-forkfork+wait-timeout-devel.noarch: E: summary-too-long Cross-platform library for running Rust tests in sub-processes using a fork-like interface > rust-rusty-forkfork-devel.noarch: E: summary-too-long Cross-platform library for running Rust tests in sub-processes using a fork-like interface > rust-rusty-forkfork+default-devel.noarch: E: summary-too-long Cross-platform library for running Rust tests in sub-processes using a fork-like interface Please address this before importing the package. === Package was generated with rust2rpm, simplifying the review. ✅ 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: alpha;beta;rc;pre distro: Fedora Package: rust-$crate - add @rust-sig with "commit" access as package co-maintainer (should happen automatically) - set bugzilla assignee overrides to @rust-sig (optional) - track package in koschei for all built branches (should happen automatically once rust-sig is co-maintainer) === If you have time, it would be great if you could review one of my pending packages in return.
The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-rusty-forkfork
FEDORA-2024-ed0d123fe4 (rust-rusty-forkfork-0.4.0-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ed0d123fe4
FEDORA-2024-ecb18e6e22 (rust-rusty-forkfork-0.4.0-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ecb18e6e22
FEDORA-2024-ee4222357b (rust-rusty-forkfork-0.4.0-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ee4222357b
FEDORA-2024-ed0d123fe4 (rust-rusty-forkfork-0.4.0-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-ee4222357b has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ee4222357b \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ee4222357b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-ecb18e6e22 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ecb18e6e22 \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ecb18e6e22 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-ecb18e6e22 (rust-rusty-forkfork-0.4.0-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-ee4222357b (rust-rusty-forkfork-0.4.0-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.