Bug 1591989

Summary:	bcc-v0.6.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	bcc	Assignee:	Jiri Olsa <jolsa>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	jolsa, myllynen, rdossant, skozina
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	bcc-0.6.0-1.fc28 bcc-0.6.1-1.fc27	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-03 16:49:45 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 2018-06-16 00:12:16 UTC

Latest upstream release: v0.6.0
Current version/release in rawhide: 0.4.0-3.fc28
URL: https://github.com/iovisor/bcc

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/12803/

Comment 1 Fedora Update System 2018-06-18 12:54:36 UTC

bcc-0.6.0-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-afd3437ae7

Comment 2 Fedora Update System 2018-06-18 17:08:54 UTC

bcc-0.6.0-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-afd3437ae7

Comment 3 Marko Myllynen 2018-07-03 09:23:52 UTC

Since there have been some API changes in 0.6.0 it would be nice if 0.6.0 could be pushed to Fedora 27 as well so that Fedora 27/28 would have the same API. Let me know if you want a separate BZ for that. Thanks.

Comment 4 Fedora Update System 2018-07-03 11:33:01 UTC

bcc-0.6.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7bb6a8f439

Comment 5 Fedora Update System 2018-07-03 16:49:45 UTC

bcc-0.6.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2018-07-04 16:22:04 UTC

bcc-0.6.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-7bb6a8f439

Comment 7 Fedora Update System 2018-08-22 21:39:08 UTC

bcc-0.6.1-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-fe11e67638

Comment 8 Fedora Update System 2018-08-23 08:34:27 UTC

bcc-0.6.1-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-fe11e67638

Comment 9 Fedora Update System 2018-08-31 20:04:29 UTC

bcc-0.6.1-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.