Skip to content
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

gem issues #2

Open
ranguard opened this issue Jul 8, 2017 · 4 comments
Open

gem issues #2

ranguard opened this issue Jul 8, 2017 · 4 comments

Comments

@ranguard
Copy link

ranguard commented Jul 8, 2017

Wonderful post on https://puppet.com/blog/deploying-docker-swarm-puppet thank you so much, and this is a really useful repo... though I haven't been able to get it working...

==> swarm-101: ERROR:  While executing gem ... (Gem::DependencyError)
==> swarm-101:     Unable to resolve dependencies: r10k requires semantic_puppet (~> 0.1.0); puppet_forge requires semantic_puppet (~> 1.0)

I did a:

/opt/puppet/bin/gem install puppet_forge

and a:

/opt/puppet/bin/gem update

So now get:

/opt/puppet/bin/gem install r10k
ERROR:  While executing gem ... (Gem::DependencyError)
    Unable to resolve dependencies: r10k requires semantic_puppet (~> 0.1.0)

Side note: the README talks about master-01 it's swarm-master-01

I have seem some network warnings, but haven't looked at those yet.

Again - thanks - even if I can't use this repo having it for reference is amazing

@scotty-c
Copy link
Owner

scotty-c commented Jul 9, 2017

@ranguard I will have a look at this tonight, the gem issue has been broken from an upstream r10k release. I will run the repo and make sure everything is working.

@scotty-c
Copy link
Owner

@ranguard I have fixed most of the issues to get this working again. Sorry, it's taken longer than expected. There is an issue with an upstream module that I will put a PR in to fix. So hopefully it will be up and running by the end of the week

@ranguard
Copy link
Author

Hi @scotty-c no rush on my part, and I realised it wasn't you so much as upstream, when there's a fix please close this issue and I'll have another go then. Again thank you for what you have done.

scotty-c pushed a commit that referenced this issue Jul 17, 2017
@scotty-c
Copy link
Owner

@ranguard I have all the issues fixed now and in master. So this should all work now. If you could test on your end to make sure I have not missed anything. I will leave the issue open for you until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants