Spec URL: https://dmellado.fedorapeople.org/rust-criterion/rust-criterion.spec SRPM URL: https://dmellado.fedorapeople.org/rust-criterion/rust-criterion-0.5.1-1.fc39.src.rpm Description: Statistics-driven micro-benchmarking library. Fedora Account System Username: dmellado
This package built on koji: https://koji.fedoraproject.org/koji/taskinfo?taskID=114132938
Copr build: https://copr.fedorainfracloud.org/coprs/build/7064868 (succeeded) Review template: https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2266307-rust-criterion/fedora-rawhide-x86_64/07064868-rust-criterion/fedora-review/review.txt Please take a look if any issues were found. --- This comment was created by the fedora-review-service https://github.com/FrostyX/fedora-review-service If you want to trigger a new Copr build, add a comment containing new Spec and SRPM URLs or [fedora-review-service-build] string.
Any special reason you want to package `criterion`? We usually just patch out benchmark dependencies, since bechmarks are not relevant for Fedora packaging / package maintenance activity.
I agree - benchmarks are neither compiled nor run during package builds. I don't think that packaging a project that will never be used and that only makes build times longer is a good way to spend your time - so please just drop the "criterion" dev-dependency whereever you find it. There are very few legitimate reasons to depend on criterion, but benchmarks are not one of them.
I'll go ahead and assume that you're not packaging a benchmarking tool, but submitted this as an (unused during package builds) dependency for something else.