[ANNOUNCEMENT] TEST: bash 5.2.15-2

The following packages have been uploaded to the Cygwin distribution: * bash-5.2.15-2 * bash-devel-5.2.15-2 v2: Make /usr/bin/sh.exe a hardlink to /usr/bin/bash.exe, as required. The v1 installer script accidentally created a symlink. This is a long overdue update of the bash shell. Given

[ANNOUNCEMENT] TEST: bash 5.2.15-1

[first announcement was a bit... incomplete...] The following packages have been uploaded to the Cygwin distribution: * bash-5.2.15-1 * bash-devel-5.2.15-1 This is a long overdue update of the bash shell. Given the big step in the version, this is a TEST release for now. Please give it a try.

[ANNOUNCEMENT] TEST: bash 5.2.15-1

The following packages have been uploaded to the Cygwin distribution: * bash-5.2.15-1 * bash-devel-5.2.15-1 This is a long overdue update of the bash shell. Given the big step in the version, this is a TEST release for now. Please give it a try. This release is based on the Fedora Linux 37

Re: [ANNOUNCEMENT] Updated: bash-4.4.12-3

On Sat, 28 Jan 2017 12:27:48, Steven Penny wrote: > Bash printf cannot handle any Unicode blocks starting with "Private Use Area" > (U+E000 - U+F8FF). Note I will be skipping the surrogate blocks[1] (U+D800 - > U+DFFF) for this post, as /bin/printf does not support them either[2]: A patch was

Re: [ANNOUNCEMENT] Updated: bash-4.4.12-3

On Fri, 27 Jan 2017 13:23:53, "Eric Blake (cygwin)" wrote: > A new release of bash, 4.4.12-3, has been uploaded and will soon reach a > mirror near you. Bash printf cannot handle any Unicode blocks starting with "Private Use Area" (U+E000 - U+F8FF). Note I will be skipping the surrogate blocks[1]

[ANNOUNCEMENT] Updated: bash-4.4.12-3

A new release of bash, 4.4.12-3, has been uploaded and will soon reach a mirror near you. This release replaces 4.4.11-2 as current, and works with either the current libreadline7-7.0.1-1 or experimental libreadline7-7.0.1-2. NEWS: = This build incorporates 6 new official upstream patches;

[ANNOUNCEMENT] Updated: bash-4.4.11-2

A new release of bash, 4.4.11-2, has been uploaded and will soon reach a mirror near you. This release replaces 4.4.5-1 as current, and works with either the current libreadline7-7.0.1-1 or experimental libreadline7-7.0.1-2. NEWS: = This build incorporates 6 new official upstream patches; no

[ANNOUNCEMENT] Updated: bash-4.3.48-8

A new release of bash, 4.3.48-8, has been uploaded and will soon reach a mirror near you. It leave 4.3.46-7 as the previous version. NEWS: = This is a minor build that incorporates two official upstream patches, while I work on the larger project of building bash 4.4 for Cygwin. This build

Re: [ANNOUNCEMENT] Updated: bash-4.3.46-6

Greetings, Eric Blake! > On 08/06/2016 04:25 PM, David Rothenberger wrote: >> On 8/6/2016 6:13 AM, Eric Blake (cygwin) wrote: >>> 7b. completion_strip_exe - using 'shopt -s completion_strip_exe' >>> makes completion strip .exe suffixes >> >> I get an error that completion_strip_exe is not a

[ANNOUNCEMENT] Updated: bash-4.3.46-7

A new release of bash, 4.3.46-7, has been uploaded and will soon reach a mirror near you. It replaces 4.3.46-6, and leaves 4.3.42-4 as the previous version. NEWS: = This is a minor build that fixes an accidental regression in 'shopt -s completion_strip_exe' [1]. Since this is the only

Re: [ANNOUNCEMENT] Updated: bash-4.3.46-6

On 08/06/2016 04:25 PM, David Rothenberger wrote: > On 8/6/2016 6:13 AM, Eric Blake (cygwin) wrote: >> 7b. completion_strip_exe - using 'shopt -s completion_strip_exe' >> makes completion strip .exe suffixes > > I get an error that completion_strip_exe is not a supported option with > this

Re: [ANNOUNCEMENT] Updated: bash-4.3.46-6

