I've been in the habit of looking up build logs on amd64.ftbfs.de to see why various new uploads have failed to develop amd64 binary packages. Lately, however (over this past weekend?) the server, which evidently also hosts volatile.debian.net, has started presenting the latter site exclusively -- an attempt to bring up http://amd64.ftbfs.de/ instead yields the front page of volatile.debian.net, and http://amd64.ftbfs.de/build.php gives the infamous error 404.
FWIW, I'm proxying via a local squid installation configured as a child of *.ircache.net. Anybody know what's up? -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
