WindowsError: [Error 5]

[Bulgrien, Kevin]

> -----Original Message-----
> I thought it might relate to that. So there is currently no
> way of forcing bzr to not look in those locations?
>
> Is it a bug that's likely to see a fix in the near future?

The silence probably means "no", but then you can use bzr
from a command prompt to workaround it - that is what I have
to do since I have not gotten to the point where I think it
is reasonable for me to ramp up on the skills needed to fix
it myself.

Command line bzr also unnecessarily chokes and dies on file
read faults when it could forge ahead with a message instead
of just giving up, but on the command-line you can direct
areas of the filesystem to traverse with more precision.  I
personnally feel this is a lot about philosophy of how
errors are handled as much as it is about usability.

This issue is rather sad in that I am in a position to have
to select a VCS that is friendly for users that do not like
command-line tools, and who are not software developers.
Not finding sympathy for issues like this this seems to mean
that the tools are primarily supported for use-cases that
are limited to traditional software development.  I want to
pick a new VCS that lets me leverage benefits for both
software development and other kinds of tasks.

This message and/or attachments may include information subject to GD Corporate Policy 07-105 and is intended to be accessed only by authorized personnel of General Dynamics and approved service providers.  Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties.  Recipients should refer to the policies or contract to determine proper handling.  Unauthorized review, use, disclosure or distribution is prohibited.  If you are not an intended recipient, please contact the sender and destroy all copies of the original message.