Hmmm - hang on a second, something very weird is going on - looking at how to track where files get written on OSX and using: touch ~/timestamp find -x / -newer ~/timestamp >~/changedfiles.txt
The result is that when I do my zero conf install - my files now seem to be going to the 7.0.2 install that I did on Thursday, and not to the local directory where I am running. I think Is it possible that this new release has change something. - WTF? How can this happen? /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git/refs/heads /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git/index /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git/FETCH_HEAD /Users/macta/Dev/Exercism/pharo7e3 /Users/macta/Dev/Exercism/pharo7e3/Pharo.changes /Users/macta/Dev/Exercism/pharo7e3/pharo-local /Users/macta/Dev/Exercism/pharo7e3/pharo-local/iceberg /Users/macta/Dev/Exercism/pharo7e3/pharo-local/iceberg/credentials.fuel /Users/macta/Dev/Exercism/pharo7e3/pharo-local/ombu-sessions /Users/macta/Dev/Exercism/pharo7e3/pharo-local/ombu-sessions/Pharo7.0.2-0-32bit-890f474.c1wfkijoa7470az0raz1zczo0.ombu /Users/macta/Dev/Exercism/pharo7e3/icon-packs /Users/macta/Dev/Exercism/pharo7e3/icon-packs/idea11.zip Tim > On 16 Mar 2019, at 21:50, Tim Mackinnon <tim@testit.works> wrote: > > Hi Sean - thanks for chipping in: > > Yes - the correct packages are loading, the baseline is fine (and its a > baseline I’ve been using without issues for a while) - its simply just not > loading the same source as if I do a clone by hand via git in a separate > directory? > > It’s like iceberg just doesn’t want to load the lates stuff and wants me to > do a manual “pull” in the image to catch up? > > Thinking that maybe my master branch was weird - I did a hard reset in a > separate copy, and update the readme.md and committed that, and pushed it. > > Now when I go back to my pharo zero, conf - and clear out the iceberg > directory, and run my command line/or playground script again - it now loads > and says I need to pull 5 new commits (prior to this, it said 4 commits). > > The is what I’m not understanding - why isn’t it just pulling in all of those > commits in a fresh load? I’ve never seen this before, and am at a loss why > this is suddenly happening? > > If I open the settings, and check software config management - the share > repo’s setting is unchecked. However - the weird thing is that I don’t see > anything in the pharo-local/iceberg directory (making me think that something > must have got flipped - but I’ve not knowingly done anything in the few hours > between when it last worked and suddenly stopped). > > Grrrr… just as I was starting to get the hang of things, its all fallen apart > again. > > Tim > >> On 16 Mar 2019, at 17:34, Sean P. DeNigris <s...@clipperadams.com> wrote: >> >> Tim Mackinnon wrote >>> Can anyone think of what might cause this? I’m really confused. >> >> Am I understanding correctly that your load script is loading the correct >> packages, but not the latest versions? >> >> If so, just a few initial thoughts: >> - What does the local clone look like after the load (i.e. does it show the >> missing commit(s)? >> - It is possible that shared repo location is enabled? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >
