Bug 2342143 - Review Request: rust-rust-fuzzy-search - Fuzzy Search with trigrams implemented in Rust
Summary: Review Request: rust-rust-fuzzy-search - Fuzzy Search with trigrams implement...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: wojnilowicz
QA Contact: Fedora Extras Quality Assurance
URL: https://crates.io/crates/rust-fuzzy-s...
Whiteboard:
Depends On:
Blocks: 2333544
TreeView+ depends on / blocked
 
Reported: 2025-01-26 15:45 UTC by Fabio Valentini
Modified: 2025-02-16 19:31 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-16 19:31:52 UTC
Type: ---
Embargoed:
lukasz.wojnilowicz: fedora-review+


Attachments (Terms of Use)

Description Fabio Valentini 2025-01-26 15:45:45 UTC
Spec URL: https://decathorpe.fedorapeople.org/rust-rust-fuzzy-search.spec
SRPM URL: https://decathorpe.fedorapeople.org/rust-rust-fuzzy-search-0.1.1-1.fc41.src.rpm

Description:
Fuzzy Search with trigrams implemented in Rust.

Fedora Account System Username: decathorpe

Comment 1 Fabio Valentini 2025-01-26 15:45:47 UTC
This package built on koji:  https://koji.fedoraproject.org/koji/taskinfo?taskID=128501443

Comment 2 Fedora Review Service 2025-01-26 15:48:44 UTC
Copr build:
https://copr.fedorainfracloud.org/coprs/build/8571238
(succeeded)

Review template:
https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2342143-rust-rust-fuzzy-search/fedora-rawhide-x86_64/08571238-rust-rust-fuzzy-search/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.

Comment 3 wojnilowicz 2025-02-13 20:20:33 UTC
===

Package was generated with rust2rpm. The binary has been removed manually, but it seems to not offer any feature except calling one function. Simplifying the review anyway.

✅ 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
✅ licenses of statically linked dependencies are correctly taken into account
✅ license file is 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 (*NOT* pre-release) 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)

BTW, could you review https://bugzilla.redhat.com/show_bug.cgi?id=2344534 in return?

Comment 4 Fabio Valentini 2025-02-16 16:52:10 UTC
Thank you for the review! I'll take a look at the linked bug ASAP.

Comment 5 Fedora Admin user for bugzilla script actions 2025-02-16 16:52:36 UTC
The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-rust-fuzzy-search

Comment 6 Fedora Update System 2025-02-16 19:28:04 UTC
FEDORA-2025-9467b6b49e (rust-argh-0.1.13-1.fc43, rust-argh_derive-0.1.13-1.fc43, and 2 more) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-9467b6b49e

Comment 7 Fedora Update System 2025-02-16 19:31:52 UTC
FEDORA-2025-9467b6b49e (rust-argh-0.1.13-1.fc43, rust-argh_derive-0.1.13-1.fc43, and 2 more) has been pushed to the Fedora 43 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.