Created attachment 341178 [details] emerge --info If bash-4.1_p11 is used, many ebuilds fail with a this message: /var/tmp/portage/dev-java/java-config-2.1.12-r1/temp/environment: line 2632: MULTIBUILD_VARIANTS: bad array subscript * ERROR: dev-java/java-config-2.1.12-r1 failed (install phase): * MULTIBUILD_VARIANTS need to be set * * Call stack: * ebuild.sh, line 93: Called src_install * environment, line 3479: Called distutils-r1_src_install * environment, line 942: Called _distutils-r1_run_common_phase 'python_install_all' * environment, line 241: Called multibuild_for_best_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_install_all' * environment, line 2633: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_install_all' * environment, line 2638: Called die * The specific snippet of code: * [[ -n ${MULTIBUILD_VARIANTS} ]] || die "MULTIBUILD_VARIANTS need to be set"; java-config is just one quick example. Upgrading to bash-4.2_p37 allowed the emerge to finish, and was the only change I made between a failed emerge and one that succeeded. This started happening sometime after 2013.01.21, which was the last time java-config built under the older bash version for me. I have been using the older bash version due to changes in 4.2 that broke or altered tab completion related to variables. (seem to be somewhat fixed now, though the behaviour is still different.)
Just to note that bash-4.0_p38 also fails.
app-shells/bash: 4.1_p11::squish-local-overlay An older version installed from an overlay. Please tell there's a very good reason not to upgrade. :)
I think we are technically supposed to support 3.2 or greater.
Oh, so it's about ${foo} vs ${foo[0]}? Easy enough, didn't know this ain't supported.
bash-4.1 compatibility should be fixed now. Please let me know if there are any more issues.
First, it is working again on 4.1_p11. About the overlay, sorry, that is an exact copy from 4.1_p11::gentoo I made the last time my older version appeared endangered. I tested on two different systems and didnt notice the local overlay on the one I pasted from. Thanks for fixing; as I mentioned there were some signifigant behavioural differences with 4.2 that I wanted to avoid. (though seemingly mitigated in the later releases.)
