Comment 12 for bug 2003851

Hello, also affected by this.

I'm able to reproduce the bug using Walter's mock server. I suspect it may be related to the retry code that kicks in when a transient error is encountered (like a 503). Retries are enabled by default since apt 2.3.2, which seems to fit the regression window people have mentioned here.

Frustratingly, I can't reproduce while step debugging, I'm guessing because the bug is clock-dependent.

Setting either `Acquire::Retries::Delay=false` or `Acquire::Retries=0` seems to mitigate it. I'm curious if that works for others as well. I'll be testing this in prod soon and will report back.

In the mean time I'll keep trying to find the actual bug.