Re: libsasl2 2.1.25-1 incompatible with latest openldap. (ATTN: openldap maintainer)

2012-06-22 Thread David Rothenberger
On 6/22/2012 3:08 PM, Andrew Branson wrote: > Hi, > > After updating my cygwin yesterday, my openldap slapd failed to start, > giving the following output: > > $ /usr/sbin/slapd -d 1 -f /etc/openldap/slapd.conf > @(#) $OpenLDAP: slapd 2.3.43 (Mar 26 2012 13:27:31) $ > > vzell@vzell-de:/misc/src/

libsasl2 2.1.25-1 incompatible with latest openldap.

2012-06-22 Thread Andrew Branson
Hi, After updating my cygwin yesterday, my openldap slapd failed to start, giving the following output: $ /usr/sbin/slapd -d 1 -f /etc/openldap/slapd.conf @(#) $OpenLDAP: slapd 2.3.43 (Mar 26 2012 13:27:31) $ vzell@vzell-de:/misc/src/release/openldap-2.3.43-3/build/servers/slapd daemon_init:

Re: cygwin 1.7.15-1 - .NET console output locks up mintty

2012-06-22 Thread Andrey Repin
Greetings, Jamie Briggs! >> > I have noticed a problem with the "cygwin: The Unix emulation engine" >> > package, >> > version 1.7.15-1. Output from .NET console does not show up, the console >> > (mintty) becomes unresponsive and must be killed. >> >> > Reverting back to 1.7.14-2 fixes the p

Re: stdout not visible on some programs after upgrading from to 1.7.11-1 to 1.7.15-1

2012-06-22 Thread Brian Cavagnolo
On Wed, Jun 20, 2012 at 1:39 PM, James Johnston wrote: >> -Original Message- >> Sent: Wednesday, June 20, 2012 16:27 >> Subject: stdout not visible on some programs after upgrading from to > 1.7.11- >> 1 to 1.7.15-1 >> >> Hello, >> >> I use cygwin on a windows 7 machine to automate a Visua

Re: cygwin 1.7.15-1 - .NET console output locks up mintty

2012-06-22 Thread Jamie Briggs
On Fri, Jun 22, 2012 at 02:49:20PM +0400, Andrey Repin wrote: > Greetings, Jamie Briggs! > > > I have noticed a problem with the â"cygwin: The Unix emulation engine" > > package, > > version 1.7.15-1. Output from .NET console does not show up, the console > > (mintty) becomes unresponsive and mu

RE: cygwin 1.7.15-1 - .NET console output locks up mintty

2012-06-22 Thread James Johnston
> -Original Message- > Sent: Friday, June 22, 2012 02:22 > Subject: cygwin 1.7.15-1 - .NET console output locks up mintty > > I have noticed a problem with the â"cygwin: The Unix emulation engine" > package, version 1.7.15-1. Output from .NET console does not show up, the > console > (min

Re: cygwin 1.7.15-1 - .NET console output locks up mintty

2012-06-22 Thread Earnie Boyd
On Thu, Jun 21, 2012 at 10:21 PM, Jamie Briggs wrote: > This results in no output and an unresponsive mintty under 1.7.15-1.  If > "cmd.exe" is ran on top of bash and then HelloWorld is ran there it does the > same thing.  After reverting to 1.7.14-2 everything is working normally again. Does the

Re: RCS file corruption.

2012-06-22 Thread Andrey Repin
Greetings, Richard Gribble! >> > One thing I may have failed to mention is that (anecdotaly - I didn't >> > take copious notes) the problem usually appeared when I had lines with >> > two "^M"s at the end.  I suspect this happens because sometimes I edit >> > the files on my Linux box and sometime

Re: cygwin 1.7.15-1 - .NET console output locks up mintty

2012-06-22 Thread Andrey Repin
Greetings, Jamie Briggs! > I have noticed a problem with the â"cygwin: The Unix emulation engine" > package, > version 1.7.15-1. Output from .NET console does not show up, the console > (mintty) becomes unresponsive and must be killed. > Reverting back to 1.7.14-2 fixes the problem. > The pr

Re: Cygwin unstable as hell on Windows7 64bit‏

2012-06-22 Thread Gerard H. Pille
As suggested, I did a "set CYGWIN=detect_bloda" before running cygwin.bat, but that didn't produce any output. It seems as if the shells are the most vulnerable. Quite often, working in vi, I get thrown out, with "You have running jobs". After a "^Jtty sane^J" and "fg", I can terminate vi al