Bug 2086091 - Review Request: rust-num_threads - Determine the number of running threads for the current process
Summary: Review Request: rust-num_threads - Determine the number of running threads fo...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anderson Sasaki
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2043327
TreeView+ depends on / blocked
 
Reported: 2022-05-13 19:48 UTC by Fabio Valentini
Modified: 2022-05-31 20:40 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-05-31 20:40:53 UTC
Type: ---
Embargoed:
ansasaki: fedora-review+

Attachments (Terms of Use)

Description Fabio Valentini 2022-05-13 19:48:14 UTC 
Spec URL: https://decathorpe.fedorapeople.org/rust-num_threads.spec
SRPM URL: https://decathorpe.fedorapeople.org/rust-num_threads-0.1.6-1.fc36.src.rpm

Description:
Minimal library that determines the number of running threads for the current
process.

Fedora Account System Username: decathorpe

koji scratch build for rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=87007378
Comment 1 Anderson Sasaki 2022-05-31 10:08:39 UTC 
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 (MIT or ASL 2.0) and is acceptable for Fedora
- license files are included with %license in %files
- package complies with Rust Packaging Guidelines

Package APPROVED.
Comment 2 Gwyn Ciesla 2022-05-31 15:06:04 UTC 
(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-num_threads
Comment 3 Fabio Valentini 2022-05-31 20:40:53 UTC 
Built for rawhide:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1973998

Will be submitted to bodhi with the actix-web 4 update.
Note You need to log in before you can comment on or make changes to this bug.