-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
"Could not update: Got nil value for ensure" on "ensure => latest" #43
Comments
swsnr
added a commit
to flycheck/flycheck
that referenced
this issue
Aug 14, 2013
The NPM provider fails to handle latest packages which are already at the latest version, see voxpupuli/puppet-nodejs#43.
I confirmed that changing latest to present resolves the error. As long as this behavior is in place, it would probably make sense to update the readme, which shows the use of latest with the Express package. |
Is this happening with the latest git sources? |
@juniorsysadmin I don't know. You're a little late to ask. I don't even use Puppet anymore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With
ensure => latest
this provider fails withCould not update: Got nil value for ensure
, if the package is already at the latest version.The culprit is likely this line which fails to set
@property_hash[:ensure]
to the actual version of the package.The text was updated successfully, but these errors were encountered: