Re: Required help on local Debain mirror
- Date: Wed, 30 Aug 2017 12:31:06 -0500
- From: David Wright <deblis@xxxxxxxxxxxxxxxxx>
- Subject: Re: Required help on local Debain mirror
On Wed 30 Aug 2017 at 17:27:31 (+0200), Christian Seiler wrote:
> Hi there,
> Am 2017-08-29 11:57, schrieb Kala Techies:
> >I am using (Debian GNU/Linux 6.0.10 (squeeze)) in my environment and I
> >want to update all systems using one local mirror.
> I don't think it's a good idea to setup a real local mirror,
> as that means you'll download the entire archive, which is
> likely going to be a _lot_ more stuff (especially if you
> download all available architectures) than upgrading each
> machine individually.
> What you'll rather want is to setup a local proxy server
> that'll cache the packages. This way you'll only download
> what you actually need, but you'll also only download it
> I can recommend the apt-cacher-ng package for that.
However, be prepared for problems if you run a version of
apt-cacher-ng as old as squeeze's.
I still run apt-cacher-ng on a wheezy machine and have had to switch
between the backports and backports-sloppy versions, currently the
latter, 0.9.1-1~bpo7+1. The main failures have been (1) expiration of
old packages¹, (2) new compression schemes² for Packages files, (3)
new InRelease files and (4) servicing apt-listbugs³ searches. I use it
for wheezy and jessie, but have made no attempt to use it with
stretch; is that when hashed indexing started?
I don't know how many of these issues will affect a constituency of
totally squeeze PCs; I guess that depends on whether the mirrors
being used have been updating their apt methods, and if there are
¹ie the archive grows for ever.
²eg .xz and/or .bz2 files.
³my current command sequence for upgrading is the unwieldy
# apt-get -o Acquire::http::Proxy="http://192.168.1.19:3142/" update
# apt-get -d -o Acquire::http::Proxy="http://192.168.1.19:3142/" upgrade
# apt-get upgrade