Package Details: mpv-git 0.32.0_779_gcbbdb3fae4-1

Git Clone URL: (read-only, click to copy)
Package Base: mpv-git
Description: Video player based on MPlayer/mplayer2 (git version)
Upstream URL:
Keywords: media player video
Licenses: GPL
Conflicts: mpv
Provides: mpv
Submitter: rpolzer
Maintainer: qmega
Last Packager: qmega
Votes: 203
Popularity: 0.189063
First Submitted: 2012-12-04 09:21
Last Updated: 2020-10-16 21:46

Required by (175)

Sources (3)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

qmega commented on 2020-10-16 21:48

@misc: Yeah, noexec on the filesystem you cloned to would do it. Wouldn't affect waf because prepare() is copying that so it's actually residing on /tmp's filesystem.

I've made the change you suggested.

Thanks for following up.

misc commented on 2020-10-16 19:29

@qmega: no noexec for /tmp and no issues with python3 either.

The full error is: /mnt/build/mpv-git/PKGBUILD: line 140: /tmp/makepkg/mpv-git/src/ Permission denied

(Re. python or python3, I have no preference.)

edit: noexec is however set for the partition that the PKGBUILD & co. reside on, and since the on /tmp is only a symlink, I'm guessing that's the cause.

qmega commented on 2020-10-10 00:51

@misc That's strange. I compile in tmpfs too and I haven't had problems like that. The only thing that comes to mind is having it mounted noexec, but I don't think it's that because then it would have failed on ./waf before it got to that line. there some chance that /usr/bin/python3 isn't executable? That would probably result in the same error message as the interpreted file itself not being executable. I'm trying to think of what else could cause a permission error and I can't think of much. What exactly is the error you get?

I'm not opposed to calling python as you propose (though I think I'd call python3) if it solves a real problem, but I'd like to understand what's going on first.

misc commented on 2020-10-09 17:21

Line 139 should probably be changed to call the script like $(python "$srcdir"/, otherwise it can fail to execute due to insufficient permissions (for people like me; guessing it's since I compile in tmpfs).

qmega commented on 2020-07-16 06:17


Why are the options not desirable? They seem useful to me and were requested in the past. The only practical downside I see is that on the first install, the user may have to explicitly enable something that the community package had by default -- but that only has to be done once. Depending on those by default would mean that people who didn't want those dependencies -- e.g. someone who used only Wayland and didn't want to install X libraries -- would have to remove them every time, or live with them. With a binary package there has to be a compromise, but I don't see the need for that here.

The majority of mpv's optional features are enabled by default if their dependencies are present, so there's no need to explicitly enable them every time. All one has to do is install them before (re)building the package. I imagine that in many cases, the dependencies for what you want would be installed already. Whatever is linked in will be picked up as dependencies of the package when it's built.

Are there specific problems that the current setup of this package is causing?

qmega commented on 2020-07-16 05:53

@haawda I can't reproduce that. Tried with LANG=de_DE.UTF-8 and LANG=de_DE.ISO-8859-1. What are your LANG / LC_* settings and what error do you get? Or, maybe consider opening an issue upstream. Even if it is just an issue on your system, GitHub is probably a better medium for debugging than here.

SirCmpwn commented on 2020-07-11 18:01

This package should more closely map to the mpv package in community, i.e. the default build should use an identical build config to mpv. The "optional" features in the PKGBUILD are not really desirable.

haawda commented on 2020-07-08 19:52

I needed to add LANG=C to the build function, otherwise build would fail with a linking error.

qmega commented on 2019-10-31 01:35

@ekce Sounds like it could be which was fixed today. I can reproduce the crash with that commit reverted and --gpu-api=opengl, but with master as of this writing it's fine. Try again?

If it's still broken for you, open an issue upstream. Even if it ends up being a problem with your system and not a bug in mpv, that's probably a better place to figure it out. AUR comments aren't great for debugging.

ekce commented on 2019-10-30 16:20

See the comments on mpv-build-git. It's possible that the most recent build has a bug that causes it to crash right after starting up.