Bug 2265213

Summary:	rust-archery-1.2.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	rust-archery	Assignee:	Rust SIG <rust-sig>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	decathorpe, mattia.verga, rust-sig
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rust-archery-1.2.0-1.fc41 rust-archery-1.2.0-1.fc40	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-02-25 08:55:45 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 2024-02-20 23:39:27 UTC

Releases retrieved: 1.2.0
Upstream release that is considered latest: 1.2.0
Current version/release in rawhide: 1.1.0-2.fc40
URL: https://crates.io/crates/archery

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/360976/


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

Comment 1 Fedora Update System 2024-02-25 08:52:51 UTC

FEDORA-2024-3a08871837 (rust-archery-1.2.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-3a08871837

Comment 2 Fedora Update System 2024-02-25 08:54:59 UTC

FEDORA-2024-0584f20bc8 (rust-archery-1.2.0-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-0584f20bc8

Comment 3 Fedora Update System 2024-02-25 08:55:45 UTC

FEDORA-2024-3a08871837 (rust-archery-1.2.0-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 4 Fedora Update System 2024-02-25 08:58:33 UTC

FEDORA-2024-0584f20bc8 (rust-archery-1.2.0-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 5 Fabio Valentini 2024-02-28 21:44:32 UTC

Just wondering, is there a reason why this update was not pushed to Fedora 39 too?

Comment 6 Mattia Verga 2024-02-29 07:29:49 UTC

I suppose I could, but I keep the safe side and didn't touch a stable release.

$ fedrq wrsrc -F narmsrc:rust-archery rust-archery
python-rpds-py.src : (crate(archery/default) >= 1.1.0 with crate(archery/default) < 2.0.0~)
rust-archery+default-devel.noarch : crate(archery) = 1.2.0
rust-archery+fatal-warnings-devel.noarch : crate(archery) = 1.2.0
rust-archery+serde-devel.noarch : crate(archery) = 1.2.0
rust-archery+triomphe-devel.noarch : crate(archery) = 1.2.0
rust-rpds.src : (crate(archery/triomphe) >= 1.1.0 with crate(archery/triomphe) < 2.0.0~)
rust-rpds.src : (crate(archery/default) >= 1.1.0 with crate(archery/default) < 2.0.0~)
rust-rpds-devel.noarch : (crate(archery/triomphe) >= 1.1.0 with crate(archery/triomphe) < 2.0.0~)
rust-rpds-devel.noarch : (crate(archery/default) >= 1.1.0 with crate(archery/default) < 2.0.0~)

Do you want me to push it in F39 also?

Comment 7 Fabio Valentini 2024-02-29 10:32:05 UTC

Yes, please. F38 too, while you're at it :)
For library-only Rust packages, we try to keep them in sync between all the Fedora branches + EPEL 9. This makes maintenance much easier.

(For actual applications that are shipped to users, the reasoning is different, of course. But shipping library-only updates to stable branches is preferred in 99.9% of cases, unless it would create issues with applications that are intentionally not updated on older branches. But this is not the case here.)

Comment 8 Fabio Valentini 2024-02-29 10:32:36 UTC

(I see the package is not in f38, so ignore that part)