Bug 1901339

Summary:	pygrib-2.0.5 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	pygrib	Assignee:	Jos de Kloe <josdekloe>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	josdekloe
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pygrib-2.0.5-1.fc32 pygrib-2.0.5-1.fc33	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-05 01:15:34 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 2020-11-24 21:57:18 UTC

Latest upstream release: 2.0.5
Current version/release in rawhide: 2.0.4-7.fc33
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://fedoraproject.org/wiki/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/

Comment 1 Upstream Release Monitoring 2020-11-24 21:57:22 UTC

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-on6z3im9/pygrib.spec'] returned 1: b'error: Bad source: ./pygrib-2.0.5-build.patch: No such file or directory\n'

Comment 2 Fedora Update System 2020-11-26 12:26:12 UTC

FEDORA-2020-ab906e673b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ab906e673b

Comment 3 Fedora Update System 2020-11-26 12:26:54 UTC

FEDORA-2020-f9270f9051 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f9270f9051

Comment 4 Fedora Update System 2020-11-27 02:10:42 UTC

FEDORA-2020-f9270f9051 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f9270f9051`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f9270f9051

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

Comment 5 Fedora Update System 2020-11-27 02:18:44 UTC

FEDORA-2020-ab906e673b has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ab906e673b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ab906e673b

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

Comment 6 Fedora Update System 2020-12-05 01:15:34 UTC

FEDORA-2020-ab906e673b has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2020-12-05 01:39:03 UTC

FEDORA-2020-f9270f9051 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.