Bug 2396030 - Review Request: rust-vsock - Virtio socket support for Rust
Summary: Review Request: rust-vsock - Virtio socket support for Rust
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: fedora.dm0
QA Contact: Fedora Extras Quality Assurance
URL: https://crates.io/crates/vsock
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-17 10:47 UTC by Dorinda
Modified: 2025-09-17 13:06 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-09-17 13:06:46 UTC
Type: ---
Embargoed:
fedora.dm0: fedora-review+


Attachments (Terms of Use)
The .spec file difference from Copr build 9562135 to 9562145 (847 bytes, patch)
2025-09-17 10:59 UTC, Fedora Review Service
no flags Details | Diff

Comment 1 Fedora Review Service 2025-09-17 10:49:30 UTC
Copr build:
https://copr.fedorainfracloud.org/coprs/build/9562135
(failed)

Build log:
https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2396030-rust-vsock/fedora-rawhide-x86_64/09562135-rust-vsock/builder-live.log.gz

Please make sure the package builds successfully at least for Fedora Rawhide.

- If the build failed for unrelated reasons (e.g. temporary network
  unavailability), please ignore it.
- If the build failed because of missing BuildRequires, please make sure they
  are listed in the "Depends On" field


---
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 Fedora Review Service 2025-09-17 10:59:18 UTC
Created attachment 2106847 [details]
The .spec file difference from Copr build 9562135 to 9562145

Comment 4 Fedora Review Service 2025-09-17 10:59:20 UTC
Copr build:
https://copr.fedorainfracloud.org/coprs/build/9562145
(succeeded)

Review template:
https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2396030-rust-vsock/fedora-rawhide-x86_64/09562145-rust-vsock/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 5 fedora.dm0 2025-09-17 11:58:01 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, excluding those requiring kernel modules and VM access in the buildroot
- latest version of the crate is packaged
- license matches upstream specification (Apache-2.0) and is acceptable for Fedora
- license file is included with %license in %files
- package complies with Rust Packaging Guidelines

Package APPROVED.

===

Recommended post-import rust-sig tasks:

- add @rust-sig with "commit" access as package co-maintainer

- set bugzilla assignee overrides to @rust-sig (optional)

- 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

- track package in koschei for all built branches

Comment 6 Fedora Admin user for bugzilla script actions 2025-09-17 12:42:16 UTC
The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-vsock

Comment 7 Fedora Update System 2025-09-17 13:02:26 UTC
FEDORA-2025-f9e6f6fa43 (rust-vsock-0.5.1-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f9e6f6fa43

Comment 8 Fedora Update System 2025-09-17 13:06:46 UTC
FEDORA-2025-f9e6f6fa43 (rust-vsock-0.5.1-1.fc44) has been pushed to the Fedora 44 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.