Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: Chet Ramey Newsgroups: gnu.bash.bug Subject: Re: bash 4.3.48(1) and repo: processing of commands halts at first semicolon Date: Tue, 3 Jul 2018 10:59:32 -0600 Organization: ITS, Case Western Reserve University Lines: 27 Approved: bug-bash@gnu.org Message-ID: References: <7474bb6d-af63-4a00-7a2b-97a1eb98c86b@case.edu> Reply-To: chet.ramey@case.edu NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1530637184 2300 208.118.235.17 (3 Jul 2018 16:59:44 GMT) X-Complaints-To: action@cs.stanford.edu Cc: chet.ramey@case.edu To: toww , bug-bash@gnu.org, bash@packages.debian.org Envelope-to: bug-bash@gnu.org X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:cc:subject:to:references:from :organization:message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=5sDxZHTFFNq4dbJdFrk0OXR3PlTQzQ2vZJWEB18s0LM=; b=ANxjiizSPoVLKU9HrvEocqe6MpDHRIKgfKd0SpcMe2EFE5xvcYAgtF4KvmZqyL3qQO zJxJgIxIiXtNAF+ALV47qYV7YV/m6qaId8OLdfDbWF9gecgy21NnyHYGAyv+bnbjVzwT 13qWCf9km8WIGujKe56kZqo2imabuOqeMtjl7AdQTEOY4oExupd3aUp4yKPU4AUON0bN 6gcX5MQwK8w3Cw8ULUNhTA1xcrskLJS/1miuurET/FWZjMt082woFNVm6OjLSO54rC1X hdM9oQmduQzGHahg6M5ipMcHkQt90pH/Xz+T+FQ96mu0D6nF8A9akh0jWRlFA89la6hu +omw== X-Gm-Message-State: APt69E2q6JqmSitKuzMMkJtY9Oug95WTr+TUY9KLInHNWhyIEQIj2ERv hH/uJCqRS9zvhtuj86r/P1UtQZ9+F70+0PxvQfqRbeZcNfFLHEBiy0JeSR5vNlzjODKYKLGEiuo zTGvcH1S5Dw8= X-Received: by 2002:a24:8201:: with SMTP id t1-v6mr10303144itd.51.1530637174360; Tue, 03 Jul 2018 09:59:34 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdhspdfv5mYpILoprVzYVnG4/EJpWT7mITozdE7kXtWy7PX3tbmwZXqNPM62gpPxfaKg7rc5A== X-Received: by 2002:a24:8201:: with SMTP id t1-v6mr10303132itd.51.1530637174137; Tue, 03 Jul 2018 09:59:34 -0700 (PDT) User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 In-Reply-To: <7474bb6d-af63-4a00-7a2b-97a1eb98c86b@case.edu> Content-Language: en-US X-Junkmail-Status: score=9/90, host=mpv3-2015.case.edu X-Junkmail-PrAS-Raw: score=9/90, refid=2.7.2:2018.7.3.154517:17:9.975, ip=, rules=__YOUTUBE_RCVD, __HAS_REPLYTO, __HAS_CC_HDR, __SUBJ_REPLY, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __TO_MALFORMED_2, __TO_NAME, __REFERENCES, __HAS_FROM, FROM_EDU_TLD, __HAS_MSGID, __SANE_MSGID, DATE_TZ_NA, __USER_AGENT, __MOZILLA_USER_AGENT, __MIME_VERSION, __IN_REP_TO, __CT, __CT_TEXT_PLAIN, __CTE, __REPLYTO_SAMEAS_FROM_ADDY, __REPLYTO_SAMEAS_FROM_ACC, __FROM_DOMAIN_IN_ANY_CC1, __FROM_DOMAIN_IN_ANY_CC2, __TO_IN_SUBJECT2, __REPLYTO_SAMEAS_FROM_DOMAIN, __ANY_URI, __URI_WITH_PATH, __URI_NO_WWW, __CP_URI_IN_BODY, __INVOICE_MULTILINGUAL, __SUBJ_ALPHA_NEGATE, __URI_IN_BODY, __URI_NOT_IMG, __FORWARDED_MSG, __NO_HTML_TAG_RAW, BODY_SIZE_1100_1199, BODYTEXTP_SIZE_3000_LESS, __MIME_TEXT_P1, __MIME_TEXT_ONLY, __URI_NS, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, IN_REP_TO, MSG_THREAD, __FROM_DOMAIN_IN_RCPT, MULTIPLE_REAL_RCPTS, [TRUNCATED], so=2010-03-03 19:42:08, dmn=2016-08-03-0138 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] [fuzzy] X-Received-From: 129.22.103.194 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:14295 On 7/3/18 10:34 AM, Chet Ramey wrote: > On 7/2/18 5:58 PM, toww wrote: > >> Bash Version: 4.3 >> Patch Level: 48 >> Release Status: release >> >> Description: >> There seems to be a new incompatibility or incorrect string parsing in how >> the Google "repo" utility interacts with the bash shell. Previously I could >> invoke the "repo" command, passing to it a string to execute multiple >> commands separated by semicolons (';' characters), and all commands would >> execute. Now with the latest bash 4.3.38, only the first command executes, >> and processing stops at the semicolon. > > It would help to see the exact set of commands that repo uses to invoke the > shell, the options it passes to shell invocation. It would help more to > have a reproducer that doesn't involve `repo'. You could also check whether repo is invoking /bin/sh instead of /bin/bash, and, if so, whether bash is installed as /bin/sh. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/