Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-65086
On Fri, Feb 02, 2018 at 11:37:19AM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Well, getting chromium fixed would be the first big step here. Then we can
> prod upstreams to use a new chromium version.
This patch from upst
El viernes, 2 de febrero de 2018 11:05:36 -03 James Cowgill escribió:
[snip]
> > Hi James! Qt upstreams will certainly not start developing against a new
> > FFmpeg version until it gets released.
>
> Having FFmpeg 3.5 released is not a prerequisite to fix this. All the
> old APIs in FFmpeg 3.5 ha
Hi,
On 02/02/18 13:50, Lisandro Damián Nicanor Pérez Meyer wrote:
> El miércoles, 24 de enero de 2018 19:26:50 -03 jcowg...@debian.org escribió:
>> Source: qtwebengine-opensource-src
>> Version: 5.9.2+dfsg-2
>> Severity: important
>> User: debian-multime...@lists.debian.org
>> Usertags: ffmpeg-3.5
El miércoles, 24 de enero de 2018 19:26:50 -03 jcowg...@debian.org escribió:
> Source: qtwebengine-opensource-src
> Version: 5.9.2+dfsg-2
> Severity: important
> User: debian-multime...@lists.debian.org
> Usertags: ffmpeg-3.5-transition
>
> Hi,
>
> Your package FTBFS with the upcoming version 3.5
4 matches
Mail list logo