Bug 2254519 - rust-bankstown-lv2-1.0.2 is available
Summary: rust-bankstown-lv2-1.0.2 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-bankstown-lv2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rust SIG
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-14 10:24 UTC by Upstream Release Monitoring
Modified: 2023-12-15 02:18 UTC (History)
3 users (show)

Fixed In Version: rust-bankstown-lv2-1.0.2-1.fc40 rust-bankstown-lv2-1.0.2-1.fc39 rust-bankstown-lv2-1.0.2-1.fc38
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-14 22:51:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2023-12-14 10:24:55 UTC
Releases retrieved: 1.0.1
Upstream release that is considered latest: 1.0.1
Current version/release in rawhide: 1.0.0-2.fc40
URL: https://crates.io/crates/bankstown-lv2

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


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

Comment 1 Upstream Release Monitoring 2023-12-14 22:34:41 UTC
Releases retrieved: 1.0.2
Upstream release that is considered latest: 1.0.2
Current version/release in rawhide: 1.0.0-2.fc40
URL: https://crates.io/crates/bankstown-lv2

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


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

Comment 2 Fedora Update System 2023-12-14 22:48:04 UTC
FEDORA-2023-e2e0923713 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e2e0923713

Comment 3 Fedora Update System 2023-12-14 22:51:08 UTC
FEDORA-2023-e2e0923713 has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2023-12-14 23:06:25 UTC
FEDORA-2023-ba4eacd7df has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ba4eacd7df

Comment 5 Fedora Update System 2023-12-14 23:22:38 UTC
FEDORA-2023-cce782fab4 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-cce782fab4

Comment 6 Fedora Update System 2023-12-15 01:32:51 UTC
FEDORA-2023-ba4eacd7df has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2023-12-15 02:18:46 UTC
FEDORA-2023-cce782fab4 has been pushed to the Fedora 38 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.