Setup:

Server:
Ubuntu 8.0.4
darcs 2.3.1
Create a repository in the root directory (/)

Client:
Ubuntu 8.0.4
Running darcs 2.3.1
Try to pull the repository from server with command:

darcs get root@kamus.it:/

or:

darcs get root@kamus.it:/

I get:

Invalid repository:  root@kamus.it:.

darcs failed:  (scp) failed to fetch: root@kamus.it:./_darcs/hashed_inventory


Regards,

        titto




-- 
Pasqualino "Titto" Assini, Ph.D.
http://quicquid.org/

Yuck, another filepath parsing bug (it seems).

Unless I'm missing something, this isn't something we can easily represent in 
our functional test suite (bunch of shell scripts) because of the remote server 
requirement.

So it looks like we just need somebody to develop some unit tests instead, one 
that will help us reproduce the error.

Titto: if you're familiar with Haskell, we'd love some help :-)

Titto: actually, have a look at tests/external.sh
We test SSH stuff there by setting DARCS_SSH to some shell script.

Do you think I might be able to interest you in writing a regression test for 
this?

Hints on how to do this: http://wiki.darcs.net/Development/RegressionTests

Hi Eric,

testing the bug is easy and does not require a remote server as one
can ssh to his own local machine.

However, is it acceptable to have a test that creates (temporarily) a
darcs repo in the tester's machine root directory?

    titto

2009/12/15 Eric Kow <bugs@darcs.net>:
>
> Eric Kow <kowey@darcs.net> added the comment:
>
> Titto: actually, have a look at tests/external.sh
> We test SSH stuff there by setting DARCS_SSH to some shell script.
>
> Do you think I might be able to interest you in writing a regression test for
> this?
>
> Hints on how to do this: http://wiki.darcs.net/Development/RegressionTests
>
> ----------
> assignedto:  -> tittoassini
>
> __________________________________
> Darcs bug tracker <bugs@darcs.net>
> <http://bugs.darcs.net/issue1718>
> __________________________________
>



-- 
Pasqualino "Titto" Assini, Ph.D.
http://quicquid.org/

On Tue, Dec 15, 2009 at 13:33:36 +0100, Pasqualino Titto Assini wrote:
> testing the bug is easy and does not require a remote server as one
> can ssh to his own local machine.

Right you are, but it's still not completely easy as it requires that
the user is running ssh on his local machine that it's configured to let
the user log in without some kind of intervention (password, key).

> However, is it acceptable to have a test that creates (temporarily) a
> darcs repo in the tester's machine root directory?

Whoops, no I don't think that's acceptable; I guess I was implicitly
hoping there would be a way to do without (for example, check for one
error message [not a repo] vs another [no path found: ./]

Perhaps we have to go the unit testing route after all (of course,
you could also argue that we ought to have unit tests *anyway*)...

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9

So it looks like the route of developing an automated test first is not
going to work for this.  So what we really need is for somebody to
investigate the cause of this, one likely culprit being the filepath
handling code.