Summary: | configure: error: Package requirements (libva >= 0.34) were not met | ||
---|---|---|---|
Product: | libva | Reporter: | U. Artie Eoff <ullysses.a.eoff> |
Component: | intel | Assignee: | haihao <haihao.xiang> |
Status: | VERIFIED FIXED | QA Contact: | Sean V Kelley <seanvk> |
Severity: | critical | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
U. Artie Eoff
2013-11-06 15:08:20 UTC
Quite strange that yesterday my automated build found HEAD commit 73a11b3e24 from libva master which had the correct api version (0.34). Now, I can't find that commit in libva on any of its branches after updating... "git branch --contains 73a11b3e24" turns up nothing! However, since I had a local copy of libva, I am still able to "git checkout 73a11b3e24" in detached state just fine which means it was there at some point. What kind of git voodoo are the maintainers casting on libva tree? (In reply to comment #1) > Quite strange that yesterday my automated build found HEAD commit 73a11b3e24 > from libva master which had the correct api version (0.34). Now, I can't > find that commit in libva on any of its branches after updating... "git > branch --contains 73a11b3e24" turns up nothing! However, since I had a > local copy of libva, I am still able to "git checkout 73a11b3e24" in > detached state just fine which means it was there at some point. What kind > of git voodoo are the maintainers casting on libva tree? So it looks like the libva "master" branch has been restored to its earlier state (73a11b3e24) now. Anyone care to comment here about what was done to fix this? The branch bas been restored, please give a try. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.