Bug 1908229

Summary:	python-colcon-ros-bundle-0.1.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	python-colcon-ros-bundle	Assignee:	Scott K Logan <logans>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	logans
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-colcon-ros-bundle-0.1.0-1.fc32 python-colcon-ros-bundle-0.1.0-1.el8 python-colcon-ros-bundle-0.1.0-1.el7 python-colcon-ros-bundle-0.1.0-1.fc33	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-26 01:18:46 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-12-16 06:58:39 UTC

Latest upstream release: 0.1.0
Current version/release in rawhide: 0.0.14-3.fc33
URL: https://github.com/colcon/colcon-ros-bundle

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

Comment 1 Upstream Release Monitoring 2020-12-16 06:58:51 UTC

An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 2 Fedora Update System 2020-12-17 21:11:39 UTC

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

Comment 3 Fedora Update System 2020-12-17 21:11:45 UTC

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

Comment 4 Fedora Update System 2020-12-17 21:12:31 UTC

FEDORA-EPEL-2020-6c6c7a90ab has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6c6c7a90ab

Comment 5 Fedora Update System 2020-12-17 21:12:36 UTC

FEDORA-EPEL-2020-6c6c7a90ab has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6c6c7a90ab

Comment 6 Fedora Update System 2020-12-17 21:14:38 UTC

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

Comment 7 Fedora Update System 2020-12-17 21:14:43 UTC

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

Comment 8 Fedora Update System 2020-12-17 21:15:21 UTC

FEDORA-EPEL-2020-3cd491ab4c has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-3cd491ab4c

Comment 9 Fedora Update System 2020-12-17 21:15:26 UTC

FEDORA-EPEL-2020-3cd491ab4c has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-3cd491ab4c

Comment 10 Fedora Update System 2020-12-18 01:14:03 UTC

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

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

Comment 11 Fedora Update System 2020-12-18 01:26:30 UTC

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

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

Comment 12 Fedora Update System 2020-12-18 01:30:31 UTC

FEDORA-EPEL-2020-6c6c7a90ab has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6c6c7a90ab

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

Comment 13 Fedora Update System 2020-12-18 01:41:18 UTC

FEDORA-EPEL-2020-3cd491ab4c 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-2020-3cd491ab4c

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

Comment 14 Fedora Update System 2020-12-26 01:18:46 UTC

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

Comment 15 Fedora Update System 2021-01-02 00:34:53 UTC

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

Comment 16 Fedora Update System 2021-01-02 00:56:11 UTC

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

Comment 17 Fedora Update System 2021-01-05 01:25:41 UTC

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