without looking at the details, the HTTP/1.1 504 error suggests that the buildd is in kind of an odd state network wise.
i would think that we can expect xsl/xml parsers to deal with "no network", or a good network ... but expecting them to also ignore existing, but broken network setups is a wishlist bug. IMO first step is to fix the network setup on the buildd (e.g. dont run a proxy ...). Scond, you can file a bug against whatever underlying xml library cannot cope with HTTP errors like this coming back ... but as said above that would be a wishlist bug imo. - Alexander -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]

