Bug 2453125

Summary:	rust-b3sum-1.8.4 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.8.4-1.el10_2 rust-b3sum-1.8.4-1.el10_3 rust-b3sum-1.8.4-1.el9 rust-b3sum-1.8.4-1.fc43 rust-b3sum-1.8.4-1.fc42 rust-b3sum-1.8.4-1.fc44	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-04-09 00:27:00 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:
Bug Depends On:	2453126
Bug Blocks:

Description Upstream Release Monitoring 2026-03-30 18:12:59 UTC

Releases retrieved: 1.8.4
Upstream release that is considered latest: 1.8.4
Current version/release in rawhide: 1.8.3-2.fc44
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 2026-03-31 21:38:55 UTC

FEDORA-2026-6b6c6ef353 (rust-b3sum-1.8.4-1.fc45 and rust-blake3-1.8.4-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-6b6c6ef353

Comment 2 Fedora Update System 2026-03-31 21:39:11 UTC

FEDORA-2026-ecc2211338 (rust-b3sum-1.8.4-1.fc44 and rust-blake3-1.8.4-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-ecc2211338

Comment 3 Fedora Update System 2026-03-31 21:39:34 UTC

FEDORA-2026-9323dec806 (rust-b3sum-1.8.4-1.fc43 and rust-blake3-1.8.4-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-9323dec806

Comment 4 Fedora Update System 2026-03-31 21:39:50 UTC

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

Comment 5 Fedora Update System 2026-03-31 21:40:04 UTC

FEDORA-EPEL-2026-837eab52de (rust-b3sum-1.8.4-1.el10_3 and rust-blake3-1.8.4-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-837eab52de

Comment 6 Fedora Update System 2026-03-31 21:40:18 UTC

FEDORA-EPEL-2026-8beb75e155 (rust-b3sum-1.8.4-1.el10_2 and rust-blake3-1.8.4-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-8beb75e155

Comment 7 Fedora Update System 2026-03-31 21:41:34 UTC

FEDORA-EPEL-2026-7930f6e1dc (rust-b3sum-1.8.4-1.el9 and rust-blake3-1.8.4-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7930f6e1dc

Comment 8 Fedora Update System 2026-03-31 21:41:57 UTC

FEDORA-2026-6b6c6ef353 (rust-b3sum-1.8.4-1.fc45 and rust-blake3-1.8.4-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2026-04-01 01:16:06 UTC

FEDORA-EPEL-2026-8beb75e155 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-8beb75e155

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

Comment 10 Fedora Update System 2026-04-01 01:23:14 UTC

FEDORA-EPEL-2026-837eab52de has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-837eab52de

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

Comment 11 Fedora Update System 2026-04-01 01:29:22 UTC

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

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

Comment 12 Fedora Update System 2026-04-01 01:29:42 UTC

FEDORA-EPEL-2026-7930f6e1dc 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-2026-7930f6e1dc

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

Comment 13 Fedora Update System 2026-04-01 01:47:10 UTC

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

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

Comment 14 Fedora Update System 2026-04-01 02:18:17 UTC

FEDORA-2026-b7d182686e 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-2026-b7d182686e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-b7d182686e

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

Comment 15 Fedora Update System 2026-04-09 00:27:00 UTC

FEDORA-EPEL-2026-8beb75e155 (rust-b3sum-1.8.4-1.el10_2 and rust-blake3-1.8.4-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2026-04-09 00:37:47 UTC

FEDORA-EPEL-2026-837eab52de (rust-b3sum-1.8.4-1.el10_3 and rust-blake3-1.8.4-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2026-04-09 00:50:29 UTC

FEDORA-EPEL-2026-7930f6e1dc (rust-b3sum-1.8.4-1.el9 and rust-blake3-1.8.4-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 18 Fedora Update System 2026-04-09 03:22:44 UTC

FEDORA-2026-9323dec806 (rust-b3sum-1.8.4-1.fc43 and rust-blake3-1.8.4-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 19 Fedora Update System 2026-04-09 03:37:35 UTC

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

Comment 20 Fedora Update System 2026-04-25 01:31:20 UTC

FEDORA-2026-ecc2211338 (rust-b3sum-1.8.4-1.fc44 and rust-blake3-1.8.4-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.