Hello Kir, or anyone else affected, Accepted bash into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bash/5.0-6ubuntu1.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: bash (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1878517 Title: please apply bash 5.0 patch 17 Status in bash package in Ubuntu: Fix Released Status in bash source package in Focal: Fix Committed Bug description: This section is for Focal SRU purpose [Impact] From https://ftp.gnu.org/gnu/bash There were cases where bash 5.0 patch 16 reaped process substitution file descriptors (or FIFOs) and processes to early. This is a better fix for the problem that bash50-016 attempted to solve. [Test Case] This simple bash script pass when bash with patch 017 is installed Recommend to run it before and after installing the update to notice the difference ``` #!/usr/bin/bash ouch() { cat < <(echo bar) cat "$1" } ouch2() { { cat; } < <(echo bar) cat "$1" } ouch <(echo "foo") ouch2 <(echo "foo") ``` Expected output with the patch installed: foo bar foo bar [Regression Potential] This is an upstream patch level update with no additional modification. The regression potential should be fairly low. Also the patch is intended to only fix this problem. Possible regression would be unforeseen additional process substitutions that upstream bash would share. End SRU ------ Original Bug Description: I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0 patch 16. I can't reproduce it in pure bash, but with bats from https://github.com/bats-core/bats-core/ it is very easy to repro: ``` # cat << EOF > ya.bats check() { echo "check $@" ls -l /proc/self/fd } @test "here file" { check -p <(echo "hey") false } EOF $ bats ya.bats ``` Normally the output should contain the line lr-x------ 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918] which is a result of a "here file" created by bash via <(echo "hey"). In my testing, about 50% of runs don't have /dev/fd/63 listed. I found out this is a manifest of a bug introduced in bash 5.0 patch 16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016) The bug is fixed in 5.0 patch 17 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017). Please update bash to patchlevel 17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
