Bug#204971: Wrong priorities with 'Pin-Priority: 0' in /etc/apt/preferences

[Matt Zimmerman <mdz@debian.org>]

On Mon, Aug 11, 2003 at 01:57:14PM -0400, Matt Zimmerman wrote:

> On Mon, Aug 11, 2003 at 07:43:01PM +0300, Jarkko Suontausta wrote:
> 
> > On Monday 11 August 2003 19:28, Matt Zimmerman wrote:
> > > What happens if you change the priority to -10 or so?  I think zero may be
> > > special.apt_preferences
> > 
> > Negative values are ok, only zero is special. However, according to 
> > apt_preferences(5), this shouldn't be the case:
> > 
> > "HOW APT INTERPRETS PRIORITIES
> > <cut>
> >        0 <= P <=100
> >               causes a version to be installed only if there is no installed
> >               version of the package"
> 
> Since I don't feel too confident about changing the semantics of priority
> zero, I think the best solution is to change the documentation to match the
> existing behaviour, and have apt print a warning if it encounters this
> situation.

Hmm, I just noticed that this is already documented, in the paragraph at the
very beginning of that section:

> Priorities (P) assigned in the APT preferences file must be positive
> or negative integers.  They are interpreted as follows (roughly speaking):

so I will just add a warning and change that <= to a <.

-- 
 - mdz