Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1086199

Summary:	PackageKit-gstreamer-plugin: Bogus "Requires: gstreamer" (should be "gstreamer1" or just rely on the autoreq)
Product:	[Fedora] Fedora	Reporter:	Kevin Kofler <kevin>
Component:	PackageKit	Assignee:	Kevin Kofler <kevin>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	jonathan, rdieter, rhughes, smparrish
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	PackageKit-0.9.1-2.fc21	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-29 15:56:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	661442

Description Kevin Kofler 2014-04-10 10:51:18 UTC

Description of problem:
PackageKit-gstreamer-plugin in Rawhide is built against GStreamer 1, but still has a hardcoded "Requires: gstreamer" that drags in 0.10.

Version-Release number of selected component (if applicable):
PackageKit-gstreamer-plugin-0.9.1-1.fc21

How reproducible:
Always

Steps to Reproduce:
1. Install PackageKit-gstreamer-plugin.

Actual results:
GStreamer 0.10 is required.

Expected results:
GStreamer 0.10 is not required anymore.

Additional info:
The BuildRequires were changed to gstreamer1-* on March 24, but the Requires was apparently forgotten.

Comment 1 Richard Hughes 2014-04-10 15:52:54 UTC

Yup, can you please just fix this in the spec and I'll do a build/update for the next PK release. Thanks!

Comment 2 Kevin Kofler 2014-04-29 15:56:34 UTC

This has been fixed since 0.9.1-2.