Sounds good! Thanks for the update (and your hard work on the Cygwin bash release)! On Wed, Aug 24, 2016 at 10:24 AM, Eric Blake wrote: > On 08/24/2016 10:02 AM, Nem W Schlecht wrote: >> Having heard no news on this, I'm unsure if this functionality is just >> going to be

Re: [ANNOUNCEMENT] Updated: bash-4.3.46-6

On 08/24/2016 10:02 AM, Nem W Schlecht wrote: > Having heard no news on this, I'm unsure if this functionality is just > going to be this way now or if the author went on an extended vacation > or what. It *is* still listed in the release notes: Extended vacation (or rather, I just moved across

Re: [ANNOUNCEMENT] Updated: bash-4.3.46-6

Having heard no news on this, I'm unsure if this functionality is just going to be this way now or if the author went on an extended vacation or what. It *is* still listed in the release notes: 7b. completion_strip_exe - using 'shopt -s completion_strip_exe' makes completion strip .exe

Re: [ANNOUNCEMENT] Updated: bash-4.3.46-6

I can confirm - I get this same error. I'm guessing the patch for this (which is cygwin specific) was accidentally skipped for this build. On Sat, Aug 6, 2016 at 4:25 PM, David Rothenberger wrote: > On 8/6/2016 6:13 AM, Eric Blake (cygwin) wrote: >> >> 7b. completion_strip_exe

Re: [ANNOUNCEMENT] Updated: bash-4.3.46-6

On 8/6/2016 6:13 AM, Eric Blake (cygwin) wrote: 7b. completion_strip_exe - using 'shopt -s completion_strip_exe' makes completion strip .exe suffixes I get an error that completion_strip_exe is not a supported option with this release. It was working fine in 4.3.42-4. -- David Rothenberger

[ANNOUNCEMENT] Updated: bash-4.3.46-6

A new release of bash, 4.3.46-6, has been uploaded and will soon reach a mirror near you. It replaces 4.3.43-5, and leaves 4.3.42-4 as the previous version. NEWS: = This is a minor build that incorporates a couple more upstream bug fixes that I missed in the previous build. Since 4.3.43-5

[ANNOUNCEMENT] Updated: bash-4.3.43-5

A new release of bash, 4.3.43-5, has been uploaded and will soon reach a mirror near you. It leaves 4.3.42-4 as the previous version. NEWS: = This is a minor build that incorporates an upstream bug fix, as well as disables some old cruft in upstream code that tries to use O_TEXT in the

Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2

On 09/28/2015 08:56 AM, Eric Blake wrote: > On 09/28/2015 08:30 AM, Mikhail Usenko wrote: > >> But catching that bug (in upstream?) hasn't changed anything >> at least on my installation: > > Okay, I can see the disappearing \r even on a binary mount, so it > appears to be unrelated to the fix

Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2

On Mon, 28 Sep 2015 08:56:14 -0600 Eric Blake <...> wrote: > > 'echo -n' and 'echo -e' are non-portable (even in bash; because I can > use 'shopt -s xpgecho' to get POSIX-mandated behavior). Use 'printf' > instead. > xpg_echo doesn't change 'echo -ne' behavior ('echo -e' force backslash-escape

Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2

On 09/28/2015 10:48 AM, Mikhail Usenko wrote: > On Mon, 28 Sep 2015 08:56:14 -0600 > Eric Blake <...> wrote: >> >> 'echo -n' and 'echo -e' are non-portable (even in bash; because I can >> use 'shopt -s xpgecho' to get POSIX-mandated behavior). Use 'printf' >> instead. >> > > xpg_echo doesn't

Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2

On Thu, 24 Sep 2015 15:10:25 -0600 Eric Blake <...> wrote: > On 06/04/2015 03:51 AM, Mikhail Usenko wrote: > > Eric Blake (cygwin) <...> wrote: > >> 4.3.39-2 > > > > Hello, Eric. > > It has the same issue as in the previous version: > > eating one \r from the odd numbered chains of the \r. > > >

Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2

On 09/28/2015 08:30 AM, Mikhail Usenko wrote: > But catching that bug (in upstream?) hasn't changed anything > at least on my installation: Okay, so it sounds like your issue is separate. > > ---%<--%<--- > #! /bin/bash > bash -version | head -n1 > echo > > sender() > { > echo -n

Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2

