bazaar 1.2 (standalone) failed in cygwin shell

Bug #200436 reported by chen bin
2
Affects Status Importance Assigned to Milestone
Bazaar
Incomplete
Undecided
Unassigned

Bug Description

bazaar 1.2 (standalone) failed in cygwin shell when running command " bzr init-repo --no-tree sftp://<email address hidden>/~/repo", no output, no error message in .bzr.log.

if I run the same command in dos shell, it works.

Tags: cygwin
Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 200436] [NEW] bazaar 1.2 (standalone) failed in cygwin shell

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

chen bin пишет:
| Public bug reported:
|
| bazaar 1.2 (standalone) failed in cygwin shell when running command "
| bzr init-repo --no-tree sftp://<email address hidden>/~/repo", no
| output, no error message in .bzr.log.
|
| if I run the same command in dos shell, it works.

What kind of cygwin shell you are using?

I want to note that windows version of bzr is not intended to run on cygwin.
If you want to bzr works correctly on cygwin you need to install cygwin's native version.

 status incomplete
 tag cygwin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH1NQlzYr338mxwCURAgQoAJ9jemFlSzRVjsbEY7hUyhYS7+B4pgCfdeMC
GEIZIN5d6eiy/Vu9rEh3Ps0=
=RnjL
-----END PGP SIGNATURE-----

Changed in bzr:
status: New → Incomplete
Revision history for this message
chen bin (chenbin-sh) wrote :

I found this bug on my company's workstation. But I upgrade my cygwin
every week, so it should be the latest one.

I use bash.

cygwin's native bzr is too old.

I think the standalone version should work on cygwin shell. The only
issue may be path. But cygwin does provide tools like cygpath to
handle it.

Chen Bin

On Mon, Mar 10, 2008 at 5:24 PM, Alexander Belchenko <email address hidden> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> chen bin пишет:
>
> | Public bug reported:
> |
> | bazaar 1.2 (standalone) failed in cygwin shell when running command "
> | bzr init-repo --no-tree sftp://<email address hidden>/~/repo", no
> | output, no error message in .bzr.log.
> |
> | if I run the same command in dos shell, it works.
>
> What kind of cygwin shell you are using?
>
> I want to note that windows version of bzr is not intended to run on cygwin.
> If you want to bzr works correctly on cygwin you need to install cygwin's native version.
>
> status incomplete
> tag cygwin
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFH1NQlzYr338mxwCURAgQoAJ9jemFlSzRVjsbEY7hUyhYS7+B4pgCfdeMC
> GEIZIN5d6eiy/Vu9rEh3Ps0=
> =RnjL
> -----END PGP SIGNATURE-----
>
> ** Changed in: bzr
> Status: New => Incomplete
>
>
> --
> bazaar 1.2 (standalone) failed in cygwin shell
> https://bugs.launchpad.net/bugs/200436
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Incomplete
>
>
>
> Bug description:
> bazaar 1.2 (standalone) failed in cygwin shell when running command " bzr init-repo --no-tree sftp://<email address hidden>/~/repo", no output, no error message in .bzr.log.
>
> if I run the same command in dos shell, it works.
>

--
help me, help you.

Revision history for this message
Alexander Belchenko (bialix) wrote :

chen bin пишет:
> I found this bug on my company's workstation. But I upgrade my cygwin
> every week, so it should be the latest one.
>
> I use bash.
>
> cygwin's native bzr is too old.

AFAICT, cygwin's version is bzr 1.0. It's not too old. It's only 3 months old.

Revision history for this message
chen bin (chenbin-sh) wrote :

I think at least the win32 native version should detect the terminal
and give some warning message when running in cygwin.

On Mon, Mar 10, 2008 at 11:42 PM, Alexander Belchenko <email address hidden> wrote:
> *** This bug is a duplicate of bug 69851 ***
> https://bugs.launchpad.net/bugs/69851
>
> chen bin пишет:
>
> > I found this bug on my company's workstation. But I upgrade my cygwin
> > every week, so it should be the latest one.
> >
> > I use bash.
> >
> > cygwin's native bzr is too old.
>
> AFAICT, cygwin's version is bzr 1.0. It's not too old. It's only 3
> months old.
>
> --
>
>
> bazaar 1.2 (standalone) failed in cygwin shell
> https://bugs.launchpad.net/bugs/200436
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Incomplete
>
> Bug description:
> bazaar 1.2 (standalone) failed in cygwin shell when running command " bzr init-repo --no-tree sftp://<email address hidden>/~/repo", no output, no error message in .bzr.log.
>
> if I run the same command in dos shell, it works.
>

--
help me, help you.

Revision history for this message
Alexander Belchenko (bialix) wrote :

chen bin пишет:
> *** This bug is a duplicate of bug 69851 ***
> https://bugs.launchpad.net/bugs/69851
>
> I think at least the win32 native version should detect the terminal
> and give some warning message when running in cygwin.

bzr.exe is native windows version. It knows nothing about Cygwin.
And it should not know anything about Cygwin. It's out of scope it's
intended usage.

