Re: [PATCH 0/1] avoid user prompts when mk-build-deps is called

[Alexander Smirnov <asmirnov@ilbers.de>]

On 01/29/2018 06:59 PM, Henning Schild wrote:
> Am Mon, 29 Jan 2018 16:49:51 +0300
> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
> 
>> Hello Cedric,
>>
>> On 01/25/2018 11:36 PM, Cedric_Hombourger@mentor.com wrote:
>>> From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
>>>
>>> commit 498b128 caused build dependencies to be installed via
>>> mk-build-deps.
>>>> The tool may ask the user to confirm their installation but
>>>> would
>> fail when
>>
>> Do you know in which circumstances this could happen?
> 
> Basically whenever apt-get decides to become interactive and wants to

I do understand what this patch does. My question is exactly when 
"whenever" really happens. I've noticed such behavior several times for 
different Debian tools, but it would be nice eventually to understand 
this kind of magic.

BTW: for me it's not the point to block this patch.

Alex

> ask for confirmation. My patch removed an "apt-get ... -y" while the
> "-y" should have stayed.
> 
> Henning
> 
>> Alex
>>
>>> called from bitbake (no stdin). Override the default install
>>> command to add the -y switch (assume yes).
>>>
>>> Cedric Hombourger (1):
>>>     build.sh: eliminate potential prompts from mk-build-deps/apt-get
>>>
>>>    meta/recipes-devtools/buildchroot/files/build.sh | 5 ++++-
>>>    1 file changed, 4 insertions(+), 1 deletion(-)
>>>    
>>
>