On 09/28/2015 09:04 AM, Tim Higgins wrote: > Team > When I run startx I get the following error. > higginst@HigginsT-LT-W7 ~ > $ startx > And this is related to bash, how? Please don't top-post or commandeer unrelated threads. If you have an unrelated question, start a new thread. > > >

Re: [ANNOUNCEMENT] Updated: bash-4.3.42-4

On 09/24/2015 03:08 PM, Eric Blake (cygwin) wrote: > A new release of bash, 4.3.42-4, has been uploaded and will soon reach a > mirror near you. It is currently marked experimental pending test > results from others that have reported problems on text mounts: >

[ANNOUNCEMENT] Updated: bash-4.3.42-4

A new release of bash, 4.3.42-4, has been uploaded and will soon reach a mirror near you. It is currently marked experimental pending test results from others that have reported problems on text mounts: https://cygwin.com/ml/cygwin/2015-03/msg00496.html

Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2

On 06/04/2015 03:51 AM, Mikhail Usenko wrote: > Eric Blake (cygwin) <...> wrote: >> 4.3.39-2 > > Hello, Eric. > It has the same issue as in the previous version: > eating one \r from the odd numbered chains of the \r. > Please try the (currently-experimental) 4.3.42-4, which should fix the

Re: [ANNOUNCEMENT] Updated: bash-4.3.42-3

On Fri, 11 Sep 2015 12:48:59 + Nellis, Kenneth <...> wrote: > FWIW, back in 2012 there was a discussion on this behavior of sed. > Apparently strong enough arguments were made to retain this behavior. > > http://sourceware.org/ml/cygwin/2012-02/msg00301.html > Hello, Ken. Thank you for the

Re: [ANNOUNCEMENT] Updated: bash-4.3.42-3

On Tue, 25 Aug 2015 14:19:54 -0600 Eric Blake (cygwin) <...> wrote: > A new release of bash, 4.3.42-3, has been uploaded and will soon reach a > mirror near you; leaving 4.3.39-2 as the previous version. > It is one more buggy release (cygwin-specific). ---8<---(cygwin-test.sh)---8<--- #!

RE: [ANNOUNCEMENT] Updated: bash-4.3.42-3

From: Mikhail Usenko > There is also the similar problem found accidentally just now with sed in > pipelines: > $ echo -ne "\r\n" | sed '' | od -A n -tx1 # should be: 0d 0a > 0a > $ echo -ne "\r\r\n" | sed '' | od -A n -tx1 # should be: 0d 0d 0a > 0d 0a FWIW, back in 2012 there was a

[ANNOUNCEMENT] Updated: bash-4.3.42-3

A new release of bash, 4.3.42-3, has been uploaded and will soon reach a mirror near you; leaving 4.3.39-2 as the previous version. NEWS: = This is a minor build that folds in several new upstream patches. I am aware of an issue reported with using bash on text mode mounts, but have not yet

Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2

Eric Blake (cygwin) ... wrote: 4.3.39-2 Hello, Eric. It has the same issue as in the previous version: eating one \r from the odd numbered chains of the \r. bash-4.3.39-2 - $ echo -ne \r\n | { read t; echo $t; } | od -tx1 000 0a 001 $ echo -ne \r\r\n | { read t; echo $t; } |

Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2

On 06/04/2015 03:51 AM, Mikhail Usenko wrote: Eric Blake (cygwin) ... wrote: 4.3.39-2 Hello, Eric. It has the same issue as in the previous version: eating one \r from the odd numbered chains of the \r. Yes, I know there are still \r issues, although I appreciate the test case as I'm not

[ANNOUNCEMENT] Updated: bash-4.3.39-2

A new release of bash, 4.3.39-2, has been uploaded and will soon reach a mirror near you; leaving 4.3.33-1 as the previous version. NEWS: = This is my second build of bash 4.3 for cygwin, incorporating several new upstream official patches and working around a change in make 4.1 VPATH

[ANNOUNCEMENT] Updated: bash-4.1.17-9

A new release of bash, 4.1.17-9, has been uploaded and will soon reach a mirror near you; leaving the previous version at 4.1.16-8. NEWS: = This is a minor rebuild which picks up an upstream patch to fix another parser bug (CVE-2014-6278). This bug was found as a result of studying the extent

[ANNOUNCEMENT] Updated: bash-4.1.16-8

A new release of bash, 4.1.16-8, has been uploaded and will soon reach a mirror near you; leaving the previous version at 4.1.14-7. NEWS: = This is a minor rebuild which picks up two upstream patches to fix some parser bugs (CVE-2014-7186, CVE-2014-7187, CVE-2014-6277). These bugs were found

Re: [ANNOUNCEMENT] Updated: bash-4.1.14-7

On 30/09/2014 4:22, Eric Blake (cygwin) wrote: A new release of bash, 4.1.14-7, has been uploaded and will soon reach a mirror near you; leaving the previous version at 4.1.13-6. I've checked for updates several time, but I don't find bash version 4.1.14-7. I get version 4.1.13-7 instead. I

RE: [ANNOUNCEMENT] Updated: bash-4.1.14-7

Alive sent the following at Tuesday, September 30, 2014 1:49 PM On 30/09/2014 4:22, Eric Blake (cygwin) wrote: A new release of bash, 4.1.14-7, has been uploaded and will soon reach a mirror near you; leaving the previous version at 4.1.13-6. I've checked for updates several time, but I don't

RE: [ANNOUNCEMENT] Updated: bash-4.1.13-6

Eric Blake (cygwin) sent the following at Saturday, September 27, 2014 2:14 AM I also turned on the (undocumented) 'bash --wordexp' mode (actually, that happened in 4.1.12-5, although I failed to mention it at the time), which allows the C library call wordexp() to now function. From a user

Re: [ANNOUNCEMENT] Updated: bash-4.1.13-6

On 2014-09-29 09:18, Buchbinder, Barry (NIH/NIAID) [E] wrote: Eric Blake (cygwin) sent the following at Saturday, September 27, 2014 2:14 AM I also turned on the (undocumented) 'bash --wordexp' mode (actually, that happened in 4.1.12-5, although I failed to mention it at the time), which allows

Re: [ANNOUNCEMENT] Updated: bash-4.1.13-6

Eric Blake (cygwin) writes: A new release of bash, 4.1.13-6, has been uploaded and will soon reach a mirror near you; leaving the previous version at 4.12-5. Just out of curiosity, why is this release version -6 instead of -1? Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb

Re: [ANNOUNCEMENT] Updated: bash-4.1.13-6

On 09/29/2014 10:14 AM, Achim Gratz wrote: Eric Blake (cygwin) writes: A new release of bash, 4.1.13-6, has been uploaded and will soon reach a mirror near you; leaving the previous version at 4.12-5. Just out of curiosity, why is this release version -6 instead of -1? Because of how

Re: [ANNOUNCEMENT] Updated: bash-4.1.13-6

Eric Blake writes: On 09/29/2014 10:14 AM, Achim Gratz wrote: Eric Blake (cygwin) writes: A new release of bash, 4.1.13-6, has been uploaded and will soon reach a mirror near you; leaving the previous version at 4.12-5. Just out of curiosity, why is this release version -6 instead of -1?

RE: [ANNOUNCEMENT] Updated: bash-4.1.13-6

