apt-move affected by keys [was: Re: apt-move archive not being picked up by apt]
On 2/18/06, Chris Stiles <email@example.com> wrote:
> Thanks for the suggestions Andreas, I didn't know about the policy
> option before. I used it and came up with the following:
> /usr/mirror is in sources.list:
> commanche:~# grep /usr/mirror /etc/apt/sources.list
> #deb file:/usr/mirror/debian testing/updates main contrib non-free
> deb file:/usr/mirror/debian testing main
> commanche:~# apt-cache policy cpp
> Installed: 4:4.0.2-2
> Candidate: 4:4.0.2-2
> Version table:
> *** 4:4.0.2-2 0
> 500 file: testing/main Packages
> 500 http://ftp.uk.debian.org testing/main Packages
> 100 /var/lib/dpkg/status
I have done some digging around and have come to the conclusion that
the problem is caused by the introduction of public keys. The normal
order in which a sources.list is processed is the order in which the
sources appear in the file (pinning being equal) - and that is what
'apt-cache policy' is picking up on.
However, with the introduction of keys when priorities are equal it
appears that sources with a Releases.gpg file are preferred over ones
without (which is kind of logical).
As apt-move doesn't generate this file - unless a pin is used to
increase the priority of the created mirror it won't be used in
preference to whatever it's mirrored.
Incidentally, I fixed this temporarily by using:
Pin: origin "APT-Move"