Bug 603110 - Update gstreamer-plugins-bad-free to F13 for WebM
Update gstreamer-plugins-bad-free to F13 for WebM
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gstreamer-plugins-bad-free (Show other bugs)
6.0
All Linux
low Severity medium
: rc
: ---
Assigned To: Benjamin Otte
desktop-bugs@redhat.com
: Rebase
Depends On: 603113
Blocks: 603100
  Show dependency treegraph
 
Reported: 2010-06-11 10:44 EDT by Benjamin Otte
Modified: 2010-11-10 15:36 EST (History)
5 users (show)

See Also:
Fixed In Version: gstreamer-plugins-bad-free-0.10.19-2.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-10 15:36:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Benjamin Otte 2010-06-11 10:44:17 EDT
The GStreamer bad-free plugins package needs to be updated to support WebM.
Comment 2 RHEL Product and Program Management 2010-06-11 11:52:55 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 4 Benjamin Otte 2010-06-30 12:40:23 EDT
Rebuilt gstreamer-plugins-bad-free with libvpx support now that it was imported.
Comment 6 Vladimir Benes 2010-07-02 09:10:11 EDT
can play http://people.opera.com/howcome/2010/video/norway/00313-n.webm successfully in Totem
-> VERIFIED
Comment 7 releng-rhel@redhat.com 2010-11-10 15:36:54 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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