image do_rootfs

image do_rootfs

[Alexander Smirnov]

Hi all,

After some digging in image recipe, I've noticed that current Isar next 
branch contains an error in log from do_rootfs. You may find it, for 
example in 
'tmp/work/debian-stretch-amd64/isar-image-base/temp/log.do_rootfs':

8<--
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such 
device)
8<--

So two questions:

1. Why bitbake skips this error and doesn't stop, will we catch any 
other possible error that could occur?

2. Is it normal behavior for apt-get, i.e. what is the criticality of 
this error?

Alex

Re: image do_rootfs

[Henning Schild]

Am Tue, 8 May 2018 23:03:38 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:

> Hi all,
> 
> After some digging in image recipe, I've noticed that current Isar
> next branch contains an error in log from do_rootfs. You may find it,
> for example in 
> 'tmp/work/debian-stretch-amd64/isar-image-base/temp/log.do_rootfs':
> 
> 8<--
> E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No
> such device)
> 8<--

I have seen this as well, decided to ignore it at the moment because i
saw it mixed up with other errors which my recipe caused.

> So two questions:
> 
> 1. Why bitbake skips this error and doesn't stop, will we catch any 
> other possible error that could occur?
> 
> 2. Is it normal behavior for apt-get, i.e. what is the criticality of 
> this error?

I do not know. But it might be worth checking Claudius outstanding
patches to find an answer/fix.

There are also several of my patches that still wait for review.

Henning
 
> Alex
>