Bug 1990626 - Review Request: rust-thread-tree - Tree-structured thread pool for splitting jobs hierarchically on worker threads
Summary: Review Request: rust-thread-tree - Tree-structured thread pool for splitting ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1990584 1993868
TreeView+ depends on / blocked
 
Reported: 2021-08-05 18:43 UTC by Davide Cavalca
Modified: 2021-10-28 18:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-27 02:08:36 UTC
Type: ---
Embargoed:
decathorpe: fedora-review+


Attachments (Terms of Use)

Description Davide Cavalca 2021-08-05 18:43:33 UTC
Spec URL: https://dcavalca.fedorapeople.org/review/rust-thread-tree/rust-thread-tree.spec
SRPM URL: https://dcavalca.fedorapeople.org/review/rust-thread-tree/rust-thread-tree-0.3.2-1.fc35.src.rpm

Description:
Tree-structured thread pool for splitting jobs hierarchically on worker
threads.
The tree structure means that there is no contention between workers when
delivering jobs.

Fedora Account System Username: dcavalca

Comment 1 Davide Cavalca 2021-08-05 18:43:35 UTC
This package built on koji:  https://koji.fedoraproject.org/koji/taskinfo?taskID=73347769

Comment 2 Fabio Valentini 2021-10-18 14:32:19 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 and is acceptable for Fedora
- license file is included with %license in %files
- package complies with Rust Packaging Guidelines

You might want to trim the package's Summary, it is a bit wide (almost 80 characters).

Package APPROVED.

If you have a few minutes' time, it would be great if you could review 1998894 for me in turn.

Comment 3 Gwyn Ciesla 2021-10-18 15:43:53 UTC
(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-thread-tree

Comment 4 Fedora Update System 2021-10-18 16:16:42 UTC
FEDORA-2021-5f1d4ab49b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5f1d4ab49b

Comment 5 Fedora Update System 2021-10-18 16:27:05 UTC
FEDORA-2021-d6a0f68c16 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d6a0f68c16

Comment 6 Fedora Update System 2021-10-19 00:48:29 UTC
FEDORA-2021-d6a0f68c16 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2021-d6a0f68c16 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d6a0f68c16

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2021-10-20 13:47:21 UTC
FEDORA-2021-5f1d4ab49b has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2021-5f1d4ab49b \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5f1d4ab49b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2021-10-27 02:08:36 UTC
FEDORA-2021-d6a0f68c16 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2021-10-28 18:27:47 UTC
FEDORA-2021-5f1d4ab49b has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.