[Catalog-sig] Problems with pep381client
Brian Long
briandlong at gmail.com
Wed Feb 20 17:37:18 CET 2013
Hello,
I've been trying to set up a private Pypi mirror at my place of
employment using the pep381client v1.5. The script has bombed at
various places while trying to download packages over the last three
weeks. I've changed __init__.py to specify a.pypi.python.org (and
others), but it still fails.
After a couple of weeks of trying to mirror, fixing problems (changing
mirrors), etc. I've not been able to get past the following error:
Synchronizing Quotient
Copying /packages/source/Q/Quotient/Quotient-0.3.0.tar.gz
Traceback (most recent call last):
File "/usr/local/pep381client-1.5/scripts/pep381run", line 30, in <module>
state.synchronize()
File "/usr/local/pep381client-1.5/scripts/../pep381client/__init__.py",
line 119, in synchronize
self._synchronize()
File "/usr/local/pep381client-1.5/scripts/../pep381client/__init__.py",
line 159, in _synchronize
self.maybe_copy_file(project, file)
File "/usr/local/pep381client-1.5/scripts/../pep381client/__init__.py",
line 247, in maybe_copy_file
data = r.read()
File "/usr/lib64/python2.6/httplib.py", line 529, in read
s = self._safe_read(self.length)
File "/usr/lib64/python2.6/httplib.py", line 619, in _safe_read
chunk = self.fp.read(min(amt, MAXAMOUNT))
File "/usr/lib64/python2.6/socket.py", line 383, in read
data = self._sock.recv(left)
socket.error: [Errno 104] Connection reset by peer
I'm not sure if my problems could be caused by a transparent proxy or
if a.pypi.python.org is refusing my connection for another reason. My
source IP is 64.102.53.91. So far, my Pypi directory has 27GB
downloaded.
I'm more familiar with mirroring Linux distributions using rsync. If
there were a way to set up the initial Pypi mirror using rsync and
then fall back to pep381client to keep things in sync, that would be
great.
Thank you for any assistance in troubleshooting this problem.
/Brian/
More information about the Catalog-SIG
mailing list