-
Notifications
You must be signed in to change notification settings - Fork 136
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
1.0.0 and 0.4.0 packages in puppetforge broken #46
Comments
This release was only compatible with Puppet 4.0 or higher. You need version 1.0.0 or higher to use Puppet 3.4 - 3.8, or enable the future parser. |
Ah, ok. How about bug in 1.0.0 git tag? |
These are virtual files added by GNU tar, looks like you might be using r10k which warns about them. https://tickets.puppetlabs.com/browse/RK-238 appears to reduce the logging severity. I don't know about the full_module_name error, but there are some tickets in r10k's tracker mentioning it - perhaps rule out if it's an issue in r10k or pointing to an issue in the module? A basic |
Thank you very much for your support. Yes, you're right. In latest version of r10k (2.3.0) problem doesn't reproduce.
|
1.0.0 package in puppetforge broken:
Code of package 0.4.0 broken too:
The text was updated successfully, but these errors were encountered: