From mboxrd@z Thu Jan  1 00:00:00 1970
X-GM-THRID: 6553303311112470528
X-Received: by 2002:a1c:af0e:: with SMTP id y14-v6mr703702wme.14.1525850494500;
        Wed, 09 May 2018 00:21:34 -0700 (PDT)
X-BeenThere: isar-users@googlegroups.com
Received: by 2002:adf:bb06:: with SMTP id r6-v6ls966727wrg.11.gmail; Wed, 09
 May 2018 00:21:34 -0700 (PDT)
X-Google-Smtp-Source: AB8JxZpNwaiv9rRmEqIfHKtyWwS6hunMxMLVH3KwlzI+R6jPDRPc4demHtQA/cTHAccpaL/B9xam
X-Received: by 2002:adf:9141:: with SMTP id j59-v6mr3226315wrj.3.1525850494049;
        Wed, 09 May 2018 00:21:34 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1525850494; cv=none;
        d=google.com; s=arc-20160816;
        b=BrC7mhHT7jbomMWJWyN4n5ZVCadr5h9ZG6erHTo7WyCdaeNeNoVgiCnsW1LuJ+59H+
         dMNnIhDtIQwhIx4zC17Db+zX18KXjSKovZVXb2NG4IcHDQ9/7xfuhuXAe30xNuBeZ+bL
         KaZybu+FteCBvBiTR8MPCemr6CPXSKp0OVoCp0NH73kwHL11oYuzPOdbXPXqTvrIIQOW
         7jFqagc51ZAQiakkB17i+6lUDsidCriNu14jD0c31LhUR/wm1kH3UxG88BxUrZbv6p42
         Af9avf4WJs16oKSa3g+Hs4remfkP47EAE51VFubRiTjl6AuV+il9fabTyn1j3B8zsgl/
         Pcbg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=content-transfer-encoding:mime-version:references:in-reply-to
         :message-id:subject:cc:to:from:date:arc-authentication-results;
        bh=oolq//chXNnKOxZVw6jAsHooSFLPaJH0h/84b8fUJ6g=;
        b=CI6h2FKYuNo3j5A+qdR5Kq5HGsOM/B6qp0aqwwLMl6+P58pdfMcdl8Daa/MFKJuGhY
         YintBTTsGqWZi+EkCXah8YlgHjEJ7FMgxG0OllwrWNMMsNDWLPoz5XFqFwWXdv1PuL/6
         BdBgFyzBhZf06J+4aB8fCa4oYDey9iHuVhz0sB1hHp6Xwk1fqzoj9PV9PtwkhKyml+zu
         quyJqiBGQTE1ZyIie3H9cIwz0gIFvKbQQ4kMxwT6CE9qrKhDAaNC4nn96Q7Ylg8qhRqD
         Xj11P0t8StxU7ESkP8s3OrzJDeK9nmdwdQJpWeA9tqb4cnHnuboyai2eDHFdOFDS9+3c
         6nag==
ARC-Authentication-Results: i=1; gmr-mx.google.com;
       spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com
Return-Path: <henning.schild@siemens.com>
Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28])
        by gmr-mx.google.com with ESMTPS id v12-v6si331723wmc.2.2018.05.09.00.21.33
        for <isar-users@googlegroups.com>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 09 May 2018 00:21:33 -0700 (PDT)
Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28;
Authentication-Results: gmr-mx.google.com;
       spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id w497LX0b010231
	(version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK);
	Wed, 9 May 2018 09:21:33 +0200
Received: from md1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40])
	by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id w497LX1G022383;
	Wed, 9 May 2018 09:21:33 +0200
Date: Wed, 9 May 2018 09:21:32 +0200
From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: image do_rootfs
Message-ID: <20180509092132.5cf9dfc4@md1pvb1c.ad001.siemens.net>
In-Reply-To: <40c26728-57a3-f9a0-09b6-052ee05f6961@ilbers.de>
References: <40c26728-57a3-f9a0-09b6-052ee05f6961@ilbers.de>
X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-TUID: lMX3LfONB0oE

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
>