With darcs 2.7.98.1 (beta 1) on two machines, pulling from one to the
other repeats the ssh password prompt for every file fetched (five prompts
to pull one patch.) Downgrading the client (pulling) machine to darcs
2.5.2 restores the old behaviour (just one password prompt).
Correct me If I am wrong, but --packs and --no-packs are applicable
only to get. So, we cannot use --packs for darcs pull.
On Thu, Oct 13, 2011 at 6:44 PM, Mark Stosberg <bugs@darcs.net> wrote:
>
> Mark Stosberg <mark@summersault.com> added the comment:
>
> Can someone test with --packs and --nopacks and compare the results?
>
> __________________________________
> Darcs bug tracker <bugs@darcs.net>
> <http://bugs.darcs.net/issue2090>
> __________________________________
> _______________________________________________
> darcs-devel mailing list
> darcs-devel@darcs.net
> http://lists.osuosl.org/mailman/listinfo/darcs-devel
>
--
BSRK Aditya
I think patch686 (in screened) fixes this.
Simon: any chance you'd be free to write a test case, perhaps in the
spirit of tests/network/ssh.sh?
I envision grepping for darcs transfer-mode.
Slight problem is giving a server to connect to. I think I last tried
to fix that with an environment variable. I could be worth having a
default that the darcs team would use.
The following patch sent by Eric Kow <kowey@darcs.net> updated issue issue2090 with
status=has-patch
* Resolve issue2090: correctly detect existing transfer-mode connection.
Ignore-this: c392d370cd614c7a72be7d63f5d9da85
The actual resolution is a dependency included with ask-deps.
The following patch sent by Eric Kow <kowey@darcs.net> updated issue issue2090 with
status=resolved;resolvedin=2.8.0 HEAD
* Resolve issue2090: correctly detect existing transfer-mode connection.
Ignore-this: c392d370cd614c7a72be7d63f5d9da85
The actual resolution is a dependency included with ask-deps.