Re: [PATCH v2 0/5] Debootstrap integration

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2018-02-22 15:21, Alexander Smirnov wrote:
> 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)
> 

Looks like we are lucky that the other bootstraps work, maybe due to the
keys installed on the host: there are no key rings specified so far.

Jan