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

"Could not update: Got nil value for ensure" on "ensure => latest" #43

Closed
swsnr opened this issue Aug 14, 2013 · 3 comments
Closed

"Could not update: Got nil value for ensure" on "ensure => latest" #43

swsnr opened this issue Aug 14, 2013 · 3 comments

Comments

@swsnr
Copy link
Contributor

swsnr commented Aug 14, 2013

With ensure => latest this provider fails with Could 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.

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.
@dbowling
Copy link

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.

@juniorsysadmin
Copy link
Member

Is this happening with the latest git sources?

@juniorsysadmin juniorsysadmin added the needs-feedback Further information is requested label May 20, 2015
@swsnr
Copy link
Contributor Author

swsnr commented May 20, 2015

@juniorsysadmin I don't know. You're a little late to ask. I don't even use Puppet anymore.

@juniorsysadmin juniorsysadmin removed the needs-feedback Further information is requested label May 20, 2015
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

3 participants