apt-move affected by keys [was: Re: apt-move archive not being picked up by apt]

2006-03-05 Thread Chris Stiles
On 2/18/06, Chris Stiles [EMAIL PROTECTED] 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
 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:

Package: *
Pin: origin APT-Move
Pin-Priority: 990

--
regards, chris



apt-move archive not being picked up by apt

2006-02-18 Thread Chris Stiles
Hi --

I have the following cron job that runs nightly :

/usr/bin/apt-get update 
/usr/bin/apt-get autoclean 
/usr/bin/apt-get -dy dist-upgrade 
/usr/bin/apt-move update 
/usr/bin/apt-get update

This downloads updates currently needed, and puts them into an
apt-move style archive in /usr/mirror, which is then picked up like so
in sources.list:

deb file:/usr/mirror/debian testing main

However, even if a file exists in /usr/mirror, apt-upgrade will still
tryn and download it.

What is going wrong?

--
regards, chris



Re: apt-move archive not being picked up by apt

2006-02-18 Thread Andreas Janssen
Hello

Chris Stiles ([EMAIL PROTECTED]) wrote:

 I have the following cron job that runs nightly :
 
 /usr/bin/apt-get update 
 /usr/bin/apt-get autoclean 
 /usr/bin/apt-get -dy dist-upgrade 
 /usr/bin/apt-move update 
 /usr/bin/apt-get update
 
 This downloads updates currently needed, and puts them into an
 apt-move style archive in /usr/mirror, which is then picked up like so
 in sources.list:
 
 deb file:/usr/mirror/debian testing main
 
 However, even if a file exists in /usr/mirror, apt-upgrade will still
 tryn and download it.

Check apt-cache policy packagename to see if your apt-move package
source is listed. If it is, move it to a higher position in your
sources.list and run apt-get update.

best regards
Andreas Janssen

-- 
Andreas Janssen [EMAIL PROTECTED]
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps-sarge.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: apt-move archive not being picked up by apt

2006-02-18 Thread Chris Stiles
On 2/18/06, Andreas Janssen [EMAIL PROTECTED] wrote:
 
  This downloads updates currently needed, and puts them into an
  apt-move style archive in /usr/mirror, which is then picked up like so
  in sources.list:
 
  deb file:/usr/mirror/debian testing main
 
  However, even if a file exists in /usr/mirror, apt-upgrade will still
  tryn and download it.

 Check apt-cache policy packagename to see if your apt-move package
 source is listed. If it is, move it to a higher position in your
 sources.list and run apt-get update.

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
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

apt-get upgrade will now try and get cpp-4.0 4.0.2-8, however:

commanche:~# find /usr/mirror -name cpp*deb|grep   4.0.2-8
/usr/mirror/debian/pool/main/g/gcc-4.0/cpp-4.0_4.0.2-8_i386.deb

Interrupting apt-upgrade, running apt-update again and rerunning it
still won't pick it up from the local mirror.

--
chris

--
regards, chris