Revision history for this message
chen bin (chenbin-sh) wrote :

On Tue, Mar 11, 2008 at 9:54 AM, Alexander Belchenko <email address hidden> wrote:
> *** This bug is a duplicate of bug 69851 ***
> https://bugs.launchpad.net/bugs/69851
>
> chen bin пишет:
> > *** This bug is a duplicate of bug 69851 ***
> > https://bugs.launchpad.net/bugs/69851
> >
>
> > I think at least the win32 native version should detect the terminal
> > and give some warning message when running in cygwin.
>
> bzr.exe is native windows version. It knows nothing about Cygwin.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bzr.exe could try to run the command "uname" and grep the "CYGWIN"
from stdout, then it wounld display some warning message.

> And it should not know anything about Cygwin. It's out of scope it's
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It's actually a minor engineering problem about friendly interface
design instead of one related to programming philosophy.

I'm working for a commercial company. My boss always blames me (and
he's right) for such problems. Because it's MY responsibility to make
sure our softewares are robust , NOT our clients.

This bug happens at least twice,right? Although bzr is free, this bug
at least cost u and your company money and time on tech support.

> intended usage.
>
> --
>
>
> bazaar 1.2 (standalone) failed in cygwin shell
> https://bugs.launchpad.net/bugs/200436
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Incomplete
>
> Bug description:
> bazaar 1.2 (standalone) failed in cygwin shell when running command " bzr init-repo --no-tree sftp://<email address hidden>/~/repo", no output, no error message in .bzr.log.
>
> if I run the same command in dos shell, it works.
>

--
help me, help you.

Revision history for this message
Alexander Belchenko (bialix) wrote :

chen bin пишет:
>> bzr.exe is native windows version. It knows nothing about Cygwin.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> bzr.exe could try to run the command "uname" and grep the "CYGWIN"
> from stdout, then it wounld display some warning message.

I don't want to make bzr.exe slower. And it could be not enough in some cases.

>> And it should not know anything about Cygwin. It's out of scope it's
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> It's actually a minor engineering problem about friendly interface
> design instead of one related to programming philosophy.

There is nothing about friendliness IMO. It's only about using native functions
from msvcrt.dll (getpass)

> I'm working for a commercial company. My boss always blames me (and
> he's right) for such problems. Because it's MY responsibility to make
> sure our softewares are robust , NOT our clients.

I'm totally agree here. But all related to bzr.exe I do purely in my free
time and I have more important things to implement for proper windows
support.

>
> This bug happens at least twice,right? Although bzr is free, this bug
> at least cost u and your company money and time on tech support.

I think it's at least 3 times.

If you think you know how to solve it's problem in robust and efficient way --
please send us a patch.

Revision history for this message
chen bin (chenbin-sh) wrote :

I don't think to grep `uname ` for only once will influence the performance.

anyway, I'll give you a patch this weekend.

On Tue, Mar 11, 2008 at 6:15 PM, Alexander Belchenko <email address hidden> wrote:
> *** This bug is a duplicate of bug 69851 ***
> https://bugs.launchpad.net/bugs/69851
>
> chen bin пишет:
>
> >> bzr.exe is native windows version. It knows nothing about Cygwin.
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > bzr.exe could try to run the command "uname" and grep the "CYGWIN"
> > from stdout, then it wounld display some warning message.
>
> I don't want to make bzr.exe slower. And it could be not enough in some
> cases.
>
>
> >> And it should not know anything about Cygwin. It's out of scope it's
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > It's actually a minor engineering problem about friendly interface
> > design instead of one related to programming philosophy.
>
> There is nothing about friendliness IMO. It's only about using native functions
> from msvcrt.dll (getpass)
>
>
> > I'm working for a commercial company. My boss always blames me (and
> > he's right) for such problems. Because it's MY responsibility to make
> > sure our softewares are robust , NOT our clients.
>
> I'm totally agree here. But all related to bzr.exe I do purely in my free
> time and I have more important things to implement for proper windows
> support.
>
>
> >
> > This bug happens at least twice,right? Although bzr is free, this bug
> > at least cost u and your company money and time on tech support.
>
> I think it's at least 3 times.
>
> If you think you know how to solve it's problem in robust and efficient way --
> please send us a patch.
>
> --
>
>
> bazaar 1.2 (standalone) failed in cygwin shell
> https://bugs.launchpad.net/bugs/200436
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Incomplete
>
> Bug description:
> bazaar 1.2 (standalone) failed in cygwin shell when running command " bzr init-repo --no-tree sftp://<email address hidden>/~/repo", no output, no error message in .bzr.log.
>
> if I run the same command in dos shell, it works.
>

--
help me, help you.

Revision history for this message
Alexander Belchenko (bialix) wrote :

chen bin пишет:
> Public bug reported:
>
> bazaar 1.2 (standalone) failed in cygwin shell when running command "
> bzr init-repo --no-tree sftp://<email address hidden>/~/repo", no
> output, no error message in .bzr.log.

I re-read your bug description again.
It sounds like mysterious for me.

You said there is nothing in .bzr.log? Are you sure you looking into
proper .bzr.log? For bzr.exe it should be in My Documents folder.

Can you double check it one more time?

> if I run the same command in dos shell, it works.

Revision history for this message
Alexander Belchenko (bialix) wrote :

chen bin пишет:
> On Tue, Mar 11, 2008 at 9:54 AM, Alexander Belchenko <email address hidden> wrote:

>>> I think at least the win32 native version should detect the terminal
>> > and give some warning message when running in cygwin.
>>
>> bzr.exe is native windows version. It knows nothing about Cygwin.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> bzr.exe could try to run the command "uname" and grep the "CYGWIN"
> from stdout, then it wounld display some warning message.

If user have C:\cygwin\bin directory in his Windows $PATH environment variable
then even running from DOS shell you always get

C:>uname
CYGWIN_NT-5.0

So I don't think it's actually a solution.

Revision history for this message
Martin Pool (mbp) wrote :

> There is nothing about friendliness IMO. It's only about using native functions
> from msvcrt.dll (getpass)

So is that the heart of the problem, that getpass fails? Do we know
what happens exactly? If we call it from inside cygwin does it fail
and raise an exception, or just terminate the process?

--
Martin

Revision history for this message
Alexander Belchenko (bialix) wrote :

Martin Pool пишет:
> *** This bug is a duplicate of bug 69851 ***
> https://bugs.launchpad.net/bugs/69851
>
>> There is nothing about friendliness IMO. It's only about using native functions
>> from msvcrt.dll (getpass)
>
> So is that the heart of the problem, that getpass fails? Do we know
> what happens exactly? If we call it from inside cygwin does it fail
> and raise an exception, or just terminate the process?
>
In my understanding of situation getpass uses low-level access to stdin.
If there is no real terminal something bad will happen, i.e. it's effectively
blocking execution of bzr in the method get_nonechoed_password.

I sent a patch prevents this situation by explicit check sys.stdin.isatty()

http://bundlebuggy.aaronbentley.com/request/%3C47D70669.60702%40ukr.net%3E

But this not the end of story. There is another possible situation with Cygwin.
If I run Cygwin's bash console and from it run 'startx' then I could working in xterm
with Cygwin's terminal console floating on windows desktop. In this case the prompt for password
appears not in xterm window but in original terminal behind it!
In this case if user has xterm open in maximized mode he/she could not realize that
in back window something happens and waiting for the input.

Revision history for this message
chen bin (chenbin-sh) wrote :

I've already considered this situation. Only few geeks would do this
and I was one of them.

Adding cygwin/bin to $PATH was a nightmare because of some path
problems so I removed the cygwin/bin from my $PATH.

My solution is simple and has no side effect.

It will harm no one (even geeks) ff bzr reading from stdout and
display some warning message only when user typing "bzr help" and
"bzr init-repo".

The fact is it will definitely improve the current situation without
cost you more time on such a minor bug.

It's also maintainable solution, because every newbie programmer can
grep the the code fro warnning message and delete my patch.

It's simple, with no side effect, maintainable. So in my design
philosophy, it's perfect.

Chen bin

On Wed, Mar 12, 2008 at 3:05 AM, Alexander Belchenko <email address hidden> wrote:
> *** This bug is a duplicate of bug 69851 ***
> https://bugs.launchpad.net/bugs/69851
>
> chen bin пишет:
> > On Tue, Mar 11, 2008 at 9:54 AM, Alexander Belchenko <email address hidden> wrote:
>
>
> >>> I think at least the win32 native version should detect the terminal
> >> > and give some warning message when running in cygwin.
> >>
> >> bzr.exe is native windows version. It knows nothing about Cygwin.
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > bzr.exe could try to run the command "uname" and grep the "CYGWIN"
> > from stdout, then it wounld display some warning message.
>
> If user have C:\cygwin\bin directory in his Windows $PATH environment variable
> then even running from DOS shell you always get
>
> C:>uname
> CYGWIN_NT-5.0
>
> So I don't think it's actually a solution.
>
> --
>
>
> bazaar 1.2 (standalone) failed in cygwin shell
> https://bugs.launchpad.net/bugs/200436
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Incomplete
>
> Bug description:
> bazaar 1.2 (standalone) failed in cygwin shell when running command " bzr init-repo --no-tree sftp://<email address hidden>/~/repo", no output, no error message in .bzr.log.
>
> if I run the same command in dos shell, it works.
>

--
help me, help you.

Revision history for this message
Alexander Belchenko (bialix) wrote :
Revision history for this message
chen bin (chenbin-sh) wrote : chen_bin wants to keep up with you on Twitter

To find out more about Twitter, visit the link below:

http://twitter.com/i/99d6c5aa27c5e4f4296c6f987376a9ef5b95770c

Thanks,
-The Twitter Team

About Twitter

Twitter is a unique approach to communication and networking based on the simple concept of status. What are you doing? What are your friends doing—right now? With Twitter, you may answer this question over SMS, IM, or the Web and the responses are shared between contacts.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.