public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <Cedric_Hombourger@mentor.com>, <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/1] avoid user prompts when mk-build-deps is called
Date: Mon, 29 Jan 2018 16:59:54 +0100	[thread overview]
Message-ID: <20180129165954.404a1ab8@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <4e857783-a4ae-7649-523c-ae277fef6bab@ilbers.de>

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
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(-)
> >   
> 


  reply	other threads:[~2018-01-29 15:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 20:36 Cedric_Hombourger
2018-01-25 20:36 ` [PATCH 1/1] build.sh: eliminate user prompts from mk-build-deps Cedric_Hombourger
2018-01-26  7:42   ` Jan Kiszka
2018-01-26  7:47     ` Hombourger, Cedric
2018-01-26  7:48       ` Jan Kiszka
2018-01-29 10:25   ` Henning Schild
2018-01-29 16:31     ` [PATCH v2] build.sh: eliminate potential prompts from mk-build-deps/apt-get Cedric_Hombourger
2018-01-29 18:17       ` Henning Schild
2018-01-30 20:51         ` Henning Schild
2018-01-29 13:49 ` [PATCH 0/1] avoid user prompts when mk-build-deps is called Alexander Smirnov
2018-01-29 15:59   ` Henning Schild [this message]
2018-01-29 16:14     ` Alexander Smirnov
2018-02-03  9:49       ` chombourger
2018-02-03 17:37         ` Alexander Smirnov
2018-02-04  8:08           ` chombourger

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=20180129165954.404a1ab8@mmd1pvb1c.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=Cedric_Hombourger@mentor.com \
    --cc=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /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