Hi Grabriel,

yes, that's the point ... it's not currently possible so I wanted to know
what the community is doing for overcoming this "problem" ... and whether
it could be a useful feature.

I have done a quick&dirty hack to the APT provider and it works when
installing a new package I can enforce a version and hold it. But from my
minor mod to a proper patch...there is still much work to do, so that's why
I was looking for comments, opinions, and so on about this feature....

I probably didn't explain myself well enough in my first email :-)

On Friday, May 17, 2013 4:20:16 AM UTC+2, Lelutin wrote:
On 16/05/13 03:28 AM, sjr wrote:
Take a look to the example I wrote, I know writing the version in ensure
puppet will do that...but let's imagine someone puts a new version of
one of our services in the repository and another someone comes and
makes the mistake of upgrading without noticing that new version, the
service will be restarted twice ... for the upgrade and next time puppet
will run, also notice we're not running puppet agent in daemon mode so
either a human or Nagios will have to find out about the upgrade. We
would like to avoid this kind of situations.
oh! I just went back to the puppet documentation and learned something.
I didn't know puppet was able to hold packages..

according to documentation you should set "ensure" to the value "held"
to have puppet use "dpkg --set-selections $package hold",

but then reading the "package" type and its "apt" provider,
unfortunately I don't think it's possible to mix holding and enforcing a
particular version since both use the ensure parameter..

On Thursday, May 16, 2013 7:25:57 AM UTC+2, Lelutin wrote:
On 15/05/13 08:24 PM, sjr wrote:
The thing is we would like to be able to specify a version for the
package and tell dpkg to hold it to prevent unwanted upgrades
because human errors). As I haven't been able to get it working
current APT provider I would like if with its current status this
if you provide a version in the "ensure" parameter, then puppet will
install this specific version..

but the way we do it where I work is to have puppet drop a file in
/etc/apt/preferences.d and pin it. See [0] for more info on pinning (it
doesn't talk about preferences.d, but everything that can go in
/etc/apt/preferences can be split in different files in

[0]: http://wiki.debian.org/AptPreferences

this way, you're sure that no operation, should it be puppet or manual
interventions will upgrade the package.

Gabriel Filion
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 5 of 7 | next ›
Discussion Overview
grouppuppet-users @
postedMay 16, '13 at 12:24a
activeMay 20, '13 at 2:45p

2 users in discussion

Sjr: 4 posts Gabriel Filion: 3 posts



site design / logo © 2022 Grokbase