[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problem with APT pinning



also sprach Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> [2006.03.12.0419 +0100]:
> >   Pin: release o=Jeff Bailey,l=Jeff Bailey
> >
> > doesn't work at all. In fact, I can't seem to pin on any o= and l=
> > fields of the release data.
> 
> Right, that rings a bell.

It does? It certainly seems like o= and l= are broken. I cannot find
a bug report on this. Any pointers?

> > It should not even apply. Default are pinned at 500, so any Ubuntu
> > package will be 500. However, I specifically pin bzr to 50, and
> > APT just ignores that.
> 
> The problem is that it pins down the already installed package as
> well. That should always be 100.

It only does that when I specify a package name. With *, it does not
pin already installed packages. #317186

> > Where did you get this information? In my book, I describe *** as
> > denoting the candidate and I am quite sure that I didn't "make that
> > up" but empirically determined it; I did not go and look at the
> > source though.
> 
> Just by looking at the output.

I shall have to investigate.

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`.     martin f. krafft <madduck@debian.org>
: :'  :    proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver!
 
women can keep a secret just as well as men,
but it takes more of them to do it.

Attachment: signature.asc
Description: Digital signature (GPG/PGP)


Reply to: