Summary: | media-libs/libvpx-1.3.0 stable request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mike Gilbert <floppym> |
Component: | [OLD] Keywording and Stabilization | Assignee: | Gentoo Media-video project <media-video> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alex_y_xu, chromium, pacho |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 501010 | ||
Bug Blocks: | 499954, 502094 |
Description
Mike Gilbert
2014-02-20 00:47:34 UTC
According to upstream, this version has "blocking issues" or "bugs" or somesuch: https://code.google.com/p/webm/issues/detail?id=688 https://code.google.com/p/webm/issues/detail?id=648 and claims that 1.3.1 will be released soon... as of Dec 2013. Probably not worth waiting for if chromium is using 1.3.0 as is though. Well, I suppose we could always do bundled libvpx for the Chromium 33 release, and switch back to system libvpx for Chromium 34. (In reply to Mike Gilbert from comment #2) > Well, I suppose we could always do bundled libvpx for the Chromium 33 > release, and switch back to system libvpx for Chromium 34. Actually I consider Gentoo blocking bugs more serious than these. Note that libvpx is part of chromium herd, we can fix things, I just didn't have cycles for that. (In reply to Paweł Hajdan, Jr. from comment #3) The Gentoo blockers should be resolved. Any objections to stabilizing? (In reply to Mike Gilbert from comment #4) > The Gentoo blockers should be resolved. Any objections to stabilizing? Arches please go ahead. The target is =media-libs/libvpx-1.3.0 amd64 stable x86 stable Stable for HPPA. ppc stable USE=avx2 doesn't seem to be masked correctly at least for arm profile: # emerge -1 =media-libs/libvpx-1.3.0 -pv These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ~] media-libs/libvpx-1.3.0 [1.1.0] USE="{test%*} threads (-altivec) (-avx) -avx2% -doc (-mmx) -postproc (-sse) (-sse2) (-sse3) (-sse4_1) (-ssse3) -static-libs (-debug%)" 0 kB (In reply to Markus Meier from comment #10) Fixed. arm stable ia64 stable sparc is also needed for gst-plugins-vpx (needed by cheese). The problem is that the keyword was dropped silently, I see no reference in changelog, neither a rekeyword bug report... and we have now a ugly mix of sparc keywords for some versions and not others :/ If it's due bug 501010, looks like it has a fix, but I don't know if it was really the culprit :/ (In reply to Pacho Ramos from comment #14) > sparc is also needed for gst-plugins-vpx (needed by cheese). The problem is > that the keyword was dropped silently, I see no reference in changelog, > neither a rekeyword bug report... and we have now a ugly mix of sparc > keywords for some versions and not others :/ libvpx-1.3.0 was never keyworded sparc in g-x86. currently, 1.1.0 has ~sparc, that's it. In general, when a keyword is dropped on a new version, some note is added explaining what occurred and a bug asking for rekeywording is opened (at least for cases like this where lib cannot be slotted) My guess is that aballier copied libvpx-9999 to libvpx-1.2.0_pre20130625.ebuild. libvpx-9999 never had the ~sparc keyword added, so it got lost by accident. Let's get confirmation on bug 501010, and then ask sparc to keyword/stable libvpx-1.3.0. sparc stable ppc64 stable alpha stable. Closing. |