Closed GoogleCodeExporter closed 9 years ago
I'm trying to commit the presetDict.py, but keep getting:
cvs [commit aborted]: error writing to server: Connection reset by peer
Original comment by schulte....@gmail.com
on 20 Oct 2011 at 2:24
The RECOORD CVS archive is where the presetDict.py is stored. I just committed
to that without problem.
Chris can you try again. If it fails I can send you my jurgenfd pass if you
like.
Please show me the settings you used for the protons in T during next weeks
hangout.
NB CCPN is on SVN as Chris mentions.
***
cvs ci -m "- Testing syncing with CVS." -l
"/recoord/python/recoord2/presetDict.py"
Checking in python/recoord2/presetDict.py;
/ebi/cvs/recoord/recoord/python/recoord2/presetDict.py,v <-- presetDict.py
new revision: 1.29; previous revision: 1.28
done
ok (took 0:00.432)
***
Original comment by jurge...@gmail.com
on 24 Feb 2012 at 9:50
This time I get:
? saved_2lar_preset.py
? presetDict.pyc
? presetDict.py.backup
? not_msd
? backup_presetDict.py
? __init__.pyc
? Constants.pyc
cvs commit: Up-to-date check failed for `presetDict.py'
cvs [commit aborted]: correct above errors first!
cvs commit: Examining bmrb
cvs commit: Examining pdbe
It looks like your commit is blocking mine. I'll try an update first. Let's see.
Original comment by schulte....@gmail.com
on 24 Feb 2012 at 3:41
It looks like that one went through. Maybe it needed you to do something on
your end to make the server? I don't know. Dimitri and I spent quite some time
trying this and watching the socket log file, only to se the other end reject
us.
Anyway. This is great! I will set this to fixed, but will reopen it if need be.
cvs commit: Examining .
? saved_2lar_preset.py
? presetDict.pyc
? presetDict.py.backup
? not_msd
? backup_presetDict.py
? __init__.pyc
? Constants.pyc
Checking in presetDict.py;
/ebi/cvs/recoord/recoord/python/recoord2/presetDict.py,v <-- presetDict.py
new revision: 1.30; previous revision: 1.29
done
cvs commit: Examining bmrb
cvs commit: Examining pdbe
Original comment by schulte....@gmail.com
on 24 Feb 2012 at 3:48
Nice! Thanks for checking again.
Perhaps the resource was only down temporarily.
Original comment by jurge...@gmail.com
on 27 Feb 2012 at 8:51
Temporarily for months? Maybe it has something to do with servers being moved
around?
Original comment by schulte....@gmail.com
on 27 Feb 2012 at 3:05
Original issue reported on code.google.com by
schulte....@gmail.com
on 20 Oct 2011 at 2:22Attachments: