> A workaround is to just put them in the /etc/hosts file.
That doesn't really help: the test suite also relies on a number of host
names.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-d
Martin v. Löwis wrote:
> That's a common OSX problem/bug. Processes occasionally lose the ability
> to resolve host names. Various theories float around what's causing this
> (most commonly, people expect that a "controlling terminal" must be
> present); my theory is this:
>
> There is a Mach po
Martin v. Löwis wrote:
> Bill Janssen wrote:
> > parc-leopard-1 (and most of the other builders) are failing the svn
> > checkout with the following error:
> >
> > svn: PROPFIND of '/projects/python/trunk': Could not resolve hostname
> > `svn.python.org': Temporary failure in name resolution
>
Bill Janssen wrote:
> parc-leopard-1 (and most of the other builders) are failing the svn
> checkout with the following error:
>
> svn: PROPFIND of '/projects/python/trunk': Could not resolve hostname
> `svn.python.org': Temporary failure in name resolution
> (http://svn.python.org)
>
> When I l
parc-leopard-1 (and most of the other builders) are failing the svn
checkout with the following error:
svn: PROPFIND of '/projects/python/trunk': Could not resolve hostname
`svn.python.org': Temporary failure in name resolution (http://svn.python.org)
When I log into that machine as "buildbot" a
