-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
install RowanClientServices fails in v2.1 #14
Comments
I remember running into the branch typo .. so I think I've fixed it along the way ... will need to spelunk a bit and I'm just headed to lunch ... |
... ooooh ... test_rowanV3_alpha.sh ... if you are running with a stone that old (I think it's over a year old) the more recent repositories may cause trouble ... With that said, I hit the branch typo using 3.7.1 ... so that bit is a real issue ... the biggest issue with the 370 alpha rowan v3 stuff is that the File System api changed and the required adjustments are not backward compatible ... so things may go along smoothly and then bang ... |
I'm just comparing the test_rowanV3_alpha.sh script with the info on the projectsSets README for guidance. I'm using v2.1 of stones installing into 3.7.0 using minimal_rowan template. then installing the projects as per the test script. |
ah ... makes perfect sense ... I will double check where I ran into that problem and make sure the I've updated the project sets in GsDevKit_stone:v2.1 |
I'm following the projectSets/README and the tests script test_rowanV3_alpha.sh in an effort to understand how to setup a Rowan stone, and install projects with Rowan.
Got to:
installProject.stone file:/path/to/gs_projects/RowanClientServices/rowan/specs/RowanClientServices.ston
--projectsHome=/path/to/gs_projects
in v2 and v2.1 the projectSet rowanV3_gs.ston clones revision ericV3.0_pharo of RowanClientServices.
RowanClientServices spec file in branch ericV3.0_pharo has a typo
masterv3.0 rather than
masterV3.0
This fails to load with the error:
performOnServer: 'set -e; cd /opt/stones/bvc_rowan/git/gs_projects/RowanClientServicesV3; git --git-dir /opt/stones/bvc_rowan/git/gs_projects/RowanClientServicesV3/.git --work-tree /opt/stones/bvc_rowan/git/gs_projects/RowanClientServicesV3 checkout masterv3.0' stdout: 'error: pathspec ''masterv3.0'' did not match any file(s) known to git
AND/OR, maybe it has something to do with #projectAlias : 'RowanClientServicesV3' - which I assume allows for having an alternative name for the cloned directory. End result, it's creating a RowanClientServicesV3 directory next to the cloned repo RowanClientServices. That doesn't seem like the intended behaviour, but I could be wrong.
The text was updated successfully, but these errors were encountered: