Re: [Sandweb-devel] debian package broken

[Micah A. <mi...@ri...>]

On Fri, 08 Aug 2003, Rob Helmer wrote:

> On Fri, 8 Aug 2003 2:25PM -0800, Micah Anderson wrote:
> >micah@miso:~$ sudo su - www-data
> >www-data@miso:~$ ssh mi...@mi...
> >mi...@mi...'s password:
> 
> Hmm.. Well at least we know it's not the ssh  connection that's the 
> problem.
> 
> >Yes, debian stable/woody/3.0.
> 
> Ok, that's what I produce the .deb on.
> Hmm.. You haven't installed from the .tar.gz distribution of sandweb 
> (doing "make install") on this system before, have you?

Nope, I've only done it via the package, I was excited to see a debian
package so I wanted to do it that way :)

> 
> >The weird thing is that I dont get a chance to respond to the first
> >one, it prints them both out and I can only type on the second one.
> 
> Weird. Could be a bug in the sandweb-expect script..
> Either that or the sandweb-ssh script, which wraps around SSH so we can 
> pass params via the CVS_RSH setting.
> 
> Let's try to figure out where the prob is. Try:
> su - www-data
> export CVS_RSH=/usr/bin/sandweb-ssh
> export CVSROOT=:ext:micah@host:/cvsroot/
> cvs co module

micah@miso:~$ sudo su - www-data
Password:
www-data@miso:~$ export CVS_RSH=/usr/bin/sandweb-ssh
www-data@miso:~$ export
CVSROOT=:ext:mi...@mi...:/var/www/webwml/
www-data@miso:~$ mkdir tmp
www-data@miso:~$ cd tmp
www-data@miso:~/tmp$ cvs co web
cvs checkout: warning: unrecognized response Note: SSH_BIN must
already be defined!' from cvs server
cvs checkout: warning: unrecognized response Syntax:
/usr/bin/sandweb-ssh <ssh args>' from cvs server
cvs [checkout aborted]: end of file from server (consult above
messages if any)


That didn't work... so I decided to try and set SSH_BIN as it said:

www-data@miso:~/tmp$ export SSH_BIN=/usr/bin/sandweb-ssh
www-data@miso:~/tmp$ cvs co web

then it hangs... nothing.


> 
> (substitute the real host, cvsroot and module of course..)
> 
> Thanks for helping to troubleshoot this! This particular exercise will 
> let us know if it's the problem is being caused by the sandweb-ssh or 
> the sandweb-expect script.

No problem! I'm glad you are helping me figure this out too, so it is
mutually appreciated :)

Micah