Ok - that should rule out those changes, however it may be a sign of things to come (or maybe not - its just the discussions here made me think of what I’m seeing).
I am running the image from the command line on OSX Sierra, using 64 bit. If I run System reporter it nicely shows the problem where I have run from a directory "Pharo-6.0-64-7vm” using .pharo-ui Pharo.image, However look at the first Monticello repository - its referencing another one of my directories - an older image that I haven’t used a for a few weeks. I’m pretty sure this current image was a fresh one downloaded with zeroconf as I was following Estebans instructions to use the 7 vm with a pharo6 image, and I had to do it a particular way as I quizzed him on it just a few days ago. I guess I will go and try it with a new image and see if I get the same results - but I’m wondering if there is a latent problem in here somehow? Image ----- /Users/macta/Dev/Smalltalk/Pharo/Pharo-6.0-64-7vm/Pharo.image Pharo6.0 Latest update: #60506 Unnamed Monticello Repositories ----------------------- /Users/macta/Dev/Smalltalk/Pharo/Pharo-6-60495-c/pharo-local/package-cache http://smalltalkhub.com/mc/Pharo/Athens/main/ http://smalltalkhub.com/mc/PharoExtras/CatalogBrowser/main/ http://smalltalkhub.com/mc/PharoExtras/Tool-DependencyAnalyser/main/ http://smalltalkhub.com/mc/MartinDias/Epicea/main/ http://smalltalkhub.com/mc/estebanlm/FastTable/main/ http://smalltalkhub.com/mc/YuriyTymchuk/ScrapYard/main/ http://smalltalkhub.com/mc/Pharo/Fuel/main/ http://smalltalkhub.com/mc/Moose/GToolkit/main/ http://smalltalkhub.com/mc/Moose/Glamour/main/ http://smalltalkhub.com/mc/Pharo/OSWindow/main/ http://smalltalkhub.com/mc/NicolaiHess/Playground/main/ http://smalltalkhub.com/mc/StephaneDucasse/AutomaticMethodCategorizer/main/ http://smalltalkhub.com/mc/Pharo/SessionManager/main/ http://smalltalkhub.com/mc/dalsat/ShoreLine-Reporter/main/ http://ss3.gemstone.com/ss/STON http://smalltalkhub.com/mc/Pharo/TxText/main/ http://smalltalkhub.com/mc/Pharo/FFI-NB/main/ http://smalltalkhub.com/mc/PharoExtras/Versionner/main/ http://smalltalkhub.com/mc/PharoExtras/BitmapCharacterSet/main/ http://smalltalkhub.com/mc/PharoExtras/XMLParser/main/ http://smalltalkhub.com/mc/Pharo/XMLWriter/main/ http://mc.stfx.eu/ZincHTTPComponents http://smalltalkhub.com/mc/Pharo/Pharo60/main http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main github://pharo-vcs/iceberg:master github://pharo-vcs/libgit2-pharo-bindings:v0.25.1 https://github.com/svenvc/NeoJSON/tree/master/repository https://github.com/svenvc/NeoJSON https://github.com/svenvc/NeoJSON/tree http://mc.stfx.eu/Neo github://svenvc/NeoJSON:master/repository filetree:///Users/macta/Dev/Smalltalk/Pharo/Pharo-6.0-64-7vm/pharo-local/iceberg/macta/PharoLambda Virtual Machine --------------- /Users/macta/Dev/Smalltalk/Pharo/Pharo-6.0-64-7vm/pharo-vm/Pharo.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.2250 uuid: 0726505e-161b-4a23-843e-c5222917ff5e Jul 1 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2250 uuid: 0726505e-161b-4a23-843e-c5222917ff5e Jul 1 2017 VM: 201707012338 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sat Jul 1 16:38:23 2017 -0700 $ Plugins: 201707012338 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Mac OS X built on Jul 1 2017 23:57:21 UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53) VMMaker versionString VM: 201707012338 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sat Jul 1 16:38:23 2017 -0700 $ Plugins: 201707012338 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ CoInterpreter VMMaker.oscog-eem.2250 uuid: 0726505e-161b-4a23-843e-c5222917ff5e Jul 1 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2250 uuid: 0726505e-161b-4a23-843e-c5222917ff5e Jul 1 2017 > On 10 Jul 2017, at 06:32, Rajula Vineet <vineet.re...@iiitb.org> wrote: > > Hey Tim, > > The new implementation hasn`t been merged into the pharo code base. This > error is not related to the new implementation. Probably it is related to > your local directories. Are you using a linux? Are you running from the > image directory? If you don`t, the path changes and pharo can not find the > cache directory. > > Rajula > > > > -- > View this message in context: > http://forum.world.st/The-new-implementation-of-current-working-directory-tp4952918p4954070.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >
