Bug 2166844

Summary: rust-difftastic-0.43.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: rust-difftasticAssignee: Rust SIG <rust-sig>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: michel, rust-sig
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rust-difftastic-0.43.1-1.fc36 rust-difftastic-0.43.1-1.el9 rust-difftastic-0.43.1-1.el8 rust-difftastic-0.43.1-1.fc37 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-24 03:46:15 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 2023-02-03 07:17:02 UTC
Releases retrieved: 0.43.0
Upstream release that is considered latest: 0.43.0
Current version/release in rawhide: 0.42.0-2.fc38
URL: https://crates.io/crates/difftastic

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


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

Comment 1 Upstream Release Monitoring 2023-02-04 23:42:21 UTC
Releases retrieved: 0.43.1
Upstream release that is considered latest: 0.43.1
Current version/release in rawhide: 0.42.0-3.fc38
URL: https://crates.io/crates/difftastic

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


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

Comment 2 Fedora Update System 2023-02-15 21:27:47 UTC
FEDORA-2023-5f155743b4 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5f155743b4

Comment 3 Fedora Update System 2023-02-15 21:27:49 UTC
FEDORA-EPEL-2023-6f8e40e18e has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6f8e40e18e

Comment 4 Fedora Update System 2023-02-15 21:27:50 UTC
FEDORA-2023-3aaa325941 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3aaa325941

Comment 5 Fedora Update System 2023-02-16 02:23:32 UTC
FEDORA-2023-5f155743b4 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5f155743b4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5f155743b4

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

Comment 6 Fedora Update System 2023-02-16 02:34:54 UTC
FEDORA-EPEL-2023-6f8e40e18e 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-2023-6f8e40e18e

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

Comment 7 Fedora Update System 2023-02-16 02:36:34 UTC
FEDORA-2023-3aaa325941 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3aaa325941`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3aaa325941

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

Comment 8 Fedora Update System 2023-02-16 02:47:36 UTC
FEDORA-EPEL-2023-4c143ba851 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-4c143ba851

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

Comment 9 Fedora Update System 2023-02-24 03:46:15 UTC
FEDORA-2023-5f155743b4 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2023-02-24 04:12:01 UTC
FEDORA-EPEL-2023-6f8e40e18e has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2023-02-24 04:42:35 UTC
FEDORA-EPEL-2023-4c143ba851 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2023-02-24 04:45:10 UTC
FEDORA-2023-3aaa325941 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.