Re: apt-cacher-ng problems

[Tim Woodall <debianuser@woodall.me.uk>]

On Sun, 7 Aug 2022, David Wright wrote:

> On Sun 07 Aug 2022 at 08:46:12 (+0100), Tim Woodall wrote:
> > I installed acng yesterday. Nothing else has changed.
> >
> > A script is fetching all of the required packages plus a few others for
> > amd64,i386,arm64 and armel starting with sid all the way to jessie
> >
> > Rather complicated setup: (This does make sense although in this
> > particular failure it looks excessively complicated)
> >
> > apt(aptmirror17) -> acng (localhost) -> squid (different host) ->
> > apache(back on aptmirror17)
> >
> > downloaded all of the i386 packages and was fine for amd64 until
> > 1659848478|O|404276|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb
> > 1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/gzip_1.12-1_amd64.deb [HTTP error, code: 502]
> > 1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/hostname_3.23_amd64.deb [HTTP error, code: 502]
> > etc
>
> So you're caching sid ?
>
> > I don't have the exact output from apt for this particular error but it
> > will have been something like:
> > Err:129 http://aptmirror17.home.woodall.me.uk/local buster/essential
> > armel linux-image-4.19.0-21-rpi armel 4.19.249-2
> >   502  Connection closed [IP: ::1 3128]
> > ...
> [ ? ]
> > I cannot see anything wrong in either of the squid or apache logs.
> [ ? ]
> > Squid checking the file is unchanged is logged by apache.
> > 2001:8b0:bfcd:100:MUNGED:8 - - [07/Aug/2022:05:01:17 +0000]
> > "GET /local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb HTTP/1.1" 304
> > - "-" "Apt-Cacher-NG/3.6.4" "aptmirror17.home.woodall.me.uk"
>
> ? and that looks as if you're running acng/bullseye.
>
> Your setup is too complicated for me to give any direct help, but
> I can say that running acng/versionN to cache packages from versionN+1
> has twice led to a need to upgrade to acng/versionNbackports, once to
> acng/versionNsloppybpo, and once where even that wasn't enough.

Thanks, I'm caching packages from everything from jessie to sid. I've
just backported acng. I'll clear the acng cache and rerun the caching of
the essential/required packages and see if the problem is fixed.

I had failures while fetching sid, bullseye, buster and stretch
packages. Only jessie didn't have any failures (which might have just
been luck - plus jessie doesn't have arm64 so a smaller set to fetch)

I'm doing a lot of automatic bootstrap builds which is why I want all of
these packages explicitly cached. I've been keeping a mirror of these
packages but I have to maintain that - acng seemed to be a way to avoid
any need to maintain the cache manually. (and it looks like it will do
the job I want)

I'm bootstrapping using only apt and dpkg and a "essential on a diet"
scheme
https://wiki.debian.org/Proposals/EssentialOnDiet
apt to decide the order to install packages and dpkg to unpack and
install them. In order to confirm that everything is always going to
work I have to ensure that an install in every possible order allowed by
the dependencies will work.

I've had to make changes to a surprisingly small set of packages to make
this work, even for jessie.
Sid only needs changes to apt (dependency change), base-files (slightly
reworked postinst script and dependency change) and util-linux
(dependency change)

Tim.