Re: [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells)
On Sunday 22 February 2009 18:03:23 Dawid Węgliński wrote: > On Sunday 22 of February 2009 23:39:11 Mike Frysinger wrote: > > On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote: > > > On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote: > > > > looks like bash-4.0 has broken semicolon escaping in subshells. this > > > > comes up when using find's -exec like we do in a few places in > > > > eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po \;); > > > > shift you can work around the issue in a couple of ways: > > > > - quote the semicolon: > > > > ';') > > > > - use backticks > > > > `find \;` > > > > > > > > i'll tweak the eclasses to use quoting for now > > > > > > FYI. Not only find's semicolons are affected. It also happens in case > > > ;; construction. > > > > embedded case statements in $(...) subshells have always been broken. > > bash-4.0 is supposed to fix that. if you have some code that is broken, > > please post it so i can push it upstream. > > It wasn't me who experienced that, but a user: > > 13:50 < diabel-> <<< dir /usr/share/doc/wxGTK-2.8.9.1-r3 > 13:50 < diabel-> > /var/tmp/binpkgs/x11-libs/wxGTK-2.8.9.1-r3/temp/environment: line 2989: > błąd składni przy nieoczekiwanym znaczniku `;;' > 13:50 < diabel-> > /var/tmp/binpkgs/x11-libs/wxGTK-2.8.9.1-r3/temp/environment: line 2989: ` > ;;' * * ERROR: x11-libs/wxGTK-2.8.9.1-r3 failed. > > All it states is syntax error near double semicolons. this is probably the same issue i pointed out originally. re-emerge bash and it should work. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells)
On Sunday 22 February 2009 18:03:23 Dawid Węgliński wrote: > On Sunday 22 of February 2009 23:39:11 Mike Frysinger wrote: > > On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote: > > > On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote: > > > > looks like bash-4.0 has broken semicolon escaping in subshells. this > > > > comes up when using find's -exec like we do in a few places in > > > > eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po \;); > > > > shift you can work around the issue in a couple of ways: > > > > - quote the semicolon: > > > > ';') > > > > - use backticks > > > > `find \;` > > > > > > > > i'll tweak the eclasses to use quoting for now > > > > > > FYI. Not only find's semicolons are affected. It also happens in case > > > ;; construction. > > > > embedded case statements in $(...) subshells have always been broken. > > bash-4.0 is supposed to fix that. if you have some code that is broken, > > please post it so i can push it upstream. > > It wasn't me who experienced that, but a user: > > 13:50 < diabel-> <<< dir /usr/share/doc/wxGTK-2.8.9.1-r3 > 13:50 < diabel-> > /var/tmp/binpkgs/x11-libs/wxGTK-2.8.9.1-r3/temp/environment: line 2989: > błąd składni przy nieoczekiwanym znaczniku `;;' > 13:50 < diabel-> > /var/tmp/binpkgs/x11-libs/wxGTK-2.8.9.1-r3/temp/environment: line 2989: ` > ;;' * * ERROR: x11-libs/wxGTK-2.8.9.1-r3 failed. > > All it states is syntax error near double semicolons. unfortunately, that info isnt useful in any way. it looks like it's a binpkg though, so getting the files again should be possible. please have the user find that file from the binpkg and report a bug. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells)
On Sunday 22 of February 2009 23:39:11 Mike Frysinger wrote: > On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote: > > On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote: > > > looks like bash-4.0 has broken semicolon escaping in subshells. this > > > comes up when using find's -exec like we do in a few places in > > > eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po \;); shift > > > you can work around the issue in a couple of ways: > > > - quote the semicolon: > > > ';') > > > - use backticks > > > `find \;` > > > > > > i'll tweak the eclasses to use quoting for now > > > > FYI. Not only find's semicolons are affected. It also happens in case ;; > > construction. > > embedded case statements in $(...) subshells have always been broken. > bash-4.0 is supposed to fix that. if you have some code that is broken, > please post it so i can push it upstream. > -mike It wasn't me who experienced that, but a user: 13:50 < diabel-> <<< dir /usr/share/doc/wxGTK-2.8.9.1-r3 13:50 < diabel-> /var/tmp/binpkgs/x11-libs/wxGTK-2.8.9.1-r3/temp/environment: line 2989: błąd składni przy nieoczekiwanym znaczniku `;;' 13:50 < diabel-> /var/tmp/binpkgs/x11-libs/wxGTK-2.8.9.1-r3/temp/environment: line 2989: `;;' * * ERROR: x11-libs/wxGTK-2.8.9.1-r3 failed. All it states is syntax error near double semicolons.
Re: [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells)
On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote: > On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote: > > looks like bash-4.0 has broken semicolon escaping in subshells. this > > comes up when using find's -exec like we do in a few places in eclasses: > > ls=$(find "$1" -name '*.po' -exec basename {} .po \;); shift you can work > > around the issue in a couple of ways: > > - quote the semicolon: > > ';') > > - use backticks > > `find \;` > > > > i'll tweak the eclasses to use quoting for now > > FYI. Not only find's semicolons are affected. It also happens in case ;; > construction. embedded case statements in $(...) subshells have always been broken. bash-4.0 is supposed to fix that. if you have some code that is broken, please post it so i can push it upstream. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells)
On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote: > looks like bash-4.0 has broken semicolon escaping in subshells. this comes > up when using find's -exec like we do in a few places in eclasses: > ls=$(find "$1" -name '*.po' -exec basename {} .po \;); > shift you can work around the issue in a couple of ways: > - quote the semicolon: > ';') > - use backticks > `find \;` > > i'll tweak the eclasses to use quoting for now > -mike FYI. Not only find's semicolons are affected. It also happens in case ;; construction. -- Cheers, Dawid Węgliński
[gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells)
looks like bash-4.0 has broken semicolon escaping in subshells. this comes up when using find's -exec like we do in a few places in eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po \;); shift you can work around the issue in a couple of ways: - quote the semicolon: ';') - use backticks `find \;` i'll tweak the eclasses to use quoting for now -mike signature.asc Description: This is a digitally signed message part.