Re: [PATCH v2 0/5] Debootstrap integration

[Claudius Heine <ch@denx.de>]

[-- Attachment #1.1: Type: text/plain, Size: 4079 bytes --]

Hi Alex,

On 02/22/2018 03:21 PM, 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)

Thx.

Is that the only issue that occured? In other words do all the other
targets where the key was available on the host run through without any
problems and the resulting image looks good? I am just asking to
decrease iteration over the testing-fixing cycle. If that is the only
problem, then I guess that this patchset can be merged after I
successfully fixed the usage of repository keys, right?

Since I am at the Embedded World as well, fixing this will be done in
the week after the following one.

Thanks again,
Claudius


-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

           PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                             Keyserver: hkp://pool.sks-keyservers.net


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]