From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 3/4] build.sh: Update apt sources
Date: Thu, 1 Feb 2018 12:40:30 +0100 [thread overview]
Message-ID: <dab9ddd9-9f98-63b3-f9da-bb0241d8675c@siemens.com> (raw)
In-Reply-To: <20180201112944.7877-4-asmirnov@ilbers.de>
On 2018-02-01 12:29, Alexander Smirnov wrote:
> Trigger apt sources update before building the package to be sure that
> we are in sync with isar-apt content.
>
> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
> ---
> meta/recipes-devtools/buildchroot/files/build.sh | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-devtools/buildchroot/files/build.sh b/meta/recipes-devtools/buildchroot/files/build.sh
> index 77e0fdd..5c59193 100644
> --- a/meta/recipes-devtools/buildchroot/files/build.sh
> +++ b/meta/recipes-devtools/buildchroot/files/build.sh
> @@ -3,6 +3,9 @@
> # This software is a part of ISAR.
> # Copyright (C) 2015-2017 ilbers GmbH
>
> +# Make sure that we have latest isar-apt content
> +apt-get update
> +
Can we confine this to the isar-apt repo? Or is there no risk that an
upstream repo update will result in a buildchroot change that is
inconsistent with an earlier build stage?
Jan
> # Go to build directory
> cd $1
>
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-02-01 11:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 11:29 [PATCH 0/4] Rework isar-apt Alexander Smirnov
2018-02-01 11:29 ` [PATCH 1/4] isar-apt: Introduce separate recipe Alexander Smirnov
2018-02-01 11:29 ` [PATCH 2/4] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-04 12:06 ` Jan Kiszka
2018-02-01 11:29 ` [PATCH 3/4] build.sh: Update apt sources Alexander Smirnov
2018-02-01 11:40 ` Jan Kiszka [this message]
2018-02-01 11:48 ` Alexander Smirnov
2018-02-01 13:13 ` Jan Kiszka
2018-02-01 13:43 ` Alexander Smirnov
2018-02-01 14:28 ` Jan Kiszka
2018-02-01 11:29 ` [PATCH 4/4] build.sh: Force 'yes' for apt Alexander Smirnov
2018-02-01 11:41 ` Jan Kiszka
2018-02-01 12:27 ` Alexander Smirnov
2018-02-01 16:14 ` [PATCH 0/4] Rework isar-apt Jan Kiszka
2018-02-01 16:22 ` Alexander Smirnov
2018-02-01 16:25 ` Jan Kiszka
2018-02-01 16:54 ` Alexander Smirnov
2018-02-01 17:03 ` Jan Kiszka
2018-02-01 20:32 ` Alexander Smirnov
2018-02-01 18:37 ` Claudius Heine
2018-02-01 19:37 ` Alexander Smirnov
2018-02-01 20:09 ` Claudius Heine
2018-02-01 20:13 ` Claudius Heine
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=dab9ddd9-9f98-63b3-f9da-bb0241d8675c@siemens.com \
--to=jan.kiszka@siemens.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