My colleague has a Windows machine. He has passwordless SSH access to a
server with a darcs repo. He uses darcs 2.0.0. When he tries to darcs get,
the following error occures:

darcs failed: Not a repository: usernam@server:/home/user/repo ((scp) failed
to fetch: user@server:/home/user/repo/_darcs/inventory)

It yields the same error whether he tries it on a v1 or v2 repo. Get works
on my Linux machine without a problem.

My wild guess is there's some problem with the Windows and the SCP clien -
today he installed WinSCP, darcs get stopped working. He tried get once
before, when no WinSCP was installed, only PuTTY, it worked. Altough he now
uninstalled WinSCP and it didn't help.

I found a somewhatsimilar bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489352

Milan Cermak

Attachments

• unnamed

Thank you very much for this report. To figure out exactly what goes on here, we 
probably need some additional information. In the meantime, I hope that you have 
been able to proceed, for example by copying the repository from the server to 
the 
client using some other means, like packing it up as a zip-file or tar-file and 
transferring it by hand.

Here are some details that we would like to know more about:

1. What variant of Windows is your colleague using?
2. What ssh client is your colleague using on his Windows machine?
3. Is the server OS Windows as well or, if not, which OS is it? And which ssh 
server is being used?
4. Could you please give us the precise commands that fail? Both for get'ting 
the 
v1 repository and the v2 repository?
5. And also, please, the precise commands that succeed on your Linux machine?
6. And in addition, the darcs version and Linux version that you use?

I expect that the answers to these questions will help us proceed with this 
issue.

Thanks again and best regards
Thorkil

On Tue, Oct 28, 2008 at 6:39 PM, Thorkil Naur <bugs@darcs.net> wrote:

>
> Thorkil Naur <naur@post11.tele.dk> added the comment:
>
> Thank you very much for this report. To figure out exactly what goes on
> here, we
> probably need some additional information. In the meantime, I hope that you
> have
> been able to proceed, for example by copying the repository from the server
> to
> the
> client using some other means, like packing it up as a zip-file or tar-file
> and
> transferring it by hand.
>

This is no longer an issue. It looks like my colleague had forgot to run
Pageant, the SSH key handler in the PuTTY pack. We didn't notice it and
searched for the error elsewhere. Now it works fine.

Thank you for your help and sorry for the inconvenience.

Milan

>
>
> ----------
> priority:  -> bug
> status: unread -> chatting
>
> __________________________________
> Darcs bug tracker <bugs@darcs.net>
> <http://bugs.darcs.net/issue1135>
> __________________________________
>

Attachments

• unnamed

Thank you very much for letting us know. Setting issue resolved.

Best regards
Thorkil
On Thursday 30 October 2008 11:56, Milan Cermak wrote:
> 
> Milan Cermak <milan@soci.ali.sm> added the comment:
> 
> On Tue, Oct 28, 2008 at 6:39 PM, Thorkil Naur <bugs@darcs.net> wrote:
> 
> >
> > Thorkil Naur <naur@post11.tele.dk> added the comment:
> >
> > Thank you very much for this report. To figure out exactly what goes on
> > here, we
> > probably need some additional information. In the meantime, I hope that 
you
> > have
> > been able to proceed, for example by copying the repository from the 
server
> > to
> > the
> > client using some other means, like packing it up as a zip-file or 
tar-file
> > and
> > transferring it by hand.
> >
> 
> This is no longer an issue. It looks like my colleague had forgot to run
> Pageant, the SSH key handler in the PuTTY pack. We didn't notice it and
> searched for the error elsewhere. Now it works fine.
> 
> Thank you for your help and sorry for the inconvenience.
> 
> Milan
> 
> >
> >
> > ----------
> > priority:  -> bug
> > status: unread -> chatting
> >
> > __________________________________
> > Darcs bug tracker <bugs@darcs.net>
> > <http://bugs.darcs.net/issue1135>
> > __________________________________
> >
> 
> __________________________________
> Darcs bug tracker <bugs@darcs.net>
> <http://bugs.darcs.net/issue1135>
> __________________________________