Bug#803822: gst-libav1.0: FTBFS with FFmpeg 2.9

Andreas Cadhalpun andreas.cadhalpun at googlemail.com
Mon Jan 18 23:14:15 UTC 2016

Control: tag -1 fixed-upstream

Hi Sebastian,

On 18.01.2016 08:21, Sebastian Dröge wrote:
> I was bored at the airport on Saturday and merged all but one of the
> patches upstream now plus two additional ones. Take a look at the
> upstream bug report for details.

That's great! (I'm glad it helped relieve your boredom. ;)

> This now works with 2.8 and ffmpeg git master just fine without
> possibly breaking with either version. Let me know if you still see
> anything problematic.

I cherry-picked these four patches onto 1.6.2-1 (in sid) and it
built fine with ffmpeg git master.

However, I don't understand your reasoning for not applying the patch
removing use of FF_API_EMU_EDGE.
It's only used in ffmpeg for backwards compatibility and thus removing
this from gst-libav1.0 now should work fine.
Or did you encounter any problems?

It would be nice to apply this patch now, as it seems to be the only
API still used by gst-libav1.0, which is going to be removed on the next
soversion bump.

For the bump after the next one, there are some more deprecated APIs
to deal with:

Just mentioning it, in case you get bored again. ;)

>>> testing will be easier once there are packages though.
>> How so? The replacements of the deprecated APIs have been present
>> for years, so you can test the patch with any recent version.
>> Once the new version is packaged, it will be a bit late to start
>> investigating this bug, as gst-libav1.0 will fail to build then.
> Well, at that point it would be easier to fix than building all of
> ffmpeg myself, right? :)

Except that you don't need to build ffmpeg yourself to fix this. :)

What remains is to get a fixed gst-libav1.0 version into sid.
Can you give an estimate, when this will happen?

Best regards,

More information about the pkg-gstreamer-maintainers mailing list