-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
Cannot install on PE3.0 #2
Comments
Currently testing against stdlib 3.2.0 to see if 4.10 is an actual requirement. PR may be pending. |
FYI...I just verified that I'm still seeing the above for PE 3.0.1 and the latest version of the moduel from the Forge. Also, I have a former Fundamentals student who emailed me stating that he is seeing same.
|
I think I may have just put this in and refactored the need for it back out. I think at minimum we can probably just require 3.2. (if you test it ) if you send a PR I will merge ASAP |
Will do this week. Stay tuned. Thx! |
I pushed a nvpuppet/r10k module to the Forge which is a fork of zack/r10k with the adjused Modulefile and this definitely made puppet module tool happy on PE 3.0.1. Also, I did a quick run of the code and I don't see anything in there that looks like it wouldn't be unhappy with stdlib 3.2.x. I think we are okay to bump the dep back in the Modulefile. |
I was able to install Nathan's branch of the module on my test PE 3.0.0 master without any issues. Puppet apply -t also completed without problems following the installation. |
Forge release cut 0.0.7 |
Awesome, thank you! |
Get the following:
Looks like a conflict on hard dependency of puppetlabs-pe_accounts/mcollective and zack-r10k modules.
The text was updated successfully, but these errors were encountered: