From: chombourger@gmail.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/1] avoid user prompts when mk-build-deps is called
Date: Sun, 4 Feb 2018 00:08:49 -0800 (PST) [thread overview]
Message-ID: <6f48f86e-ade5-46f5-a2f7-05a8eecfbbdf@googlegroups.com> (raw)
In-Reply-To: <1615cbef938.27ac.034a6b0541ed39b7fb4e17f4ac219eaa@ilbers.de>
[-- Attachment #1.1: Type: text/plain, Size: 4382 bytes --]
You're welcome and thank you!
(BTW: it does not look like you have pushed your updated "next" branch to
GitHub -- no rush though)
Cedric
On Saturday, February 3, 2018 at 6:37:47 PM UTC+1, Alexander Smirnov wrote:
>
> Hi,
>
> chomb...@gmail.com <javascript:> 3 февраля 2018 г. 12:49:41 написал:
>
> > Hi Alex,
> >
> > A simple test case to demonstrate the issue consists in adding
> libpci-dev
> > as a build dependency to example-hello
> > I have forked and modified hello for this purpose and modifed the recipe
> as
> > follows:
> >
> > diff --git a/meta-isar/recipes-app/example-hello/example-hello.bb
> > b/meta-isar/recipes-app/example-hello/example-hello.bb
> > index 602a11e..af87428 100644
> > --- a/meta-isar/recipes-app/example-hello/example-hello.bb
> > +++ b/meta-isar/recipes-app/example-hello/example-hello.bb
> > @@ -10,8 +10,8 @@ LIC_FILES_CHKSUM =
> > "file://${LAYERDIR_isar}/licenses/COPYING.GPLv2;md5=751419260
> >
> > PV = "0.2+7bf716d2"
> >
> > -SRC_URI = "git://github.com/ilbers/hello.git;protocol=https"
> > -SRCREV = "7bf716d22dbdb5a83edf0fe6134c0500f1a8b1f0"
> > +SRC_URI = "git://github.com/chombourger/hello.git;protocol=https"
> > +SRCREV = "3f05efe8cd471ce0313b5de6ea992c4a46e0e647"
> >
> > SRC_DIR = "git"
> >
> > If I bitbake example-hello, do_build will fail. The log will show:
> >
> > The following NEW packages will be installed:
> > libpci-dev libpci3 zlib1g-dev
> > 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
> > 1 not fully installed or removed.
> > Need to get 317 kB of archives.
> > After this operation, 703 kB of additional disk space will be used.
> > Do you want to continue? [Y/n] Abort.
> >
> > We get an "Abort" because we do not have a stdin when building from
> bitbake.
> >
> > Hope this helps
>
> Sure, thank you for the explanation!
>
> BTW: applied to next.
>
> >
> > Cedric
> >
> > On Monday, January 29, 2018 at 5:15:01 PM UTC+1, Alexander Smirnov
> wrote:
> >>
> >> On 01/29/2018 06:59 PM, Henning Schild wrote:
> >> > Am Mon, 29 Jan 2018 16:49:51 +0300
> >> > schrieb Alexander Smirnov <asmi...@ilbers.de <javascript:>>:
> >> >
> >> >> Hello Cedric,
> >> >>
> >> >> On 01/25/2018 11:36 PM, Cedric_H...@mentor.com <javascript:> wrote:
> >> >>> From: Cedric Hombourger <Cedric_H...@mentor.com <javascript:>>
> >> >>>
> >> >>> 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(-)
> >> >>>
> >> >>
> >> >
> >>
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "isar-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to isar-users+...@googlegroups.com <javascript:>.
> > To post to this group, send email to isar-...@googlegroups.com
> <javascript:>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/isar-users/d7821b41-5b3e-4b7a-b5cb-08938945ac8a%40googlegroups.com.
>
> > For more options, visit https://groups.google.com/d/optout.
> -
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 9556 bytes --]
prev parent reply other threads:[~2018-02-04 8:08 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
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 [this message]
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=6f48f86e-ade5-46f5-a2f7-05a8eecfbbdf@googlegroups.com \
--to=chombourger@gmail.com \
--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