Hi Klee, On Mo, 2014-03-03 at 09:20 +0200, Andrei POPESCU wrote:
> > 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. thanks, you are right again ;). For the RC, I pick the second solution you outlined, as it's just less invasive. The exception is now HTTP 404 only. Are there other error codes (i.e., matching a valid use case) to include in this list? The latest stable snapshot from here http://mini-buildd.installiert.net/get.html http://mini-buildd.installiert.net/apt/hellfield_ab_wheezy_snapshot.list already has it, in case you are so daring to try. I keep in mind the (better) first solution (or maybe something completely different) for 1.1.x development branch, though. Hth, Stephan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
