From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] Add skeleton dir option
Date: Thu, 1 Aug 2019 16:23:09 +0200 [thread overview]
Message-ID: <2686976d-0b2e-97ea-cc14-3eb37a902e29@siemens.com> (raw)
In-Reply-To: <20190801095045.GI14716@yssyq.m.ilbers.de>
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
On 8/1/19 11:50 AM, Baurzhan Ismagulov wrote:
> On Thu, Aug 01, 2019 at 09:02:48AM +0200, Quirin Gylstorff wrote:
>> I build it on my machine and the patch set applied to next worked. I don't
>> think the /dev/pts error is from the patch set. It could be a follow up from
>> this one:
>>
>> OTE: Executing RunQueue Tasks
>> ERROR: mc:qemuarm64-stretch:isar-image-base-debian-stretch-qemuarm64
>> do_rootfs_postprocess: Function failed: image_configure_accounts (log file
>> is located at /home/ibr/w/work/j/isar/src/b-20190729-skel-applied/tmp/work/debian-stretch-arm64/isar-image-base-debian-stretch-qemuarm64/temp/log.do_rootfs_postprocess.25984)
>> ERROR: Logfile of failure stored in: /home/ibr/w/work/j/isar/src/b-20190729-skel-applied/tmp/work/debian-stretch-arm64/isar-image-base-debian-stretch-qemuarm64/temp/log.do_rootfs_postprocess.25984
>>
>>
>> Can you sent log.do_rootfs_postprocess.25984 ?
>
> Attached. It fails to chroot into
> debian-stretch-arm64/isar-image-base-debian-stretch-qemuarm64/rootfs on my
> host. qemu-aarch64 is enabled in update-binfmts --display, the interpreter =
> /usr/bin/qemu-aarch64-static is installed. Do we have any host tools / libs
> missing in user_manual.md?
>
> Interestingly, the task didn't fail for next.
>
I have no idea, it sounds like it specific to your setup. Can you try to
rebuild it with kas-docker?
Set up a minimal kas.yml and enter it with kas-docker --isar shell and
source the isar-init-build-env and start the build. Then we have the
setup specific errors removed?
Kind regards,
Quirin
[-- Attachment #2: kas.yml --]
[-- Type: text/plain, Size: 171 bytes --]
#
# Copyright (c) Siemens AG, 2019
#
# Licensed under the Siemens Inner Source License 1.2, or at your option any
# later version.
#
header:
version: 8
repos:
isar:
next prev parent reply other threads:[~2019-08-01 14:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 12:36 Quirin Gylstorff
2019-07-19 12:38 ` [PATCH 1/3] image-account-extension: " Quirin Gylstorff
2019-07-19 12:38 ` [PATCH 2/3] meta-isar: Add example for user settings Quirin Gylstorff
2019-07-23 8:08 ` Henning Schild
2019-07-23 12:00 ` Quirin Gylstorff
2019-07-23 12:03 ` [PATCH 0/3] Add skeleton dir option Quirin Gylstorff
2019-07-23 12:06 ` Quirin Gylstorff
2019-07-23 12:06 ` [PATCH v2 1/3] image-account-extension: " Quirin Gylstorff
2019-07-23 12:06 ` [PATCH v2] ubifs-img: Correct function name Quirin Gylstorff
2019-07-23 12:06 ` [PATCH v2 2/3] meta-isar: Add example for user settings Quirin Gylstorff
2019-07-23 12:06 ` [PATCH v2 3/3] image-account-extension:Move configure_accounts to postprocess Quirin Gylstorff
2019-07-29 21:25 ` [PATCH 0/3] Add skeleton dir option Baurzhan Ismagulov
2019-07-31 11:44 ` Quirin Gylstorff
2019-07-31 12:40 ` Baurzhan Ismagulov
2019-07-31 14:49 ` Henning Schild
2019-07-31 17:23 ` Baurzhan Ismagulov
2019-08-01 16:10 ` Baurzhan Ismagulov
2019-08-01 7:02 ` Quirin Gylstorff
2019-08-01 9:50 ` Baurzhan Ismagulov
2019-08-01 14:23 ` Quirin Gylstorff [this message]
2019-07-19 12:38 ` [PATCH 3/3] image-account-extension:Move configure_accounts to postprocess Quirin Gylstorff
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=2686976d-0b2e-97ea-cc14-3eb37a902e29@siemens.com \
--to=quirin.gylstorff@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