The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #1822

specifying version in package declaration should pin apt to that version

Added by Sam Quigley over 5 years ago. Updated over 3 years ago.

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

0%

Category:package
Target version:-
Affected Puppet version:0.24.6 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

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”:https://bugs.launchpad.net/ubuntu/+source/xen-3.3/+bug/297077

it’d be great if specifying the version would magically add the relevant clause to “apt’s preferences”:http://wiki.debian.org/AptPinning in order to do the right thing…

History

#1 Updated by James Turnbull over 5 years ago

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

#2 Updated by Adam Jacob over 5 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 3 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 over 3 years ago

  • Target version deleted (4)

Also available in: Atom PDF