-
-
Notifications
You must be signed in to change notification settings - Fork 272
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
Under Debian, does not update collectd-core
when require => 'latest'
#269
Comments
Could you give us a complete snippet to reproduce ? Aren't you looking to set latest here instead ? https://github.com/pdxcat/puppet-module-collectd/blob/1830403421c03c10a00552075e164214e97c86da/manifests/init.pp#L16 |
On initial apply of puppet manifest, it works fine. It doesn't work properly when performing an upgrade on an existing
|
Well...
Is the mismatch between collectd and collectd-core causing issues ? If yes I'd also recommend to send this to Debian instead... Other than that I found unpractical to use ensure => latest anyway as it can cause surprise unplanned upgrades... |
Yeah, I understand where you're coming from. In our setup we had What I mean is that why have What are your thoughts on patching this inside the |
I'd rather not have us code around OS packaging problems. However, we could ensure an array of packages on (I assume) |
Let me know if #406 solves this for you. |
If you're trying to perform an upgrade on an existing collectd installation and set
require => 'latest'
,collectd-core
does not get updated.I would argue that this is more of an issue on the Debian side not specifying version requirements for
collectd-core
but it'd be great if this module would abstract this problem away.The text was updated successfully, but these errors were encountered: