public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Dawid Węgliński" <cla@gentoo.org>
Subject: Re: [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells)
Date: Sun, 22 Feb 2009 19:00:44 -0500	[thread overview]
Message-ID: <200902221900.46192.vapier@gentoo.org> (raw)
In-Reply-To: <200902230003.24056.cla@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-02-23  0:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 23:27 [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells) Mike Frysinger
2009-02-21 23:38 ` [gentoo-dev] " Ryan Hill
2009-02-21 23:55   ` Mike Frysinger
2009-02-22  0:00     ` Mart Raudsepp
2009-02-22  0:29       ` Mike Frysinger
2009-02-22  0:38         ` Mart Raudsepp
2009-02-22  0:44           ` Mike Frysinger
2009-02-22  0:54             ` Mart Raudsepp
2009-02-22  1:28               ` Mike Frysinger
2009-02-22  7:40                 ` Nirbheek Chauhan
2009-02-24 15:52             ` Daniel Gryniewicz
2009-02-24 15:56               ` Mike Frysinger
2009-02-22  1:02     ` Ryan Hill
2009-02-22 22:30 ` [gentoo-dev] " Dawid Węgliński
2009-02-22 22:39   ` Mike Frysinger
2009-02-22 23:03     ` Dawid Węgliński
2009-02-23  0:00       ` Mike Frysinger [this message]
2009-02-24  4:16       ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200902221900.46192.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=cla@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox