Package: apt-cacher
Version: 1.5.4
Severity: normal

The apt-cacher man page says

       clean_cache [1] Whether to flush old packages from your cache
              daily. Packages are deleted on the basis of whether they
              have been superseded by newer pack‐ages, not on age, so
              it should be safe to leave this on.
If one is using several releases (e.g., testing, unstable) it's not
clear to me if the comparison is made within release or across releases. 

It sounds as if all but the unstable version might get purged, which would 
basically mean apt-cacher was not acting as a cache for all of the
releases.

Since this effects the suitability of apt-cacher for some uses, I've
left this as a normal bug.  That is, the bug is that there's no way to
tell if apt-cacher is appropriate with multiple releases.

Similar issues may apply for people with different architectures.

This is *not* about attempting to combine (e.g.) Debian and Ubuntu
archives, the subject of a couple of other bugs/requests.

*If* apt-cacher keeps only one of the releases, then please also
consider this a wishlist request that it be able to handle more than
one at a time.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt-cacher depends on:
ii  bzip2                         1.0.3-7    high-quality block-sorting file co
ii  libwww-perl                   5.805-1    WWW client/server library for Perl
ii  perl                          5.8.8-7    Larry Wall's Practical Extraction 

apt-cacher recommends no packages.

-- no debconf information


Reply via email to