On Mon, Feb 21, 2005 at 10:11:14AM +0000, Steve McIntyre wrote: > On Mon, Feb 21, 2005 at 12:22:01AM -0800, Mark Symonds wrote: > >I noticed this: > > > >symonds:~$ echo $CVS_RSH > >SSH > >symonds:~$ cvs -d > >:ext:[EMAIL PROTECTED]:/home/user/cvsroot checkout . > >cvs [checkout aborted]: cannot exec rsh: No such file or directory > >cvs [checkout aborted]: end of file from server (consult above messages if > >any) > >symonds:~$ > > > >After looking around a bit, I noticed that there is > >no symlink /usr/bin/rsh -> /etc/alternatives/rsh > >...causing cvs to bail. > > > >Running update-alternatives --configure rsh didn't > >help since the symlink never existed in /usr/sbin. > > > >Perhaps I'm missing something here, but shouldn't that > >symlink exist? Not sure if this should go here, or > >to the SSH maintainer or both. > > CVS has no control over the rsh symlink, it merely uses it. That's the > job of the ssh package AFAIK. I'm reassigning this bug there in case > there is a bug in how that's being handled.
Several packages cooperate to do this, so it might or might not be ssh. Mark, has this system been incrementally upgraded from before about mid-2000? I do see some dodgy code in the postinst that could theoretically cause the /usr/bin/rsh symlink to go missing in that case, and I probably have an opportunity to clean it up. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
