Bug 1882632

Summary:	python-gattlib-0.20200925 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	python-gattlib	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	gwync
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-gattlib-0.20200925-1.fc33 python-gattlib-0.20200929-1.fc32	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-29 00:16:42 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-09-25 08:25:03 UTC

Latest upstream release: 0.20200925
Current version/release in rawhide: 0.20200915-1.fc34
URL: https://bitbucket.org/OscarAcena/pygattlib

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

Comment 1 Upstream Release Monitoring 2020-09-25 08:25:12 UTC

The following Sources of the specfile are not valid URLs so we cannot automatically build the new version for you.  Please use URLs in your Source declarations if possible.

- COPYING

Comment 2 Fedora Update System 2020-09-25 14:25:55 UTC

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

Comment 3 Fedora Update System 2020-09-25 18:13:23 UTC

FEDORA-2020-893110e744 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-893110e744`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-893110e744

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

Comment 4 Fedora Update System 2020-09-25 18:35:47 UTC

FEDORA-2020-7667471443 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-7667471443`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7667471443

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

Comment 5 Fedora Update System 2020-09-29 00:16:42 UTC

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

Comment 6 Fedora Update System 2020-09-30 01:21:54 UTC

FEDORA-2020-ccfe0be015 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-ccfe0be015`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ccfe0be015

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

Comment 7 Fedora Update System 2020-10-07 20:36:29 UTC

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