#1 Cygwin SCP doesn't understand drive letters

closed
nobody
None
5
2004-03-05
2003-07-03
Cory Dodt
No

I have the following:

:attr
{fetch=scp://foo@my.foo.org//home/foo/python.files.1.zip}
dist/packages/python.files.1.zip

When I :fetchall, this results in the output:

Aap: Attempting download of
"scp://foo@my.foo.org//home/foo/python.files.1.zip"
Aap: {interactive} C:\cygwin\bin\scp.EXE -C -p
foo@my.foo.org:/home/foo/python.files.1.zip
C:\cygwin\home\cory\aap\cache\31195839.files.1.zip
ssh: C: Temporary failure in name resolution
lost connection

On the line beginning "Aap: {interactive}" I can see
the command line that's being used to invoke scp, and
it has as the target file
C:\cygwin\home\cory\aap\cache\31195839.files.1.zip.
This is not allowed by scp, because it splits all names
up into hostname:target at the colon.

If I manually enter the command this way:

C:\cygwin\bin\scp.EXE -C -p
foo@my.foo.org:/home/foo/python.files.1.zip
/home/cory/aap/cache/31195839.files.1.zip

... obeying Cygwin filesystem semantics, then it works.
I know there's an issue on the todo list for handling
slashes better, but this is a different angle on the
problem; here, the problem is not the slashes but the
presence of a drive letter in a path.

If there is a way to detect what filesystem semantics
the tool expects, A-A-P should try to use the cygpath
tool to fix filenames.

Here's my workaround:

=== in main.aap ===
SCP=bash aapscp

=== in aapscp ===
#!sh
scp -C -p $1 `cygpath $2`

Discussion

  • Bram Moolenaar
    Bram Moolenaar
    2004-03-05

    Logged In: YES
    user_id=57665

    This is a problem in using the Cygwin scp command. Aap
    supports using the scp command from Putty, it works as expected.

    Since this is on MS-Windows, MS-Windows file names are used.
    Thus the problem is with the cygwin command, it should
    recognize the MS-Windows file name.

     
  • Bram Moolenaar
    Bram Moolenaar
    2004-03-05

    • status: open --> closed