15

I have a package in Debian that has been manually patched (not ideal, I know) that I must hold at its current version so upgrades don't overwrite the patched changes (I will manually inspect and apply security updates). As I understand it, there are a few ways to approach this:

  • apt-pinning (see apt_preferences(5))
  • aptitude hold
  • dpkg --set-selections
  • setting it with dselect?

I've read that one hold won't affect another (so, for example, using aptitude hold won't prevent apt-get or dselect from upgrading the package). What needs to be done to 100% ensure that Debian's tools will never upgrade the package unless I remove the hold?

0xC0000022L
  • 16,189
  • 24
  • 102
  • 168
jrdioko
  • 860
  • 1
  • 9
  • 18
  • 1
    Just a comment, 9 years ago someone created a bug in Debian's bug system about how really can *hold* a package, and seems like there is (or was) some issues using aptitude hold ( LINK: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=146207 ) – Luciano Facchinelli Oct 23 '11 at 07:31
  • 1
    That someone would be me. :-). Still an open bug, though the people who have recently revived aptitude said they would take a look at it. – Faheem Mitha Aug 02 '12 at 16:41
  • 1
    Daniel Hartwig wrote to me: "Been aware of this issue with holds since I began working on aptitude. At the moment I have not given it a thorough look as my focus has been on getting multi-arch working. It's age and significance does intimidate me a bit. There is also the matter that aptitude somewhat "interprets" dpkg states on startup to determine what, if any, changes and how they should incorporate in to it's internal state model. Be assured that this one will not be left alone -- I am always mindful of it when looking at related areas of the code." – Faheem Mitha Aug 02 '12 at 16:42
  • 1
    http://bugs.debian.org/146207 is supposedly fixed in the version of aptitude uploaded to unstable. – Faheem Mitha Oct 25 '15 at 16:41

3 Answers3

8

aptitude and dpkg have separate hold functions which won't respect each other, unfortunately. So you have to set both if you use both tools:

apt/dpkg: echo $PACKETNAME hold | dpkg --set-selections

aptitude: aptitude hold $PACKETNAME

scai
  • 10,543
  • 2
  • 25
  • 42
  • 4
    It appears that there is now `apt-mark hold` which according to https://help.ubuntu.com/community/PinningHowto#Introduction_to_Holding_Packages, does the same thing as `dpkg --set-selections`. – andyg0808 Jul 09 '16 at 09:59
3

A better approach in this particular case (patched package) could be to install the patched version in /usr/local. Debian won't touch that.

Stéphane Gimenez
  • 28,527
  • 3
  • 76
  • 87
daniel kullmann
  • 9,427
  • 11
  • 38
  • 45
0

As far as I know, aptitude hold <package> will be honored by the others unless you explicitly order it upgraded (such as hitting + while the cursor is on the "upgradeable packages" field in aptitude).

Shadur
  • 30,641
  • 11
  • 58
  • 69