On 2013-02-12 06:30:46 +0000, Christian Theune said:
On 2013-02-12 04:49:42 +0000, Richard Jones said:
On 12 February 2013 01:37, Christian Theune <c...@gocept.com> wrote:
Yesterday it started trying to sync lxml which seems to take longer than 25
minutes which is my timeout for a single sync.
There were some OSU connectivity issues yesterday which were
investigated and I assume cleared up. Could they have been the cause
of this problem?
Dunno - none of the mirrors affected (d-f) have caught up yet. Looking
at my logs it seems that it had to restart syncing from scratch yet
again as it's syncing something around the D packages.
Well. Actually it looks like it broke its status again:
Traceback (most recent call last):
File "/opt/pep381client/dev/pep381client/scripts/pep381run", line 25,
in <module>
state = pep381client.Synchronization.load(targetdir)
File
"/opt/pep381client/dev/pep381client/scripts/../pep381client/__init__.py",
line 121, in load
res = cPickle.load(open(os.path.join(homedir, "status"), "rb"))
\switchesr\UickleGet: etsango-libsr\Usmssluzbacz-apir\Uscikits.vectorplotr
I'm resyncing this now completely, yet again, trying to avoid
pause/resume cycles.
Christian
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG@python.org
http://mail.python.org/mailman/listinfo/catalog-sig
