Repository navigation
auto-apt-proxy #9
Replies: 4 comments
Here are your options:Modify auto-apt-proxyAdd a subroutine to detect apt-cacher-ultra (ACU). This creates a new subroutine, Modify apt-cacher-ultraThe only difference between ACU and ACNG is the HTTP error code auto-apt-proxy looks for, 400 and 406, respectively. With this change, auto-apt-proxy would mis-identify ACU as ACNG, but it would detect it. I have not tried this, so I have no idea how much is involved. Something Completely DifferentYour ideas here. DiscussionI have not tried the second suggestion. It has the advantage of not requiring anyone to get the auto-apt-proxy maintainers to accept this patch. On the other tentacle, it would be nice to have ACU properly identified. |
|
I do not use
For each of those IPs it then runs detection functions against them for every kind of apt proxy that it knows about. So the issue here is that as you say it tries to detect ACNG, gets an HTTP code that doesn't correspond and moves on to the next type of check. I think this is a clear deficiency in auto-apt-proxy to be honest. If there is a DNS entry for That said, it seems like a simple change for ACU and if the maintainers agree then that's going to reach a release long before a change in Finally, it looks like |
|
The patch above works with auto-apt-proxy version 16.8, as on trixie. The current version of auto-apt-proxy is 1.8. That is also the version on forky. Invoke the patch |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
auto-apt-proxyis a utility to detect apt proxies, such asapt-cacher-ng. Alas, it does not detectapt-cacher-ultra. I may look into that some time in October.All reactions