I've seen a thread on this but there was no conclusive answer, so I'm reopening this. I can't SCP updated PEPs to the SourceForge machine. The "pep2html.py -i" command just hangs. I can ssh into shell.sourceforge.net just fine, but scp just hangs. "scp -v" prints a bunch of things suggesting that it can authenticate itself just fine, ending with these three lines: cj20424-a.reston1.va.home.com: RSA authentication accepted by server. cj20424-a.reston1.va.home.com: Sending command: scp -v -t . cj20424-a.reston1.va.home.com: Entering interactive session. and then nothing. It just sits there. Would somebody please figure out a way to update the PEPs? It's kind of pathetic to see the website not have the latest versions... --Guido van Rossum (home page: http://www.python.org/~guido/)
On Thu, Dec 28, 2000 at 12:08:18PM -0500, Guido van Rossum wrote:
I've seen a thread on this but there was no conclusive answer, so I'm reopening this.
Actually there was: it's all SourceForge's fault. (At least that's my professional opinion ;) They honestly have a strange setup, though how strange and to what end I cannot tell.
Would somebody please figure out a way to update the PEPs? It's kind of pathetic to see the website not have the latest versions...
The way to update the peps is by ssh'ing into shell.sourceforge.net, and then scp'ing the files from your work repository to the htdocs/peps directory. That is, until SF fixes the scp problem. This method works (I just updated all PEPs to up-to-date CVS versions) but it's a bit cumbersome. And it only works if you have ssh access to your work environment. And it's damned hard to script; I tried playing with a single ssh command that did all the work, but between shell weirdness, scp weirdness and a genuine bash bug I couldn't figure it out. I assume that SF is aware of the severity of this problem, and is working on something akin to a fix or workaround. Until then, I can do an occasional update of the PEPs, for those that can't themselves. -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
On Thu, Dec 28, 2000 at 11:58:25PM +0100, Thomas Wouters wrote:
On Thu, Dec 28, 2000 at 12:08:18PM -0500, Guido van Rossum wrote:
[ blah blah ] And then they fixed it ! At least, for me, direct scp now works fine. (I should've tested that before posting my blah blah, sorry.) Anybody else, like people using F-secure ssh (unix or windows) experience the same ? -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
[Thomas Wouters]
And then they fixed it ! At least, for me, direct scp now works fine. (I should've tested that before posting my blah blah, sorry.)
I tried it immediately before posting my blah-blah yesterday, and it was still hanging.
Anybody else, like people using F-secure ssh (unix or windows) experience the same ?
Same here: I tried it again just now (under Win98 cmdline ssh/scp) and it worked fine! We're in business again. Thanks for fixing it, Thomas <wink>. now-if-only-we-could-get-python-dev-email-on-an-approximation-to-the- same-day-it's-sent-ly y'rs - tim
[Guido]
I've seen a thread on this but there was no conclusive answer, so I'm reopening this.
It hasn't budged an inch since then: your "Entering interactive session" problem is the same one everyone has; it gets reported on SF's bug and/or support managers at least daily; SF has not fixed it yet; these days they don't even respond to scp bug reports anymore; the cause appears to be SF's custom sfshell, and only SF can change that; the only known workarounds are to (a) modify files on SF directly (they suggest vi <wink>), or (b) initiate scp *from* SF, using your local machine as a server (if you can do that -- I cannot, or at least haven't succeeded).
On Thu, Dec 28, 2000 at 12:08:18PM -0500, Guido van Rossum wrote:
I've seen a thread on this but there was no conclusive answer, so I'm reopening this.
Actually there was: it's all SourceForge's fault. (At least that's my professional opinion ;) They honestly have a strange setup, though how strange and to what end I cannot tell.
Would somebody please figure out a way to update the PEPs? It's kind of pathetic to see the website not have the latest versions...
The way to update the peps is by ssh'ing into shell.sourceforge.net, and then scp'ing the files from your work repository to the htdocs/peps directory. That is, until SF fixes the scp problem. This method works (I just updated all PEPs to up-to-date CVS versions) but it's a bit cumbersome. And it only works if you have ssh access to your work environment. And it's damned hard to script; I tried playing with a single ssh command that did all the work, but between shell weirdness, scp weirdness and a genuine bash bug I couldn't figure it out. I assume that SF is aware of the severity of this problem, and is working on something akin to a fix or workaround. Until then, I can do an occasional update of the PEPs, for those that can't themselves. -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
On Thu, Dec 28, 2000 at 11:58:25PM +0100, Thomas Wouters wrote:
On Thu, Dec 28, 2000 at 12:08:18PM -0500, Guido van Rossum wrote:
[ blah blah ] And then they fixed it ! At least, for me, direct scp now works fine. (I should've tested that before posting my blah blah, sorry.) Anybody else, like people using F-secure ssh (unix or windows) experience the same ? -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
[Thomas Wouters]
And then they fixed it ! At least, for me, direct scp now works fine. (I should've tested that before posting my blah blah, sorry.)
I tried it immediately before posting my blah-blah yesterday, and it was still hanging.
Anybody else, like people using F-secure ssh (unix or windows) experience the same ?
Same here: I tried it again just now (under Win98 cmdline ssh/scp) and it worked fine! We're in business again. Thanks for fixing it, Thomas <wink>. now-if-only-we-could-get-python-dev-email-on-an-approximation-to-the- same-day-it's-sent-ly y'rs - tim
[Guido]
I've seen a thread on this but there was no conclusive answer, so I'm reopening this.
It hasn't budged an inch since then: your "Entering interactive session" problem is the same one everyone has; it gets reported on SF's bug and/or support managers at least daily; SF has not fixed it yet; these days they don't even respond to scp bug reports anymore; the cause appears to be SF's custom sfshell, and only SF can change that; the only known workarounds are to (a) modify files on SF directly (they suggest vi <wink>), or (b) initiate scp *from* SF, using your local machine as a server (if you can do that -- I cannot, or at least haven't succeeded).
participants (3)
-
Guido van Rossum -
Thomas Wouters -
Tim Peters