Forum: JRuby fatal: unrecognized argument: --format=format:%h

Posted by Jan Hegewald (Guest)
on 2010-09-01 14:32
(Received via mailing list)
Dear all,
I just tried the most recent jruby snapshot from
http://ci.jruby.org/snapshots/
This is what I see here on my Mac OS 10.6.4 machine:
$ jruby -v
jruby 1.6.0.dev (ruby 1.8.7 patchlevel 249) (2010-09-01 fatal: 
unrecognized argument: --format=format:%h) (Java HotSpot(TM) 64-Bit 
Server VM 1.6.0_20) [darwin-x86_64-java]

Do you also get this fatal ... string inside the version message?

Cheers,
-- Jan
Posted by Hirotsugu Asari (Guest)
on 2010-09-01 14:52
(Received via mailing list)
On Sep 1, 2010, at 8:32 AM, Jan Hegewald wrote:

> -- Jan
The error should not affect the fitness of the snapshot, so don't worry 
about that.

To be more precise… That's where the git revision is supposed to go if 
you build the binary from the source, like so:

$ git log -1 --format=format:%h
b9f8624

My guess is that the git version in the snapshot environment is either 
too old or too new, and the argument is not recognized.

Hiro
Posted by Nick Sieger (Guest)
on 2010-09-01 19:09
(Received via mailing list)
On Wed, Sep 1, 2010 at 7:52 AM, Hirotsugu Asari <asari.ruby@gmail.com> 
wrote:
> [darwin-x86_64-java]
> My guess is that the git version in the snapshot environment is either too
> old or too new, and the argument is not recognized.

Yes, that's exactly it -- the version of git on our CI server is too
old. It actually turned out to be easier to change the command used to
generate the hash to `git log -1 --pretty=format:%h` which is
compatible with git 1.6 on the CI server as well as newer versions.
The next snapshot should properly capture the revision from which it
was built.

/Nick

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Posted by Jan Hegewald (Guest)
on 2010-09-03 12:38
(Received via mailing list)
On 01.09.2010, at 19:08, Nick Sieger wrote:

> The next snapshot should properly capture the revision from which it
> was built.

Yep, version string is looking fine again now.

Thanks,
-- Jan

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Please log in before posting. Registration is free and takes only a minute.
Existing account (Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
No account? Register here.