Issue #639 has been updated by Russell Jackson.
Nigel Kersten wrote: > I can't find the bug now, but I added "ensure => held" a while ago in another > patch. That approach doesn't work very well in practice. You can't ensure a particular version and put it on hold at the same time. You can put in an exec to put the package on hold after the package resource installs it, but then you get a change notice on every run about the package version going from "held" to "<version>". I can't see how to fix this without holding be a separate parameter. ---------------------------------------- Feature #639: Add 'hold' feature to apt and aptitude https://projects.puppetlabs.com/issues/639#change-63166 Author: micah - Status: Duplicate Priority: Normal Assignee: Nigel Kersten Category: Debian Target version: Affected Puppet version: 0.24.4 Keywords: Branch: Placing a package on 'hold' will keep it from being upgraded automatically (or even suggested to be upgraded). It would be nice if I could put a package on hold enterprise-wide, without having to put a temporary exec statement into my manifests and instead be able to add it to my package definition. With aptitude you can do this with "aptitude hold <packagename>", with apt I think you need to do "dpkg --set-selections <package> hold" -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