Eric Blake (cygwin) sent the following at Saturday, September 27, 2014 2:14 AM Using the new version of bash, two scripts that I use have both started giving me the following error message(s). /usr/bin/bash: error importing function definition for `BASH_FUNC_make-log' /usr/bin/bash: error

Re: [ANNOUNCEMENT] Updated: bash-4.1.13-6

On 09/29/2014 03:23 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote: Eric Blake (cygwin) sent the following at Saturday, September 27, 2014 2:14 AM Using the new version of bash, two scripts that I use have both started giving me the following error message(s). /usr/bin/bash: error importing

[ANNOUNCEMENT] Updated: bash-4.1.14-7

A new release of bash, 4.1.14-7, has been uploaded and will soon reach a mirror near you; leaving the previous version at 4.1.13-6. NEWS: = This is a minor rebuild which picks up an upstream patch to fix CVE-2014-7169 and all other ShellShock attacks (4.1.13-6 was also safe, but used a

RE: [ANNOUNCEMENT] Updated: bash-4.1.13-6

Eric Blake sent the following at Monday, September 29, 2014 5:29 PM On 09/29/2014 03:23 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote: Eric Blake (cygwin) sent the following at Saturday, September 27, 2014 2:14 AM Using the new version of bash, two scripts that I use have both started giving

Re: [ANNOUNCEMENT] Updated: bash-4.1.13-6

On 09/29/2014 04:52 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote: These functions contain '-' in their name; that's a limitation of the downstream forked patch I applied early to get 4.1.13-6 out the door. Upstream solved it in a nicer manner, so you can once again have functions with '-' in

[ANNOUNCEMENT] Updated: bash-4.1.13-6

A new release of bash, 4.1.13-6, has been uploaded and will soon reach a mirror near you; leaving the previous version at 4.12-5. NEWS: = This is a minor rebuild which picks up an upstream patch to fix CVE-2014-7169, as well as a Red Hat patch to ensure that CVE-2014-7186 and CVE-2014-7187

Re: [ANNOUNCEMENT] Updated: bash-4.1.12-5

When are you releasing 4.1.12-6 -- 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

Re: [ANNOUNCEMENT] Updated: bash-4.1.12-5

On 09/26/2014 07:36 AM, Mohammad Yaqoob wrote: When are you releasing 4.1.12-6 Today. It may be numbered 4.1.13-6, depending on what upstream does in the meantime (Chet has already prepared patch 13 [fixing a parser state leak], but not yet published it), but even without waiting for

Re: [ANNOUNCEMENT] Updated: bash-4.1.12-5

On 2014-09-24 20:35, Eric Blake (cygwin) wrote: A new release of bash, 4.1.12-5, has been uploaded and will soon reach a mirror near you; leaving the previous version of 4.1.10-4 on 32-bit, and 4.1.11-2 on 64-bit. NEWS: = This is a minor rebuild which picks up an upstream patch to fix

Re: [ANNOUNCEMENT] Updated: bash-4.1.12-5

On 09/26/2014 02:56 PM, Peter Rosin wrote: On 2014-09-24 20:35, Eric Blake (cygwin) wrote: A new release of bash, 4.1.12-5, has been uploaded and will soon reach a mirror near you; leaving the previous version of 4.1.10-4 on 32-bit, and 4.1.11-2 on 64-bit. I haven't checked out 4.1.12-5

[ANNOUNCEMENT] Updated: bash-4.1.12-5

A new release of bash, 4.1.12-5, has been uploaded and will soon reach a mirror near you; leaving the previous version of 4.1.10-4 on 32-bit, and 4.1.11-2 on 64-bit. NEWS: = This is a minor rebuild which picks up an upstream patch to fix CVE-2014-6271. Left unpatched, a vulnerable version of

[ANNOUNCEMENT] Updated: bash-4.1.10-4

A new release of bash, 4.1.10-4, has been uploaded and will soon reach a mirror near you; replacing 4.1.9-3 and leaving bash 3.2.51-24 as previous. NEWS: = This is a minor rebuild which picks up an upstream patch to fix memory corruption when using \W in $PS1. [Meanwhile, bash 4.2 has been

[ANNOUNCEMENT] Updated: bash-completion-1.3-1

A new release of bash-completion, 1.3-1, will soon be on a mirror near you, leaving 1.2-1 as previous. NEWS: = This is a new upstream release. Changes since the prior release are attached. For more details, see /usr/share/doc/bash-completion/. Note that installing this package

[ANNOUNCEMENT] Updated: bash-4.1.9-3

A new release of bash, 4.1.9-3, has been uploaded and will soon reach a mirror near you; replacing 4.1.9-2 and leaving bash 3.2.51-24 as previous. NEWS: = This is a minor rebuild which avoids a miscompilation that was causing bash to crash on some machines during ssh-host-config. There are a

[ANNOUNCEMENT] Updated: bash-3.2.51-24

A new release of bash, 3.2.51-24, has been uploaded and will soon reach a mirror near you. This replaces 3.2.49-23 as current. NEWS: = This is a minor update that pulls in a couple of upstream patches and fixes a bug in the postinstall script. There are a few things you should be aware of

[ANNOUNCEMENT] Updated: bash-completion-1.2-1

A new release of bash-completion, 1.2-1, is now available for download, leaving 1.1-2 as previous. NEWS: = This is a new upstream release. Changes since the prior release are attached. For more details, including how to enable bash-completion for your interactive shells after installing

[ANNOUNCEMENT] Updated: bash-completion-1.1-1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash-completion, 1.1-1, is now available for cygwin 1.5; a corresponding release for those testing cygwin 1.7 will be available shortly. NEWS: = This is a new upstream release. Changes since the prior release are attached. For

Re: [ANNOUNCEMENT] Updated: bash-3.2.49-22

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

[ANNOUNCEMENT] Updated: bash-3.2.49-22

-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

[ANNOUNCEMENT] Updated: bash-3.2.48-21

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.48-21, has been uploaded, replacing 3.2.39-20 as current, and leaving 3.1-6 as previous. NEWS: = This is a minor patch release, which incorporates 9 official upstream patches, and works around an issue identified when

[ANNOUNCEMENT] Updated: bash-3.2.39-20

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.39-29, has been uploaded, replacing 3.2.39-19 as current, and leaving 3.1-6 as previous. NEWS: = This is a minor patch release, which blindly installs /bin/sh rather than using a postinstall script prone to failure.

Re: [ANNOUNCEMENT] Updated: bash-3.2.39-20

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 8/11/2008 6:37 AM: | A new release of bash, 3.2.39-29, has been uploaded, replacing 3.2.39-19 | as current, and leaving 3.1-6 as previous. Oops - I had a typo. If it isn't obvious, the new release is 3.2.39-20, not -29.

RE: [ANNOUNCEMENT] Updated: bash-3.2.39-19

From: Eric Blake [] 4. This version of bash has a cygwin-specific shell option, named igncr to force bash to ignore \r, independently of cygwin's mount style. As of bash-3.2.3-5, it controls regular scripts, command substitution, and sourced files. I hope to convince the upstream bash

[ANNOUNCEMENT] Updated: bash-3.2.39-19

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.39-19, has been uploaded, replacing 3.2.33-18 as current, and leaving 3.1-6 as previous. NEWS: = This is a minor patch release, folding in six upstream patches. It fixes a memory bug with certain 'pwd' calls, two bugs

[ANNOUNCEMENT] Updated: bash-3.2.33-18

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.33-18, has been uploaded, replacing 3.2.25-17 as current, and leaving 3.1-6 as previous. NEWS: = This is a minor patch release. Bash now tries harder to create a temporary file for here-docs even when $TMPDIR is

Re: [ANNOUNCEMENT] Updated: bash-3.2.25-17

On Fri, 19 Oct 2007, Corinna Vinschen wrote: On Oct 19 09:46, Igor Peshansky wrote: On Fri, 19 Oct 2007, Eric Blake wrote: According to Igor Peshansky on 10/19/2007 7:29 AM: I could, but the issue is more basic than where the script lives. Right now Cygwin populates the /dev

Re: [ANNOUNCEMENT] Updated: bash-3.2.25-17

On Oct 19 09:46, Igor Peshansky wrote: On Fri, 19 Oct 2007, Eric Blake wrote: According to Igor Peshansky on 10/19/2007 7:29 AM: I could, but the issue is more basic than where the script lives. Right now Cygwin populates the /dev directory as a virtual directory within the DLL. The

Re: [ANNOUNCEMENT] Updated: bash-3.2.25-17

On Fri, 19 Oct 2007, Eric Blake wrote: According to Igor Peshansky on 10/19/2007 7:29 AM: Why not create a stand-alone package in the base category which consists of just the postinstall script? I could, but the issue is more basic than where the script lives. Right now Cygwin

Re: [ANNOUNCEMENT] Updated: bash-3.2.25-17

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Igor Peshansky on 10/19/2007 7:29 AM: Why not create a stand-alone package in the base category which consists of just the postinstall script? I could, but the issue is more basic than where the script lives. Right now Cygwin

Re: [ANNOUNCEMENT] Updated: bash-3.2.25-17

On Fri, 19 Oct 2007, Corinna Vinschen wrote: On Oct 18 13:29, Igor Peshansky wrote: On Wed, 17 Oct 2007, Eric Blake wrote: [snip] Based on user response, I may be convinced to fold in the rest of Igor's create_devices.sh [see

Re: [ANNOUNCEMENT] Updated: bash-3.2.25-17

On Oct 18 13:29, Igor Peshansky wrote: On Wed, 17 Oct 2007, Eric Blake wrote: [snip] Based on user response, I may be convinced to fold in the rest of Igor's create_devices.sh [see http://cygwin.com/cygwin-ug-net/using-specialnames.html] into the bash postinstall, as it admittedly

Re: [ANNOUNCEMENT] Updated: bash-3.2.25-17

On Wed, 17 Oct 2007, Eric Blake wrote: [snip] Based on user response, I may be convinced to fold in the rest of Igor's create_devices.sh [see http://cygwin.com/cygwin-ug-net/using-specialnames.html] into the bash postinstall, as it admittedly looks a bit weird when 'ls /dev' shows

[ANNOUNCEMENT] Updated: bash-3.2.25-17

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.25-17, has been uploaded, replacing 3.2.25-16 as current, and leaving 3.1-6 as previous. NEWS: = This is a minor patch release. It fixes a bug in (times file) | cat, introduced in -11. It incorporates a patch that

[ANNOUNCEMENT] Updated: bash-3.2.25-16

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.25-16, has been uploaded, replacing 3.2.17-15 as current. NEWS: = This is a minor patch release. It folds in eight new upstream patches, three of which are also incorporated into readline, and the remaining which fix:

[ANNOUNCEMENT] Updated: bash-3.2.17-15

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.17-15, has been uploaded, replacing 3.2.15-14 as current. NEWS: = This is a minor patch release. It folds in two new upstream patches (both of which only affect readline, so this binary should be identical to the

[ANNOUNCEMENT] Updated: bash-3.2.15-14

A new release of bash, 3.2.15-14, has been uploaded, replacing 3.2.15-13 as current. NEWS: = This is a minor patch release. It works around a latent upstream bug that was exposed by release 11, where certain builtins leaked output when invoked inside command substitution, such as: echo

[ANNOUNCEMENT] Updated: bash-3.2.15-13

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.15-13, has been uploaded, replacing 3.2.10-12 as current. NEWS: = This is a minor patch release. It incorporates five new official upstream patches (Solaris fix, AIX fix, readline fix, properly handling null IFS, and

[ANNOUNCEMENT] Updated: bash-3.2.10-12

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.10-12, has been uploaded, replacing 3.2.9-11 as current. NEWS: = This is a minor patch release. It incorporates official upstream patch 10 (fixing =~ quoting with some regex implementations). It fixes the postinstall

[ANNOUNCEMENT] Updated: bash-3.2.9-11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.9-11, has been uploaded, replacing 3.2.9-10 as current. NEWS: = This is a minor patch release. It swaps over to the cygport build framework (although building it requires several patches on top of cygport 0.2.8). It

[ANNOUNCEMENT] Updated: bash-3.2.9-10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.9-10, has been uploaded, replacing 3.2.9-9 as current. NEWS: = This is a minor patch release. It undoes the asprintf workaround added in 3.2.5-7, now that cygwin 1.5.23 has been released which overcomes the need for

Re: [ANNOUNCEMENT] Updated: bash-3.2.9-9

Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.9-9, has been uploaded, replacing 3.2.5-8 as current. [snip] 6 fixes the readline prompt display bug Which bug is that? [snip] - Eric -- Unsubscribe info:

Re: [ANNOUNCEMENT] Updated: bash-3.2.9-9

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Lilja on 12/16/2006 6:06 AM: [snip] 6 fixes the readline prompt display bug Which bug is that? http://lists.gnu.org/archive/html/bug-bash/2006-12/msg00027.html - -- Life is short - so eat dessert first! Eric Blake

[ANNOUNCEMENT] Updated: bash-3.2.9-9

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.9-9, has been uploaded, replacing 3.2.5-8 as current. NEWS: = This is a minor patch release. It incorporates several official upstream patches (some of which I had already been experimenting with in earlier releases):

[ANNOUNCEMENT] Updated: bash-3.2.5-8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.5-8, has been uploaded, replacing 3.2.3-7 as current. NEWS: = This is a minor patch release. It adds a workaround for the bug in bash's replacement asprintf (which in turn works around a bug in cygwin's asprintf in any

[ANNOUNCEMENT] Updated: bash-3.2.5-7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.5-7, has been uploaded, replacing 3.2.3-6 as current. NEWS: = This is a minor patch release. It adds a workaround for the bug in asprintf in cygwin 1.5.22 which could cause the printf builtin to core dump on long

Re: [ANNOUNCEMENT] Updated: bash-3.2.3-5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to SungHyun Nam on 11/14/2006 10:54 PM: Hello, No need to double post. I cannot use /dev/stdout with a bash-3.2.3-5. For example, 'echo hi /dev/stdout' failed. It works fine after I reverted to bash-3.1-6. Hmm, it does indeed seem

[ANNOUNCEMENT] Updated: bash-3.2.5-6

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.5-6, has been uploaded, replacing 3.2.3-5 as current. NEWS: = This is a minor patch. It folds in two new upstream patches, fixing global pattern replacement and a floating point printing bug. It also contains a

Re: [ANNOUNCEMENT] Updated: bash-3.2.3-5

I saw a couple of posts mentioning a problem with /bin/sh not being updated and replaced with a copy of /bin/bash. I had the same problem here yesterday/today, when I discovered that none of my #!/bin/sh scripts was working. In fact, they did nothing! I tried re-installing bash-3.2.3-5, I tried

Re: [ANNOUNCEMENT] Updated: bash-3.2.3-5

Hello, I cannot use /dev/stdout with a bash-3.2.3-5. For example, 'echo hi /dev/stdout' failed. It works fine after I reverted to bash-3.1-6. Thanks. namsh -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html

Re: [ANNOUNCEMENT] Updated: bash-3.2.3-5

Eric Blake ebb9 at byu.net writes: Evil. /bin/sh is supposed to be at the same version of bash, if you installed things correctly. It sounds like your postinstall scripts did not run correctly (perhaps you had bash or sh open when you ran setup.exe?). What are the timestamps on

[ANNOUNCEMENT] Updated: bash-3.2.3-5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash, 3.2.3-5, has been promoted to current. This leaves 3.1-6 as the previous version (and not 3.1-9, since only 3.1-6 will work if you downgrade cygwin). NEWS: = This is a new upstream release, including several official

Re: [ANNOUNCEMENT] Updated: bash-3.2.3-5

Eric Blake ebb9 at byu.net writes: A new release of bash, 3.2.3-5, has been promoted to current. This leaves 3.1-6 as the previous version (and not 3.1-9, since only 3.1-6 will work if you downgrade cygwin). complete release message deleted. I've adopted 3.2.3-5 (after previously

Re: [ANNOUNCEMENT] Updated: bash-3.2.3-5

Bret Weinraub bretweinraub at yahoo.com writes: Details: bash --version 3.2.3(5)-release sh --version 3.1.17(9)-release Evil. /bin/sh is supposed to be at the same version of bash, if you installed things correctly. It sounds like your postinstall scripts did not run correctly

Re: [ANNOUNCEMENT] Updated: bash-3.2.3-5

Eric Blake ebb9 at byu.net writes: Bret Weinraub bretweinraub at yahoo.com writes: Details: bash --version 3.2.3(5)-release sh --version 3.1.17(9)-release Evil. /bin/sh is supposed to be at the same version of bash, if you installed things correctly. It

[ANNOUNCEMENT] Updated: bash-completion-20060301-2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of bash-completion, 20060301-2, is now available, replacing 20060301-1 as the current version. NEWS: = This is a minor patch release; it swaps over to a cygport build, and adds completion support for cygport contributed by Reini

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

Or even experiment with the SHELLOPTS environment variable. If you set it in windows, even the first run of bash will obey igncr; or, from within bash, if you do 'export SHELLOPTS' to convert it from a shell variable to an environment variable, then further bash invocations will inherit the

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

Wilks, Dan Dan_Wilks at intuit.com writes: Eric, as one of the complainers :) thanks. I just wanted to check in and say that our case of executing a cr/lf script via a DOS path on a text mount is working as well as it used to. I echo that sentiment. Now I don't feel so left behind.

  1   2   >