Checkout of branch w/ long file names to deep path fails on Windows XP

[Bulgrien, Kevin]

> -----Original Message-----
> From: Martin Packman [mailto:martin.packman at canonical.com]
> Sent: Wednesday, August 22, 2012 10:37 AM
>
> On 22/08/2012, Bulgrien, Kevin <Kevin.Bulgrien at gdsatcom.com> wrote:
> ...
> > IOError: [Errno 2] No such file or directory:
> >
> u'C:/msys/1.0/home/kbulgrien/tmp/bzr/kbulgrien/windows_xp/mach
> ine2/.bzr/checkout/limbo/new-2/kbulgrien/Favorites/Hardware/Em
> ulation/Emulation
> > Technology, Inc. World Leader for IC Adapters, Test Clips,
> Sockets and IC
> > Testing Accessories for QFP, BGA, PGA, PBGA.url'
>
> This is just the Windows maximum path length limitation, see their
> documentation:
>
> <http://msdn.microsoft.com/library/windows/desktop/aa365247#maxpath>
>
> It's possible to hack around by forcing the use of UNC paths
> everywhere, but then you get into the situation of having filesystem
> objects you can't operate on using explorer or other normal windows
> tools.

Ah.  It's unfortunate that the tool could not report this explicitly as a (probable) cause for the failure, though I guess it's a toss up as to how much a cross-platform tool caters to platform-specific issues.

I also find it awkward that the entire operation fails just because one file operation failed.  It seems like the failure could be reported and Bazaar could just move along... even if such behavior had to be enabled by a switch to be compatible with opposing opinions.  I feel this is one of the most objectionable behaviors Bazaar has.  I have run into this propensity to roll over and die on a single fault over and over again.

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.