pinning negative preferences not preventing installation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apt
I'm not sure if this is a problem with the documentation, or a problem with the application, however apt is not behaving as expected when pinning negative values.
According to man 5 apt_preferences, a Pin-Priority "P < 0 prevents the version from being installed."
Now I'll take a package at random and pin it in /etc/apt/
Package: python-tcm
Pin: version 0.5.1-0ubuntu4
Pin-Priority: -100
And yet, the package attempts to install:
root@prizm:/tmp# apt-get -Vs install python-tcm
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
pessulus (2.16.3-0ubuntu1)
python-tcm (0.5.1-0ubuntu4)
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Inst python-tcm (0.5.1-0ubuntu4 Ubuntu:7.10/gutsy)
Conf python-tcm (0.5.1-0ubuntu4 Ubuntu:7.10/gutsy)
The same occurs with a generalized version (Pin: version *).
I found a similar problem and I was going to report it here also; it wasn't working with "release a=unstable" and pins for debian repositories...
Finally I found the debian mirror I was using was missing the Release files in /var/lib/apt/lists and therefore the release wasn't being applied; does not seem to be your case, but I'd double check there, and perhaps would try as well changing mirrors, just in case...