add fails with "No such file" on win32

Hi mmartin, thanks for the report.

What happens if you cd to q:\archive and then try 'bzr add myfile.txt'?

The error happens the same way regardless of CWD . Also happends if tbzr is used.

2009/5/21 mgm <email address hidden>:
> The error happens the same way regardless of CWD . Also happends if tbzr
> is used.

Could you please post the traceback shown by 'bzr -Derror add myfile.txt'?

--
Martin <http://launchpad.net/~mbp/>

I guess the email reply didn't work. Here is the traceback:

Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 727, in exception_to_return_code
  File "bzrlib\commands.pyo", line 922, in run_bzr
  File "bzrlib\commands.pyo", line 559, in run_argv_aliases
  File "bzrlib\builtins.pyo", line 587, in run
  File "bzrlib\mutabletree.pyo", line 52, in tree_write_locked
  File "bzrlib\mutabletree.pyo", line 392, in smart_add
  File "bzrlib\osutils.pyo", line 1728, in file_kind
NoSuchFile: No such file: u'Q:/rchive/myfile.txt'

2009/5/27 mgm <email address hidden>:
> I guess the email reply didn't work. Here is the traceback:
>
> Traceback (most recent call last):
>  File "bzrlib\commands.pyo", line 727, in exception_to_return_code
>  File "bzrlib\commands.pyo", line 922, in run_bzr
>  File "bzrlib\commands.pyo", line 559, in run_argv_aliases
>  File "bzrlib\builtins.pyo", line 587, in run
>  File "bzrlib\mutabletree.pyo", line 52, in tree_write_locked
>  File "bzrlib\mutabletree.pyo", line 392, in smart_add
>  File "bzrlib\osutils.pyo", line 1728, in file_kind
> NoSuchFile: No such file: u'Q:/rchive/myfile.txt'
>

So, for the sake of not jumping to conclusions, is the directory name
actually 'rchive' or 'archive' and a character is being lost
somewhere? If the latter it's quite mysterious, but it would explain
why we get command not found.

--
Martin <http://launchpad.net/~mbp/>

Per the original bug report, the file of interest in this example is "Q:\archive\myfile.txt". BZR is somehow cutting off the first letter of the path (beyond the drive letter). It certainly is quite mysterious.

On Thu, May 28, 2009 at 03:36:54AM -0000, mgm wrote:
> Per the original bug report, the file of interest in this example is
> "Q:\archive\myfile.txt". BZR is somehow cutting off the first letter of
> the path (beyond the drive letter). It certainly is quite mysterious.

The escape sequence '\a' is the ascii Bell. Could you try:

    bzr add Q:/archive/myfile.txt

instead of

    bzr add Q:\archive\myfile.txt

If that works, Windows path handling is going wrong somewhere. If it
doesn't, something else is up.

Wouter van Heyst

Same result regardless of using forward or back slashes, or changing to the directory interest and adding the file without a path.

To be clear:
    bzr add Q:/archive/myfile.txt
    bzr add Q:\archive\myfile.txt
and
   q:
   cd archive
   bzr add myfile.txt

All give the same error.

I have answered all questions and this bug is still marked as "incomplete". Is anyone out there ?

Hi,

I agree the bug's complete though I personally don't know what could be causing this. I see you said in the early comment it happens regardless of cwd. Does it happen if you use a different path like "c:\test\"?

(btw you can change the bug status yourself if you think it's no longer incomplete.)