The Puppet Labs Issue Tracker has Moved:

Feature #1822

specifying version in package declaration should pin apt to that version

Added by Sam Quigley about 6 years ago. Updated almost 4 years ago.

Status:DuplicateStart date:12/15/2008
Priority:NormalDue date:
Assignee:Nigel Kersten% Done:


Target version:-
Affected Puppet version:0.24.6 Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


the issue is that specifying a version in a package declaration — eg

  package { "libxen3": 
    ensure => "3.2.0-0ubuntu10",

installs the right version — but doesn’t pin apt to that version. the result being that if you then manually run @apt-get upgrade@ you’ll end up with the newest version, regardless of what you specified. and that can be, er, “awkward”:

it’d be great if specifying the version would magically add the relevant clause to “apt’s preferences”: in order to do the right thing…


#1 Updated by James Turnbull about 6 years ago

  • Category set to package
  • Status changed from Unreviewed to Accepted
  • Target version set to 4

#2 Updated by Adam Jacob about 6 years ago

We should make sure that this feature has a way to be turned off – I can think of a few situations where you wouldn’t want pinning involved.

#3 Updated by Nigel Kersten over 4 years ago

  • Status changed from Accepted to Duplicate
  • Assignee set to Nigel Kersten

I’m closing as a duplicate in favor of #2406 which has more details around the issue.

#4 Updated by James Turnbull almost 4 years ago

  • Target version deleted (4)

Also available in: Atom PDF