Bug 2249583

Summary: pygrib-2.1.5 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: pygribAssignee: Jos de Kloe <josdekloe>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: josdekloe
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pygrib-2.1.5-1.fc39 pygrib-2.1.5-1.fc38 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-17 10:54:04 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:
Attachments:
Description Flags
Update to 2.1.5 (#2249583) none

Description Upstream Release Monitoring 2023-11-14 03:08:58 UTC 
Releases retrieved: 2.1.5
Upstream release that is considered latest: 2.1.5
Current version/release in rawhide: 2.1.4-9.fc39
URL: https://pypi.python.org/pypi/pygrib

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/pygrib
Comment 1 Upstream Release Monitoring 2023-11-14 03:09:06 UTC 
Created attachment 1999227 [details]
Update to 2.1.5 (#2249583)
Comment 2 Upstream Release Monitoring 2023-11-14 03:18:19 UTC 
the-new-hotness/release-monitoring.org's scratch build of pygrib-2.1.5-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=109000334
Comment 3 Fedora Update System 2023-11-17 10:52:48 UTC 
FEDORA-2023-f5e2b6085e has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f5e2b6085e
Comment 4 Fedora Update System 2023-11-17 10:53:16 UTC 
FEDORA-2023-da50fd4e55 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-da50fd4e55
Comment 5 Fedora Update System 2023-11-18 02:41:17 UTC 
FEDORA-2023-da50fd4e55 has been pushed to the Fedora 39 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-da50fd4e55`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-da50fd4e55

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2023-11-18 02:47:43 UTC 
FEDORA-2023-f5e2b6085e has been pushed to the Fedora 38 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-f5e2b6085e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f5e2b6085e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2023-11-26 01:55:05 UTC 
FEDORA-2023-da50fd4e55 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 8 Fedora Update System 2023-11-26 03:04:57 UTC 
FEDORA-2023-f5e2b6085e has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.