Re: Apt pinning suspect?

[Daniel Burrows <dburrows@debian.org>]

On Tue, May 13, 2008 at 09:13:32AM +1000, Rich Healey <healey.rich@gmail.com> was heard to say:
> I've got a Lenny/Unstable/Experimental laptop that I use for work (yes,
> i realise that precariously mixing 3 releases is stupid.. but I'm
> committed now so oh well.)
> 
> Anyway, the point is that my pure unstable/experimental box at home has
> pulled in all of kde 4 (version 4:4.0.72-1 0), but my laptop at work can
> find kdebase 4:4.0.72-1 0, but the rest of kde4 is still
> 4:4.0.68+svn794641-1 as a result, it won't update, and is holding
> various bits of my system back.

> This is in apt-cache policy as well, so for example kfind (one of
> kdebases's dependencies):
> 
> [xenia:/home/richo]# apt-cache policy kfind
> kfind:
>   Installed: 4:4.0.68+svn794641-1
>   Candidate: 4:4.0.68+svn794641-1
>   Version table:
>  *** 4:4.0.68+svn794641-1 0
>         501 http://ftp.iinet.net.au experimental/main Packages
>         100 /var/lib/dpkg/status
>      4:3.5.9.dfsg.1-2+b1 0
>         500 http://ftp.iinet.net.au lenny/main Packages
>         499 http://ftp.iinet.net.au unstable/main Packages
>      4:3.5.7-3lenny1 0
>         500 http://security.debian.org lenny/updates/main Packages
> [xenia:/home/richo]#

  Which architecture is this?  According to packages.debian.org, kfind
version 4.0.72-4 is only available in amd64 for experimental.

  Daniel