For anyone who wonders, the fix was in an earlier version 3.7-1 that
went to experimental first.
apt-cacher-ng (3.7-1) experimental; urgency=medium
* New EXPERIMENTAL upstream release
+ various fixes, now this probably really closes: #954904, #986356
+ minor DB generation reproducibilit
This bug was fixed in the package apt-cacher-ng - 3.7.3-1
---
apt-cacher-ng (3.7.3-1) unstable; urgency=low
* New upstream version
+ fixes interpretation of compressed v6 IPs (closes: #994778)
+ adds support for .sig suffix (closes: #989347)
+ fixes compilation with g++-
Maybe what is listed at https://wiki.debian.org/AptCacherNg under the
heading "https repositories" might serve as a starting point for you to
do this via server-side rather than client-side configuration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Sorry to hear about your trouble. May I suggest another way to deal
with the issue, albeit one that negates the benefit of caching which may
or may not be significant for you for this subset of packages. You can
place a snippet in /etc/apt/apt.conf.d/99-no-proxy of your clients with
the following
