On Fri, Dec 5, 2014 at 10:32 PM, Bigby James <bigby.james@crepcran.com> wrote:
Isn't this something that would get fixed on release? That is, wouldn't the version of mpv in [community] be rebuilt upon the release of the new ffmpeg version to [extra]? [community] packages are just one small step above the AUR, while [testing] only contains individual, official packages awaiting release, not a package plus everything that depends on it.. As I understand it, this sort of thing is inevitable and invariable when using [testing]. I'd say contact the TU responsible for the package and ask what the normal procedure for this is before filing a bug report.[1] If you already filed one, it might be worth contacting the maintainer just to see what standard practice is in these situations.
[1]: https://www.archlinux.org/packages/community/x86_64/mpv/
Since Florian Fritz is a dev, I trust him to know what he's talking about. https://www.archlinux.org/people/developers/#bluewind https://lists.archlinux.org/pipermail/arch-general/2014-December/037920.html