Package Details: libva-git 2.17.0.r24.g97cbc87c-1

Git Clone URL: https://aur.archlinux.org/libva-git.git (read-only, click to copy)
Package Base: libva-git
Description: Video Acceleration (VA) API for Linux (git version)
Upstream URL: https://01.org/linuxmedia/vaapi/
Licenses: MIT
Conflicts: libva
Provides: libva, libva-drm.so, libva-glx.so, libva-wayland.so, libva-x11.so, libva.so
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 7
Popularity: 0.000002
First Submitted: 2017-12-26 15:09 (UTC)
Last Updated: 2023-02-25 15:17 (UTC)

Required by (281)

Sources (1)

Latest Comments

eclairevoyant commented on 2023-02-25 19:23 (UTC)

Thanks for the explanation and looking into this. I forgot git tags are added after the versioned releases.

dbermond commented on 2023-02-25 15:26 (UTC)

@eclairevoyant Package updated. By using upstream source files for getting pkgver (like meson files), we will get a future git tag. For reflecting the current version, it's better to use the current git tag plus a revision number, as described in the Arch Wiki. Anyway, thanks for the suggestion and for pointing this. Now the package better reflects the upstream version.

eclairevoyant commented on 2023-02-23 21:08 (UTC) (edited on 2023-02-23 21:23 (UTC) by eclairevoyant)

I don't think this PKGBUILD is producing the correct pkgver. If I run this I get 2.11.0.pre1.r145.g97cbc87c but upstream is already on 2.18.0.pre1.

As per upstream's meson.build file, I think it makes more sense to parse that since that's what the build process does.

I would suggest something akin to the following (yes, awk could do what tr is doing but I didn't want to include some rather tortured string quoting):

pkgver() {
    cd "$_srcname"
    git blame -s -L"/version :/,+1" meson.build | tr -d "'," | awk '{
        ver = gensub(/\./,".pre",3,$5);
        "git rev-list --count "$1"..HEAD" | getline commit_count;
        print ver".r"commit_count"."$1
    }'
}

This produces the expected version 2.18.0.pre1.r5.0cae15ff3.

EDIT: I also imagine you'd need to make a similar change to the other libva-* packages you maintain since upstream isn't tagging stuff properly.

dbermond commented on 2017-12-29 14:45 (UTC)

@laichiaheng I cannot reproduce your issue. Package is building fine for me.

Try to build it in a chroot.

laichiaheng commented on 2017-12-29 14:02 (UTC) (edited on 2017-12-29 14:25 (UTC) by laichiaheng)

error after changing the source:

make[3]: *** [Makefile:505: libva_display_la-va_display_wayland.lo] Error 1

make[3]: *** Waiting for unfinished jobs....

make[3]: Leaving directory '/tmp/yaourt-tmp-laichiaheng/aur-libva-git/src/libva-git/test/common'

make[2]: *** [Makefile:413: all-recursive] Error 1

make[2]: Leaving directory '/tmp/yaourt-tmp-laichiaheng/aur-libva-git/src/libva-git/test'

make[1]: *** [Makefile:467: all-recursive] Error 1

make[1]: Leaving directory '/tmp/yaourt-tmp-laichiaheng/aur-libva-git/src/libva-git'

make: *** [Makefile:399: all] Error 2

==> ERROR: A failure occurred in build().

Aborting...

==> ERROR: Makepkg was unable to build libva-git.

laichiaheng commented on 2017-12-29 13:58 (UTC)

Because I'm not sure if it is out of date.

dbermond commented on 2017-12-28 15:44 (UTC)

@laichiaheng yes, there is. Use this as the source: 'git+https://github.com/01org/libva.git#tag=libva-1.1.0'.

By the way, the package is not out of date. I don't know why you flagged it.

laichiaheng commented on 2017-12-28 15:40 (UTC) (edited on 2017-12-28 15:40 (UTC) by laichiaheng)

Is there any way to enable VA version 1.1.0?