Bug 2348851

Summary:	rust-b3sum-1.6.1 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	rust-b3sum	Assignee:	Ben Beasley <code>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	code, rust-sig
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rust-b3sum-1.6.1-1.fc41 rust-b3sum-1.6.1-1.el10_0 rust-b3sum-1.6.1-1.el10_1 rust-b3sum-1.6.1-1.el9 rust-b3sum-1.6.1-1.fc40 rust-b3sum-1.6.1-1.fc42	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-03-09 02:15:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2025-02-27 19:35:19 UTC

Releases retrieved: 1.6.1
Upstream release that is considered latest: 1.6.1
Current version/release in rawhide: 1.6.0-1.fc43
URL: https://crates.io/crates/b3sum

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/283971/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/rust-b3sum

Comment 1 Fedora Update System 2025-02-28 03:43:00 UTC

FEDORA-2025-4ee19f32b6 (rust-b3sum-1.6.1-1.fc43 and rust-blake3-1.6.1-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4ee19f32b6

Comment 2 Fedora Update System 2025-02-28 03:43:27 UTC

FEDORA-2025-dc7cddb6f5 (rust-b3sum-1.6.1-1.fc42 and rust-blake3-1.6.1-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-dc7cddb6f5

Comment 3 Fedora Update System 2025-02-28 03:43:47 UTC

FEDORA-2025-5f280c91d1 (rust-b3sum-1.6.1-1.fc41 and rust-blake3-1.6.1-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5f280c91d1

Comment 4 Fedora Update System 2025-02-28 03:44:45 UTC

FEDORA-2025-3e6bd47ec7 (rust-b3sum-1.6.1-1.fc40 and rust-blake3-1.6.1-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-3e6bd47ec7

Comment 5 Fedora Update System 2025-02-28 03:45:04 UTC

FEDORA-EPEL-2025-d7ef5ad397 (rust-b3sum-1.6.1-1.el10_1 and rust-blake3-1.6.1-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d7ef5ad397

Comment 6 Fedora Update System 2025-02-28 03:45:24 UTC

FEDORA-EPEL-2025-a761bd2073 (rust-b3sum-1.6.1-1.el10_0 and rust-blake3-1.6.1-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a761bd2073

Comment 7 Fedora Update System 2025-02-28 03:45:54 UTC

FEDORA-EPEL-2025-0af4d79f30 (rust-b3sum-1.6.1-1.el9 and rust-blake3-1.6.1-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-0af4d79f30

Comment 8 Fedora Update System 2025-02-28 03:47:52 UTC

FEDORA-2025-4ee19f32b6 (rust-b3sum-1.6.1-1.fc43 and rust-blake3-1.6.1-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-03-01 01:54:04 UTC

FEDORA-2025-dc7cddb6f5 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-dc7cddb6f5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-dc7cddb6f5

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

Comment 10 Fedora Update System 2025-03-01 02:02:10 UTC

FEDORA-EPEL-2025-a761bd2073 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a761bd2073

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

Comment 11 Fedora Update System 2025-03-01 02:09:41 UTC

FEDORA-EPEL-2025-d7ef5ad397 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d7ef5ad397

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

Comment 12 Fedora Update System 2025-03-01 02:20:56 UTC

FEDORA-EPEL-2025-0af4d79f30 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-0af4d79f30

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

Comment 13 Fedora Update System 2025-03-01 03:08:14 UTC

FEDORA-2025-3e6bd47ec7 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-3e6bd47ec7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-3e6bd47ec7

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

Comment 14 Fedora Update System 2025-03-01 03:11:49 UTC

FEDORA-2025-5f280c91d1 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-5f280c91d1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5f280c91d1

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

Comment 15 Fedora Update System 2025-03-09 02:15:36 UTC

FEDORA-2025-5f280c91d1 (rust-b3sum-1.6.1-1.fc41 and rust-blake3-1.6.1-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2025-03-09 02:40:27 UTC

FEDORA-EPEL-2025-a761bd2073 (rust-b3sum-1.6.1-1.el10_0 and rust-blake3-1.6.1-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2025-03-09 03:00:42 UTC

FEDORA-EPEL-2025-d7ef5ad397 (rust-b3sum-1.6.1-1.el10_1 and rust-blake3-1.6.1-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2025-03-09 03:27:18 UTC

FEDORA-EPEL-2025-0af4d79f30 (rust-b3sum-1.6.1-1.el9 and rust-blake3-1.6.1-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 19 Fedora Update System 2025-03-09 03:30:57 UTC

FEDORA-2025-3e6bd47ec7 (rust-b3sum-1.6.1-1.fc40 and rust-blake3-1.6.1-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 20 Fedora Update System 2025-03-15 00:34:35 UTC

FEDORA-2025-dc7cddb6f5 (rust-b3sum-1.6.1-1.fc42 and rust-blake3-1.6.1-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.