Questions about package pinning

Andre Costa <[email protected]> Fri, 30 Jul 2004 07:33:03 -0300
Newsgroups gmane.linux.conectiva.apt-rpm
Organization TecGraf
Message-ID <[email protected]>
Hi,

I need to do some package pinning, because a couple of packages are
breaking things around here. A practical example is cdrecord from
kde-redhat: it breaks latest k3b and xcdroast (already filed a bug
report for that).

So, I put this on /etc/apt/preferences based on a couple of references
I found with Google:

Package: cdrecord
Pin: release c=freshrpms
Pin-Priority: 1001

And it seems to be working:

apt-cache policy cdrecord
cdrecord:
  Installed: 8:2.01-0.a19.2
  Candidate: (none)
  Package Pin: (not found)
  Version Table:
     8:2.01-0.fdr.5.a27.1 1001
        500 ftp://apt.kde-redhat.org fedora/1/stable pkglist
 *** 8:2.01-0.a19.2 1001
        500 http://ayo.freshrpms.net fedora/linux/1/i386/core pkglist
        100 RPM Database

(although I didn't understand why the "(not found)" for "Package
Pin:"...)

The thing is: I tried to use:

Package: cdrecord
Pin: release c=kde-redhat
Pin-Priority: 0

And it didn't work -- apt was trying to upgrade cdrecord to latest from
kde-redhat. My guess is that "c=kde-redhat" is wrong. Or should I have
used Pin-Prioiry = -1?

So, any good reference about apt pinning will be most welcome --
specifically, I'd like to know to specify a, c, o, l, v for a specific
package/repository?

Feel free to point me to some documentation if it is already there. I
browsed the APT HOWTO info at
http://www.debian.org/doc/manuals/apt-howto/ch-apt-get.en.html, but
IMHO it wasn't very complete with regards to these parameters.

TIA

Andre

-- 
Andre Oliveira da Costa
([email protected])