14 Nov
2024
14 Nov
'24
2:41 p.m.
Hi all!
On Thu, 14 Nov 2024, at 2:26 PM, Andy Smith via BitFolk Users wrote:
The BitFolk aptcacher VMs are pretty ancient. I've quickly deployed a
new one with an up to date version of apt-cacher-ng and the problem
doesn't manifest, so this seems like a simple fix.
I assume that Fastly have done something with their configuration that
older versions of acng can't handle.
This will probably remain broken for the rest of today as I need to
deploy these properly.
Again, should you particularly urgently need to do package
updates/upgrades you can edit your sources to remove the literal string
"apt-cacher.lon.bitfolk.com/debian/" from each line. That leaves you
talking directly to deb.debian.org.
In the VMs in future it might be neater/more flexible to use a generic or as-shipped
/etc/apt/sources.list and define the proxy in either /etc/apt/preferences.d/ with a config
file containing 'Acquire::http::Proxy "http://proxyaddress:proxyport";'
or use auto-apt-proxy[1] and set it in /etc/hosts or figure out the autodetection magic it
uses!
I use the latter on my home development setup these days, and also recently broke
everything by config-defining a proxy *and* using auto proxy!
[1] https://packages.debian.org/sid/auto-apt-proxy
Cheers!
--
Dave Hibberd <hibby(a)debian.org>
Debian Developer
Packet Radioist
MM0RFN