From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Alexander Smirnov <asmirnov@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/5] Rework isar-apt v2
Date: Fri, 9 Feb 2018 11:30:25 +0100 [thread overview]
Message-ID: <20180209113025.0dbf6b13@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <3bbf6184-ffe2-3e65-095c-927430170aae@siemens.com>
Am Thu, 8 Feb 2018 16:09:14 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> On 2018-02-08 15:59, [ext] Henning Schild wrote:
> > Hi,
> >
> > if that is the series that went into next already, it can not deal
> > with IMAGE_INSTALL not containing any recipes.
> > In that case we do not built a buildchroot and at install time we do
> > not have a repo for the image-rootfs.
> >
> >> W: Failed to fetch
> >> copy://builder/build/tmp/deploy/apt/debian-stretch/dists/isar/main/binary-amd64/Packages
> >> Failed to stat - stat (2: No such file or directory)
> >
> > The easiest solution is probably to call do_cache_config
> > independant of whether we will actually fill it with packages
> > later.
>
> Good catch. It's papered over by my "Install kernel via replaceable
> recipe" because that will now always need at least one recipe.
> Probably worth fixing nevertheless to once support kernel-free builds.
Yes, it should be fixed and actually got fixed in current next
"image: Add dependency from isar-apt"
Thanks Alex,
Henning
> Jan
>
next prev parent reply other threads:[~2018-02-09 10:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 9:59 Alexander Smirnov
2018-02-05 9:59 ` [PATCH 1/5] Update isar-bitbake.conf according to the changes in bitbake related to multiconfig support Alexander Smirnov
2018-02-05 10:15 ` Jan Kiszka
2018-02-05 10:26 ` Alexander Smirnov
2018-02-05 10:27 ` Jan Kiszka
2018-02-05 9:59 ` [PATCH 2/5] isar-apt: Introduce separate recipe Alexander Smirnov
2018-02-05 9:59 ` [PATCH 3/5] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-05 10:18 ` Jan Kiszka
2018-02-05 10:33 ` Alexander Smirnov
2018-02-05 9:59 ` [PATCH 4/5] build.sh: Update apt sources Alexander Smirnov
2018-02-05 9:59 ` [PATCH 5/5] build.sh: Force 'yes' for apt Alexander Smirnov
2018-02-05 11:52 ` Jan Kiszka
2018-02-05 13:56 ` Alexander Smirnov
2018-02-05 13:48 ` [PATCH 3/5 v2] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-06 11:01 ` [PATCH 3/5 v3] " Alexander Smirnov
2018-02-06 12:10 ` Jan Kiszka
2018-02-06 13:28 ` Alexander Smirnov
2018-02-05 14:41 ` [PATCH 0/5] Rework isar-apt v2 Alexander Smirnov
2018-02-05 16:47 ` Jan Kiszka
2018-02-05 16:56 ` Alexander Smirnov
2018-02-06 13:57 ` [PATCH 3/5 v4] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-06 17:31 ` Jan Kiszka
2018-02-06 18:29 ` Alexander Smirnov
2018-02-06 18:31 ` Jan Kiszka
2018-02-08 14:37 ` Henning Schild
2018-02-08 14:57 ` Alexander Smirnov
2018-02-06 20:24 ` [PATCH 0/5] Rework isar-apt v2 Alexander Smirnov
2018-02-08 14:59 ` Henning Schild
2018-02-08 15:09 ` Jan Kiszka
2018-02-09 10:30 ` Henning Schild [this message]
2018-02-08 17:03 ` Benedikt Niedermayr
2018-02-08 18:27 ` Benedikt Niedermayr
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=20180209113025.0dbf6b13@mmd1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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