On 04/18/2016 07:14 AM, Eric Cooper wrote:
I'm not sure, but due to the way mirrors work, it's often difficult to
reproduce some problems, and they often just "go away" when you retry.
For example, the ftp.us.debian.org mirror is actually round-robined
among multiple sites. A longstanding problem with approx is that it
resolves the name on each transfer (because I'm lazy and just pass the
name to curl). If it resolves to different sites between the Release
file and the Packages file, and those two sites are not in sync,
the update can fail with checksum errors.
Any way, I'm going to mark this closed as of version 5.5 unless you
object. Sorry for the inconvenience.
Please leave the bug report open.
I typically run up to a half dozen machines for my SOHO LAN. I've run
Approx off and on for the past several years, and have experienced these
kinds of insolvable problems. When it works, great. When it doesn't
work, I shut it down and do redundant downloads (netinst and/or
updates). Recently, I started doing Debian Live builds. So, now I need
Approx even more.
Perhaps if Approx saved the IP address after the first name lookup and
used that for all transfers, Approx would be more reliable (?). Or,
does round-robin make this impossible?
As a work-around, can I specify a host that is not round-robined in my
approx.conf file? How do I find such hosts?
Any other ideas?
David
