Displaying 4 results from an estimated 4 matches for "aee4d80".
2013 Oct 02
2
Unknown versions in git.
>
> Are you sure??
No, I'm confused.
:-/
With shallow clones:-
opus
PACKAGE_VERSION="aee4d80"
opus-tools
PACKAGE_VERSION="7c3f522"
Something's gone wrong.
opus-tools is broken.
configure: error: Package requirements (opus>= 1.0.3) were not met:
Requested 'opus>= 1.0.3' but version of Opus is aee4d80
2013 Oct 01
2
Unknown versions in git.
----------------------------------------
> I guess we could ...
Hi
Your "--always" commit
here ---> http://git.xiph.org/?p=opus.git;a=commit;h=c435f06b308e52d7a5d2aad9eec98a1541832b47
has fixed it for "--depth 1" with opus.
PACKAGE_VERSION="1.1-beta-24-ga32fa31"
Are you going to apply a similar fix to opus-tools?
2013 Oct 02
0
Unknown versions in git.
On 2013-10-01 5:27 PM, bat guano wrote:
> opus-tools is broken.
>
> configure: error: Package requirements (opus>= 1.0.3) were not met:
> Requested 'opus>= 1.0.3' but version of Opus is aee4d80
"You're in the bottom of a well, surrounded by yaks."
Well, I'm back to keeping a hard-coded fallback version string in the
repo. Anyone else?
-r
2013 Oct 02
2
Unknown versions in git.
...way.
Jean-Marc
On 10/02/2013 12:47 AM, Ralph Giles wrote:
> On 2013-10-01 5:27 PM, bat guano wrote:
>
>> opus-tools is broken.
>>
>> configure: error: Package requirements (opus>= 1.0.3) were not met:
>> Requested 'opus>= 1.0.3' but version of Opus is aee4d80
>
> "You're in the bottom of a well, surrounded by yaks."
>
> Well, I'm back to keeping a hard-coded fallback version string in the
> repo. Anyone else?
>
> -r
> _______________________________________________
> opus mailing list
> opu...