From: Alexander Smirnov <asmirnov@ilbers.de>
To: claudius.heine.ext@siemens.com, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH v2 0/5] Debootstrap integration
Date: Thu, 22 Feb 2018 17:21:26 +0300 [thread overview]
Message-ID: <e68b0082-5de2-e907-9012-8240107c7020@ilbers.de> (raw)
In-Reply-To: <20180222131901.20915-1-claudius.heine.ext@siemens.com>
On 02/22/2018 04:18 PM, claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
>
> Hi,
>
> this is the new rebased and fixed version of this patchset.
>
> Cheers,
> Claudius
>
> Changes from v1:
> - rebased to current next
> - added unmounting of /dev and /proc at the end of do_rootfs in isar-image-base
> This was necessary for image file creation, otherwise it tried to
> package stuff from the host.
> - added 'isar-bootstrap:do_deploy' dependency to do_rootfs task in
> image.bbclass.
> - Changed 'RFSDIR' variable name to 'ROOTFSDIR' in
> isar-bootstrap-helper.bbclass to be consistent with the variable
> name in isar-bootstrap.bb
> - Moved 'isar-apt' apt-preference settings from isar-bootstrap.bb to
> isar-bootstrap-helper.bbclass
> - Removed '--no-install-recommends' parameters in favor of adding the
> apt configuration in 'isar-bootstrap.bb'
> - unmount and remove possible existing bootstraped directories before
> bootstrapping in do_bootstrap task of 'isar-bootstrap.bb'
> - changed from /dev ro bind mounts to mounting devtmpfs to /dev to be
> consistent with the other places where /dev is mounted.
>
$ time bitbake multiconfig:qemuarm-wheezy:isar-image-base
multiconfig:qemuarm-jessie:isar-image-base
multiconfig:qemuarm-stretch:isar-image-base
multiconfig:qemui386-jessie:isar-image-base
multiconfig:qemui386-stretch:isar-image-base
multiconfig:qemuamd64-jessie:isar-image-base
multiconfig:qemuamd64-stretch:isar-image-base
multiconfig:rpi-jessie:isar-image-base
multiconfig:qemuarm64-stretch:isar-image-base
ERROR: mc:rpi-jessie:isar-bootstrap-1.0-r0 do_bootstrap: Function
failed: do_bootstrap (log file is located at
/home/builder/isar/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap/temp/log.do_bootstrap.29056)
ERROR: Logfile of failure stored in:
/home/builder/isar/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap/temp/log.do_bootstrap.29056
ERROR: Task
(multiconfig:rpi-jessie:/home/builder/isar/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb:do_bootstrap)
failed with exit code '1'
builder@zbook:~/isar$ cat
/home/builder/isar/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap/temp/log.do_bootstrap.29056
DEBUG: Executing shell function do_bootstrap
I: Running command: debootstrap --arch armhf --foreign --verbose
--variant minbase --components=main,contrib,non-free,firmware jessie
/home/builder/isar/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap/rootfs
http://archive.raspbian.org/raspbian
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
E: Release signed by unknown key (key id 9165938D90FDDD2E)
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_bootstrap (log file is located at
/home/builder/isar/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap/temp/log.do_bootstrap.29056)
Alex
next prev parent reply other threads:[~2018-02-22 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 13:18 claudius.heine.ext
2018-02-22 13:18 ` [PATCH v2 1/5] implement isar-bootstrap using debootstrap claudius.heine.ext
2018-02-23 20:39 ` Jan Kiszka
2018-02-22 13:18 ` [PATCH v2 2/5] meta/isar-bootstrap-helper.bbclass: handle rfs customization centrally claudius.heine.ext
2018-02-22 13:18 ` [PATCH v2 3/5] meta/buildchroot: switch to using isar-bootstrap claudius.heine.ext
2018-02-23 20:44 ` Jan Kiszka
2018-02-22 13:19 ` [PATCH v2 4/5] meta-isar/isar-image-base: " claudius.heine.ext
2018-02-23 20:45 ` Jan Kiszka
2018-02-22 13:19 ` [PATCH v2 5/5] meta-isar/multiconfig: remove multistrap references claudius.heine.ext
2018-02-23 20:46 ` Jan Kiszka
2018-02-22 14:21 ` Alexander Smirnov [this message]
2018-02-22 18:09 ` [PATCH v2 0/5] Debootstrap integration Jan Kiszka
2018-02-23 7:40 ` Claudius Heine
2018-02-23 20:35 ` Jan Kiszka
2018-02-26 6:43 ` Jan Kiszka
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=e68b0082-5de2-e907-9012-8240107c7020@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.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