-
Notifications
You must be signed in to change notification settings - Fork 14
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
Yosemite support #38
Comments
The dock role is currently broken, due to dockutil being broken in Yosemite, but a fix is already submitted so that should be working again soon. |
Yep, that was to expect. I think dockutil should disappear for some time, the time we figure out the right tool for that. But we should indeed upgrade ansible. I'll try to do my best to find some more time ! |
The issue with dockutil is just a problem with the os versioning, ie: 10.# vs 10.##, so not that big of a deal. While it's somewhat finicky at times it's the only tool I'm aware of to manipulate the dock from cli. Ansible seems like just wait for 1.7 to be released, so that can still be put off for a little while 8) |
Well Ansible 1.7 is out and works fine, dockutil sadly still hasn't merged the PR to fix 10.10 compatibility. So for now to get a working ansible and osxc in a clean 10.10 install I'm doing:
and then things have been working, |
Yup great ! I finally got around this issue too. |
dockutil still hasn't had the patch to handle the new 10.10 versioning merged so I've been using a new dock1010 role in my xc-custom to handle patching it for yosemite. it checks for 10.10 and then downloads the patched version, otherwise uses the existing role so can be easily merged if dockutil remains unpatched after Yosemite's official release. I took a quick glance at xc-boot last week and it seems like all that's really needed is to update line 108 in boot.sh to pull version 1.7, but I've just been doing |
Finally got around to installing Yosemite in my test VM to check out osxc and... not working.
Ansible's facts are the problem, to work around the issue for now I did a git clone of ansible's current code (1.7) and things are working again.
git clone https://github.com/ansible/ansible.git ~/src/github.com/ansible/ansible
source ~/src/github.com/ansible/ansible/hacking/env-setup
Then you can proceed with ansible-playbook as expected.
@rricard - maybe, time to update ansible's version? pip -upgrade ansible only got me to 1.6.10 so had to git clone to get 1.7, though perhaps that'll be finished before Yosemite is public.
The text was updated successfully, but these errors were encountered: