[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnu-arch] [bug #5031] sftp access fails oddly - better error handli

From: nobody
Subject: [Bug-gnu-arch] [bug #5031] sftp access fails oddly - better error handling or docs would be nice
Date: Thu, 02 Oct 2003 03:45:14 -0400
User-agent: w3m/

=================== BUG #5031: LATEST MODIFICATIONS ==================

Changes by: Scott Parish <address@hidden>
Date: Thu 10/02/2003 at 07:45 (GMT)

            What     | Removed                   | Added
                  CC |                           | srp

=================== BUG #5031: FULL BUG SNAPSHOT ===================

Submitted by: tjl                     Project: GNU arch -- a revision control 
Submitted on: Tue 09/02/2003 at 06:57
Category:  tla                        Severity:  5 - Major                  
Bug Group:  bug                       Resolution:  None                     
Status:  Open                         Release:  1.1-pre5                    
Fixed Release:                        Merge Request?:  None                 
Your Archive Name:                    Your Archive Location:                
Assigned to:  None                    

Summary:  sftp access fails oddly - better error handling or docs would be nice

Original Submission:  Running a sftp command (any other one using sftp as well)

produces the following output. What's going on?

$ tla make-archive --mirror address@hidden sftp://address@hidden/testarch2

usage: sftp [-vC1] [-b batchfile] [-o option] [-s subsystem|path] [-B 

            [-F config] [-P direct server path] [-S program]

            address@hidden:file [file]]

Error reading from serve

Follow-up Comments

Date: Thu 10/02/2003 at 07:35       By: None
There is a patch in software.srparish.net--2003tla/tla--devo--1.0 which

passes ssh the '-2' flag to enforce the use of only ssh version 2.

Date: Thu 09/04/2003 at 10:04       By: tjl
Yes, that seems to solve the problem.

However, my original bug report still stands: documenting this (even as simply 
as a "Make sure your ssh is connecting with protocol version 2" in the error 
output) would help a lot.

Date: Thu 09/04/2003 at 06:58       By: aderuwe
This is probably due to your ssh configuration.

Have a look at these posts to the mailing list:




CC List

CC Address                          | Comment
srp                                 | 

No files currently attached

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]