X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 24 Jun 2009 09:57:42 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: bash-3.2.49-22 Message-ID: <20090624075742.GB7289@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jun 23 20:14, Eric Blake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > A new release of bash, 3.2.49-22, has been uploaded, replacing 3.2.48-21 > as current, and leaving 3.1-6 as previous. This is probably the last bash > release for cygwin 1.5; my next release will be bash 4.0 for cygwin 1.7. > > NEWS: > ===== > This is a minor patch release, which incorporates 1 official upstream > patch (actually, the patch is picked up by linking against > readline-5.2.14-12). It also enables the tsaware peflag on the shell, to > make it easier to complete postinstall scripts on Windows Server 2008. Just a minor note. Bash runs fine without the TS-aware flag on Windows Server 2008. Only servers which actually have the "Terminal Service" installed get this problem. I added a FAQ entry related to this problem to the new FAQ for Cygwin 1.7: http://cygwin.com/1.7/faq/faq.setup.html#faq.setup.setup-fails-on-ts Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple