I use CVS over SSH. However, cervisia on openSUSE 12.1 (x86_64) does not work. I have the following variables in my .bashrc file: export CVSROOT=":ext:gggggg@192.168.1.201:/usr/local/cvsroot" export CVS_RSH=ssh Using using CVS from the command line works perfectly. Cervisia reports a network timeout. Firing up tcpdump, I find that cervisia is attempting to connect to port 514 instead of 22. # tcpdump -np -i eth0 host 192.168.1.201 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 16:20:08.395584 ARP, Request who-has 192.168.1.201 tell 192.168.1.192, length 28 16:20:08.395911 ARP, Reply 192.168.1.201 is-at 00:11:25:ab:18:70, length 46 16:20:08.395919 IP 192.168.1.192.1023 > 192.168.1.201.514: Flags [S], seq 2619035686, win 14600, options [mss 1460,sackOK,TS val 253599527 ecr 0,nop,wscale 7], length 0 16:20:08.396150 IP 192.168.1.201.514 > 192.168.1.192.1023: Flags [R.], seq 0, ack 2619035687, win 0, length 0 16:20:09.396395 IP 192.168.1.192.1023 > 192.168.1.201.514: Flags [S], seq 2634688377, win 14600, options [mss 1460,sackOK,TS val 253600528 ecr 0,nop,wscale 7], length 0 16:20:09.396688 IP 192.168.1.201.514 > 192.168.1.192.1023: Flags [R.], seq 0, ack 15652692, win 0, length 0 16:20:11.396973 IP 192.168.1.192.1023 > 192.168.1.201.514: Flags [S], seq 2665947523, win 14600, options [mss 1460,sackOK,TS val 253602529 ecr 0,nop,wscale 7], length 0 16:20:11.397213 IP 192.168.1.201.514 > 192.168.1.192.1023: Flags [R.], seq 0, ack 46911838, win 0, length 0 The output I get in cervisia is: cvs -f -q update -l -d -P . 2>&1 192.168.1.201: Connection refused cvs [update aborted]: end of file from server (consult above messages if any) Reproducible: Always Steps to Reproduce: 1. Go into source directory, type "cervisia ./ &" 2. Cervisia starts up in that sandbox. 3. Right-click the top-level folder, click Update. Cervisia reports a network error (because its using the wrong port) Actual Results: Network error. Tcpdump shows cervisia's connection going to the wrong server port. Attempting 514, should be attempting 22. Expected Results: Expected cervisia to connect to the CVS server via ssh and report on the status of files that are under CVS control. I can find nothing in cervisia's setup that specifies port 514 anywhere (which is normally syslog). I tried putting "export CVS_CLIENT_PORT=22" into my .bashrc as well (any recycled the environment, of course), still no luck. This is a fresh install of openSuse 12.1 x86_64, with updates. However, my home directory has been copied from my older openSuse 11.4 x86 machine (not 64 bit) via rsync. On that machine, both CVS and cervisia worked correctly. Any help would be appreciated.
I should also note: In cervisia, under 'Repository', selecting the only entry and hitting 'Modify', I have also tried putting both "ssh" and "ssh -p 22" (without the quotes) in the "Use remote shell:" field. Initially it was blank. None of those 3 settings worked either
Created attachment 73688 [details] attachment-16722-0.html Hi On Tuesday 04 September 2012 21:56:54 gregry_7@yahoo.com wrote: > https://bugs.kde.org/show_bug.cgi?id=306269 > > --- Comment #1 from gregry_7@yahoo.com --- > I should also note: In cervisia, under 'Repository', selecting the only > entry and hitting 'Modify', does that entry look like ":ext:gggggg@192.168.1.201:/usr/local/cvsroot"? > I have also tried putting both "ssh" and "ssh > -p 22" (without the quotes) in the "Use remote shell:" field. Initially it > was blank. None of those 3 settings worked either If you're using ssh it should be ssh. Do you use ssh_agent? I've no clue how Cervisia would use port 514. Are you sure that it's really Cervisia and not another program? Cheers, André
Andre, Thanks for your reply. > does that entry look like ":ext:gggggg@192.168.1.201:/usr/local/cvsroot"? Yes, the contents of Repository->Modify->Repository exactly matches the CVSROOT environment variable. > If you're using ssh it should be ssh. > > Do you use ssh_agent? If I do use ssh_agent, it's not intentional. How would I tell? > I've no clue how Cervisia would use port 514. Are you sure that it's really Cervisia and not another program? I'm certain its not another application. It's Cervisia, or something that it invokes. Your comments about "Use remote shell:" needing to be "ssh" made me try that again. I believe I have found a different bug that somewhat explains the issue, but it can be worked around. Initially, my "Use remote shell:" field was empty. I tried setting it to "ssh" and doing an update, but I still saw the same behavior (tcp connection attempted to port 514 of the server instead of 22). Today, I also ran "ps aux --forest" meanwhile. Although the "Use remote shell:" was changed to "ssh" in Cervisia, its still using rsh. If I return to the "Use remote shell:" settings, it shows the "ssh" that I placed there, even though rsh was invoked. See attachment. However, If I leave that set to "ssh", close and restart cervisia, then do an update, it works. Then, it correctly invokes ssh instead of rsh. Thanks for your help. ________________________________ From: Andre Woebbeking <woebbeking@kde.org> To: gregry_7@yahoo.com Sent: Wednesday, September 5, 2012 4:21 PM Subject: [Bug 306269] cervisia with cvs over ssh goes to wrong port number https://bugs.kde.org/show_bug.cgi?id=306269 --- Comment #2 from Andre Woebbeking <woebbeking@kde.org> --- Hi On Tuesday 04 September 2012 21:56:54 gregry_7@yahoo.com wrote: > https://bugs.kde.org/show_bug.cgi?id=306269 > > --- Comment #1 from gregry_7@yahoo.com --- > I should also note: In cervisia, under 'Repository', selecting the only > entry and hitting 'Modify', does that entry look like ":ext:gggggg@192.168.1.201:/usr/local/cvsroot"? > I have also tried putting both "ssh" and "ssh > -p 22" (without the quotes) in the "Use remote shell:" field. Initially it > was blank. None of those 3 settings worked either If you're using ssh it should be ssh. Do you use ssh_agent? I've no clue how Cervisia would use port 514. Are you sure that it's really Cervisia and not another program? Cheers, André
Created attachment 73689 [details] attachment-16722-1.dat
Created attachment 73690 [details] cervisia.txt
Hmm, I replied to your email from yahoo's webmail, and my comment shows up as an attachment... I'll re-paste it here. Andre, Thanks for your reply. > does that entry look like ":ext:gggggg@192.168.1.201:/usr/local/cvsroot"? Yes, the contents of Repository->Modify->Repository exactly matches the CVSROOT environment variable. > If you're using ssh it should be ssh. > > Do you use ssh_agent? If I do use ssh_agent, it's not intentional. How would I tell? > I've no clue how Cervisia would use port 514. Are you sure that it's really Cervisia and not another program? I'm certain its not another application. It's Cervisia, or something that it invokes. Your comments about "Use remote shell:" needing to be "ssh" made me try that again. I believe I have found a different bug that somewhat explains the issue, but it can be worked around. Initially, my "Use remote shell:" field was empty. I tried setting it to "ssh" and doing an update, but I still saw the same behavior (tcp connection attempted to port 514 of the server instead of 22). Today, I also ran "ps aux --forest" meanwhile. Although the "Use remote shell:" was changed to "ssh" in Cervisia, its still using rsh. If I return to the "Use remote shell:" settings, it shows the "ssh" that I placed there, even though rsh was invoked. See attachment. However, If I leave that set to "ssh", close and restart cervisia, then do an update, it works. Then, it correctly invokes ssh instead of rsh. Thanks for your help.
To be thorough about the bug report, I guess it should also be noted that the value of environment variable CVS_RSH (which has been set to "ssh" all along) being ignored seems to also be a bug.
> --- Comment #3 from gregry_7@yahoo.com --- > > Do you use ssh_agent? > > If I do use ssh_agent, it's not intentional. How would I tell? Well, it makes your life much easier if you use ssh keys with passphrase. If you use it it's normally started with your session and if you add a passphrase to it that passphrase is cached by the agent and applied when you use ssh. > Your comments about "Use remote shell:" needing to be "ssh" made me try that > again. I believe I have found a different bug that somewhat explains the > issue, but it can be worked around. > > Initially, my "Use remote shell:" field was empty. Because not everyone uses ssh. > I tried setting it to > "ssh" and doing an update, but I still saw the same behavior (tcp > connection attempted to port 514 of the server instead of 22). Today, I > also ran "ps aux --forest" meanwhile. Although the "Use remote shell:" was > changed to "ssh" in Cervisia, its still using rsh. If I return to the "Use > remote shell:" settings, it shows the "ssh" that I placed there, even > though rsh was invoked. See attachment. > > However, If I leave that set to "ssh", close and restart cervisia, then do > an update, it works. Then, it correctly invokes ssh instead of rsh. That sounds like a bug. If you configure ssh as remote shell it should be used immediately and not after next startup. > Thanks for your help. You're welcome. > --- Comment #7 from gregry_7@yahoo.com --- > To be thorough about the bug report, I guess it should also be noted that > the value of environment variable CVS_RSH (which has been set to "ssh" all > along) being ignored seems to also be a bug. I'd call that a feature request :-) Cervisia doesn't look into CVS_RSH it only sets it when calling CVS. Cervisia was probably made for people who don't care about enviroment variables.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!