Description of problem:
The libva project has moved from freedesktop.org to github.com. Update the .spec file accordingly.
Created attachment 1246040 [details]
Here is my attempt to update the source in the spec file.
Thx for the report.
I don't get the point to use dh-autoreconf package over autoreconf script which is distro agnostic.
When extracting the libva archive from github I have libva-libva-1.7.3 instead of libva-1.7.3, seems something is broken here.
Can you fix it ?
Also I seems weird that some files have changes from the 1.7.3 tag release (not speaking about autotools removal, but also test cases, etc).
I'm a Libva maintainer at Intel (firstname.lastname@example.org). The next release tag will be 1.8.0 and that will correct the oddity with Github double labeling the archive. You can actually rename using curl/wget as a part of the checkout anyway, but I will ensure the release tag will be numbers and not include the actual project name. I suggest you don't update the package *until* I release 1.8.0.
The test folder is gone and I've created a new project libva-utils. The next release of 1.8.0 will no longer have a test folder or the tests/apps that were inside it.
We can submit a spec file for that project for the 1.8.0 release.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
(In reply to Nicolas Chauvet (kwizart) from comment #2)
> Thx for the report.
> I don't get the point to use dh-autoreconf package over autoreconf script
> which is distro agnostic.
Just a simple misunderstanding of mine when making the file. I'll take that out.
> Also I seems weird that some files have changes from the 1.7.3 tag release
> (not speaking about autotools removal, but also test cases, etc).
Like Sean mentioned, some of the utilities got moved from libva to libva-utils. Shall we create a new package for that?
Done by Nicolas: http://pkgs.fedoraproject.org/cgit/rpms/libva.git/commit/?id=a336507eb3b4522bb070c540fb769a2b1f704a5c