Chet:
Thank you for the pointers. I tried to read through the "repo" code all
morning. I don't really know Python, but what I can see is that:
1) It appears to not invoke any specific shell. It seems to fork a new
process, which would duplicate whatever shell it started with.
2) It has a "D
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. P
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, p
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='l$
uname output: Linux 20180329x99-a 4.13.0-38-generic #43~16.04.1-Ubuntu
SMP Wed $
Machine Type: x86_64-
On 7/2/18 6:25 PM, Eduardo A. Bustamante López wrote:
> On Mon, Jul 02, 2018 at 04:58:06PM -0700, toww wrote:
> [...]
>> 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
>> invok
On Mon, Jul 02, 2018 at 04:58:06PM -0700, toww wrote:
[...]
> 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 multip
