Bug 1243615
| Summary: | gstreamer1-vaapi-0.6.0 is available | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||
| Component: | gstreamer1-vaapi | Assignee: | Simon Farnsworth <simon> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | belegdol, fraph24, kwizart, moez.roy, simon | ||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | 1.6.0-1.fc23 | Doc Type: | Enhancement | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-08-20 19:49:38 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1239152 | ||||||||
| Attachments: |
|
||||||||
|
Description
Upstream Release Monitoring
2015-07-16 00:13:06 UTC
Created attachment 1052497 [details]
[patch] Update to 0.6.0 (#1243615)
Scratch build failed http://koji.fedoraproject.org/koji/taskinfo?taskID=10372385 Patch 0001-window-Correct-prototype-to-match-implementation.patch (Patch1) should be removed. It's not needed anymore, as you can see from this line of code: https://github.com/01org/gstreamer-vaapi/blob/0.6.0/gst-libs/gst/vaapi/gstvaapiwindow_priv.h#L121 Created attachment 1053324 [details] Version bump; remove unnecessary patch F24/rawhide: http://koji.fedoraproject.org/koji/taskinfo?taskID=10398028 F22 build: http://koji.fedoraproject.org/koji/taskinfo?taskID=10398032 kwizart's gstreamer1-vaapi-0.6.0-1.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=675261 gstreamer1-vaapi-0.6.0-1.fc23, libva-1.6.0-1.fc23 has been submitted as an update for Fedora 23. https://admin.fedoraproject.org/updates/gstreamer1-vaapi-0.6.0-1.fc23,libva-1.6.0-1.fc23 Package gstreamer1-vaapi-0.6.0-1.fc23, libva-1.6.0-1.fc23: * should fix your issue, * was pushed to the Fedora 23 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gstreamer1-vaapi-0.6.0-1.fc23 libva-1.6.0-1.fc23' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-12736/gstreamer1-vaapi-0.6.0-1.fc23,libva-1.6.0-1.fc23 then log in and leave karma (feedback). Are there plans to push it to F-22 and F-21 at a later stage? Current gstreamer1-vaapi does not work with totem at all: https://bugzilla.gnome.org/show_bug.cgi?id=743687 this bug leads to https://bugzilla.gnome.org/show_bug.cgi?id=744039 which leads to https://bugzilla.gnome.org/show_bug.cgi?id=744618 The fix for the last one is included in 0.6.0 meaning that accelerated playback works again. No, I don't plan to update gst1/libva because there is vaapi changes that will trigger ffmpeg dependency that ends to trigger the whole multimedia stack. So unless you have identified the patch to backport, I'm not going to consider a version change. 9799875, e4f8d14 and 3d8e5e5 are required as a minimum it seems. I am not sure how easy backporting will be though. When testing those I ended up running the git master in the end, but I am afraid I do not remember whether it was because of backporting difficulties or another reason. How about updating gstreamer1-vaapi alone and leaving libva at 1.5.1? I have been doing it for the last few weeks and it seems to work. gstreamer1-vaapi-0.6.0-1.fc23, libva-1.6.0-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. |