bialix at ukr.net
Sat Apr 12 23:12:27 BST 2008
Dave Compton пишет:
> The point that I was trying to make is that the first time cygwin/bazaar user
> has no way of knowing what to do when he sees this error message. An
> improvement that does not involve the cygwin maintainers would be to enhance the
> error message. Perhaps something like:
> "bzr: ERROR: cygwin bzr does not work for external operations. You may want to
> use the native windows version instead."
> Of course, this message should be only on cygwin and only when this particular
> error happens in this particular context.
> Yes, the ideal would be for the cygwin folks to fix the underlying problem. In
> the meantime, a better error message would be helpful. Bear in mind that "The
> primary focus of the development team is to produce a revision control tool that
> the *free software community will LOVE to use*." (quoted from
> http://bazaar-vcs.org/Bzr). Helpful error messages are important for a tool
> that people love to use.
Yes, and anybody free to write corresponding patch.
> The cygwin maintainers were notified about this bug in January of this year:
> - Dave
> Alexander Belchenko wrote:
>> Dave Compton пишет:
>>> Alexander Belchenko wrote:
>>>> Russel Winder пишет:
>>>>> Generally I avoid all use of Windows, but from time to time I have to in
>>>>> order to test Gant to make sure it works on Windows.
>>>>> I have a Bazaar branch on which I can do "bzr info" and "bzr status" and
>>>>> I get the results I expect but "bzr update" leads to:
>>>>> bzr: ERROR: [Errno 0] Error
>>>>> not the most informative message :-) I am using Bazaar from Cygwin
>>>>> which is 1.0.0 on Python 2.5.1, the repository is in pack-0.92 format.
>>>>> Is this just a problem the answer to which is "we have to wait till
>>>>> Cygwin updates to a newer version"?
>>>> Well, it will be nice if next time you'll using different subject line, e.g.:
>>>> "Cygwin issue".
>>>> Without looking at .bzr.log I can't say for sure why you have this message,
>>>> but there is at least one known serious bug re bzr on Cygwin:
>>>> Looks very similar to your problem.
>>> Although this is almost certainly a cygwin bug, from the user's perspective
>>> it looks like a bzr failure.
>> I understand that for non-Python users it looks like bzr failure.
>> But in fact this error occurs in PyCrypto library that used by Paramiko library,
>> and Bazaar used Paramiko library directly.
>> So actually bug occurs not in bzr itself, but at 2 layers lower.
>> You need to ping Cygwins maintainers to fix or workaround this.
>>> This probably discourages a number of first time Bazaar users on windows -
>>> some to the point of giving up entirely on Bazaar.
>> You guys have strange habits to call Cygwin by name windows.
>> I don't understand why.
>>> Is there be any way to do *something* more immediate to help a cygwin/bzr
>>> user who sees this problem? Maybe the cygwin bug can be coded around. If
>>> not, could the error message be changed to give some direction regarding what
>>> the user can do to work around the problem?
>> I don't know. I'm not expert in Cygwin and prefer to not using it when I can.
More information about the bazaar