Hi Ben, it is the "short" commit hash from the official OpenSmalltalk github repo so you can reproduce the "VM" build easily: https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/276a5ff
>From Pharo 7 onwards now also the "image" is completely bootstrapped - you >also have a commit hash for the image to reproduce the image build/commit: https://github.com/pharo-project/pharo/commits/53eba94 Some details for the image hash can be found here: http://forum.world.st/SystemVersion-cleanup-or-the-return-of-the-explicit-build-number-in-latest-Pharo-7-td4977073.html We meanwhile also restored the image build number, so you can load the image with PharoLauncher with the build number again. The latest is 70414 as of today which mean Pharo 7, Build 414. You can go to "http://wiki.astares.com/pharo/30"; and click on "alpha" to visit the Pharo CI for the build number. Side note: From some of you last posts I see you still struggling with git or Iceberg issues. Had similar trouble in the beginning when Pharo process was switched to git and Iceberg was introduced. Because I tried always to compare with/tried to apply what I knew from VisualSourceSafe, ClearCase, SVN, Envy, Monticello, ... and many other VCS systems that I used before. So I bought the "Pro Git" from Apress book which helped me a lot understanding "git" (also some internals) first. I can really recommend to study it. It will safe you a lot of pain. You can find it on the web too: https://git-scm.com/book/en/v1 (first version) https://git-scm.com/book/en/v2 (new version) Bye T. Gesendet: Montag, 08. Januar 2018 um 19:45 Uhr Von: "Eliot Miranda" <[email protected]> An: "Pharo Development List" <[email protected]> Betreff: Re: [Pharo-dev] identifying source of particular VM Hi Ben, I think that the hash is indeed that if a commit. And I thought someone had written a script to find the commit from the hash. Alternatively you could look at the various system attributes the Squeak vm uses to identify itself. I *think* the Pharo vm has the same info baked in. In particular there should be the date of the commit. _,,,^..^,,,_ (phone) On Jan 8, 2018, at 6:36 AM, Ben Coman <[email protected][mailto:[email protected]]> wrote: This filename of the VM download url... http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201712211450-276a5ff.zip[http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201712211450-276a5ff.zip] includes a hash "276a5ff" that I presumed identified the opensmalltalk-vm commit from which this VM was built. i.e. so I could check that out if I wanted to compile a debug version of that VM. However... $ git checkout 276a5ff says... error: pathspec '276a5ff' did not match any file(s) known to git. so what exactly is that hash 276a5ff in the filename? cheers -ben
