Bug#879057: mpv: FTBFS against libva 2.0

[Sebastian Ramacher]

Source: mpv
Version: 0.27.0-1
Severity: important
Tags: sid buster upstream fixed-upstream

mpv FTBFS against the upcoming libva 2.0 (a pre-release is currently available
in experimental):
| ../video/vaapi.c: In function 'va_initialize':
| ../video/vaapi.c:191:5: error: too few arguments to function 'vaSetErrorCallback'
| vaSetErrorCallback(va_error_callback);
| ^~~~~~~~~~~~~~~~~~
| In file included from ../video/vaapi.h:24:0,
| from ../video/vaapi.c:22:
| /usr/include/va/va.h:270:19: note: declared here
| VAMessageCallback vaSetErrorCallback(VADisplay dpy, VAMessageCallback callback, void *user_context);
| ^~~~~~~~~~~~~~~~~~
| ../video/vaapi.c:192:5: error: too few arguments to function 'vaSetInfoCallback'
| vaSetInfoCallback(va_info_callback);
| ^~~~~~~~~~~~~~~~~
| In file included from ../video/vaapi.h:24:0,
| from ../video/vaapi.c:22:
| /usr/include/va/va.h:276:19: note: declared here
| VAMessageCallback vaSetInfoCallback(VADisplay dpy, VAMessageCallback callback, void *user_context);
| ^~~~~~~~~~~~~~~~~

A fix is available upstream in
https://github.com/mpv-player/mpv/commit/2ecf240b1cd20875991a5b18efafbe799864ff7f

Cheers

-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (650, 'unstable-debug'), (650, 'buildd-unstable'), (650, 'unstable'), (601, 'testing'), (600, 'experimental-debug'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[Debian Bug Tracking System]

Your message dated Sat, 21 Oct 2017 12:49:21 +0000
with message-id <E1e5tDN-00069s-***@fasolo.debian.org>
and subject line Bug#879057: fixed in mpv 0.27.0-2
has caused the Debian Bug report #879057,
regarding mpv: FTBFS against libva 2.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)