With darcs 1.0.8, darcs changes --repodir foo works, but darcs changes
--repodir foo --context claims that it can't find the inventory file.

I apoligize if this is a duplicate.  I reported it once before, but as
far as I can see it never showed up in the tracker.

-Aaron

Hi, I can't reproduce this with 1.0.8.  Can you cook up a minimal test case, please?

Here is an example of this behaviour:

$ darcs --exact-version
darcs compiled on May  8 2007, at 09:50:57
# configured Fri Jun 16 14:55:21 EDT 2006
./configure --no-create --no-recursion

Context:

[TAG 1.0.8
Tommy Pettersson <ptp@lysator.liu.se>**20060616160213] 
$ uname -a
Darwin Thorkil-Naurs-Computer.local 8.9.0 Darwin Kernel Version 8.9.0: Thu Feb 
22 20:54:07 PST 2007; root:xnu-792.17.14~1/RELEASE_PPC Power Macintosh powerpc
$ mkdir Issue467Repo1
$ cd Issue467Repo1
$ darcs initialize
$ echo This is file1.txt >file1.txt
$ darcs add file1.txt
$ darcs record -a --author=Thorkil --patch-name=file1.txt
Finished recording patch 'file1.txt'
$ darcs changes --context

Context:

[file1.txt
Thorkil**20070801084349] 
$ darcs changes --context --repodir=.

Context:

[file1.txt
Thorkil**20070801084349] 
$ cd .. 
$ darcs changes --context --repodir=Issue467Repo1

darcs failed:  Not a repository: Issue467Repo1 (Issue467Repo1/_darcs/inventory: 
openBinaryFile: does not exist (No such file or directory))
$ ls -R Issue467Repo1
_darcs          file1.txt

Issue467Repo1/_darcs:
inventories     inventory       patches         prefs           pristine

Issue467Repo1/_darcs/inventories:

Issue467Repo1/_darcs/patches:
20070801084349-c19ed-b92a993114182b2a6be420c023d464d5939cd12d.gz        pending

Issue467Repo1/_darcs/prefs:
binaries        boring          motd

Issue467Repo1/_darcs/pristine:
file1.txt
$ 

Best regards
Thorkil

Wow, that's pretty weird.  I can confirm also that just --repodir=Issue467Repo1
does work, but adding --context makes it not understand what's going on.  Would
be worth seeing how it behaves in later darcs, though I suspect there won't be
any improvement.

Thanks for the test case!  You might even consider submitting it as a patch to
our test suite if you're feeling extra-helpful.

It also fails with darcs 1.0.9 on a SuSE Linux:

$ darcs --exact-version
darcs compiled on Jun 13 2007, at 21:47:50
# configured Sun Jun  3 18:53:47 EDT 2007
./configure

Context:

[TAG 1.0.9
Tommy Pettersson <ptp@lysator.liu.se>**20070603213706]
$ uname -a
Linux linux 2.6.13-15-default #1 Tue Sep 13 14:56:15 UTC 2005 i686 i686 i386 
GNU/Linux
$ mkdir Issue467Repo1
$ cd Issue467Repo1
$ darcs initialize
$ echo This is file1.txt >file1.txt
$ darcs add file1.txt
$ darcs record -a --author=Thorkil --patch-name=file1.txt
Finished recording patch 'file1.txt'
$ darcs changes --context

Context:

[file1.txt
Thorkil**20070801091041]
$ darcs changes --context --repodir=.

Context:

[file1.txt
Thorkil**20070801091041]
$ cd ..
$ darcs changes --context --repodir=Issue467Repo1

darcs failed:  Not a repository: Issue467Repo1 (Issue467Repo1/_darcs/inventory: 
openBinaryFile: does not exist (No such file or directory))
$ ls -R Issue467Repo1
Issue467Repo1:
_darcs  file1.txt

Issue467Repo1/_darcs:
inventories  inventory  patches  prefs  pristine

Issue467Repo1/_darcs/inventories:

Issue467Repo1/_darcs/patches:
20070801091041-c19ed-f3a7d3d4c5d6776ecbd7e10534c8a80ead82c604.gz  pending

Issue467Repo1/_darcs/prefs:
binaries  boring  motd

Issue467Repo1/_darcs/pristine:
file1.txt
$

Best regards
Thorkil

I noticed (in trying to reproduce this) that it only causes trouble when
the --repodir argument is a relative path.  When given an absolute path,
--context and --repodir work together fine.
-- 
David Roundy
Department of Physics
Oregon State University

I think these should do it... (see darcs-devel)

Wed Aug  1 20:40:51 CEST 2007  Eric Kow <eric.kow@gmail.com>
  * [issue467] changes --context --repodir

Wed Aug  1 20:41:38 CEST 2007  Eric Kow <eric.kow@gmail.com>
  * Add test for issue467.