Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1406039 - Installed (but unpackaged) file(s) found
Installed (but unpackaged) file(s) found
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gstreamer1-plugins-bad-free (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity low
: rc
: ---
Assigned To: Wim Taymans
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-12-19 09:37 EST by Tomas Pelka
Modified: 2017-08-01 18:24 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 18:24:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2060 normal SHIPPED_LIVE Moderate: GStreamer security, bug fix, and enhancement update 2017-08-01 15:34:49 EDT

  None (edit)
Description Tomas Pelka 2016-12-19 09:37:08 EST
Description of problem:


Version-Release number of selected component (if applicable):
gstreamer1-plugins-bad-free-1.4.5-6.el7_3

How reproducible:
100%

Steps to Reproduce:
1. rpmbuild
2.
3.

Actual results:
error: Installed (but unpackaged) file(s) found:
   /usr/lib64/gstreamer-1.0/libgstcurl.so
   /usr/lib64/gstreamer-1.0/libgstopenexr.so
   /usr/lib64/gstreamer-1.0/libgstvdpau.so

Expected results:


Additional info:
Comment 2 Wim Taymans 2017-03-09 10:12:15 EST
The number of plugins built depends on what libraries are present in the buildroot. We explicitly disable those plugins from building by not specifying a buildrequirement. We could also explicitly use --disable-<foo>
Comment 4 errata-xmlrpc 2017-08-01 18:24:34 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2060

Note You need to log in before you can comment on or make changes to this bug.