Source: python-mini-buildd Severity: normal The changes to modify the URL used by the ping mechanism worked for using mini-buildd as a source, but not for using apt-cacher-ng.
I also have a similar problem connecting to package repositories that require client certificate authentication. Since there's no support for that directly in mini-buildd yet, I use the hack of disabling the client auth when activating the source. Then I can manually add the client certificate to the appropriate chroot and all is well. But since the ping check is run much more often, it breaks that hack. My temporary solution was just to mark hosts that fail to ping with a time of 1000, so they sort after low-ping hosts. I see two different approaches that might work offhand: * Change the ping code to use a full path to a repository file when checking the ping time (probably by passing a source argument to mbd_ping). * Change the ping code to consider a 404 as a successful ping (since the goal is to determine network timing, not validate the source). I'm happy to submit a patch for whatever approach you prefer, but didn't want to presume to pick one for you. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.11-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
