From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6550674890117087232 X-Received: by 2002:a19:c209:: with SMTP id l9-v6mr738134lfc.37.1525250997844; Wed, 02 May 2018 01:49:57 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a19:cf0e:: with SMTP id f14-v6ls1095196lfg.5.gmail; Wed, 02 May 2018 01:49:56 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqS52Zp5wiBOjnND80u0RkkYubh+chGkNokWJ6K5hdiD0O80iArrWAvZEyi5seRTEpgT+yI X-Received: by 2002:a19:20ce:: with SMTP id g197-v6mr1001701lfg.34.1525250996828; Wed, 02 May 2018 01:49:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525250996; cv=none; d=google.com; s=arc-20160816; b=lw5hj+bS/XvWocNkIjhuuJ7kW6+VdvXzONmdNZkceqacT3/uDTiNZx2/yRj+j1Wj3b bTBuNrYMT4QRz9fwIQVGjMC8kGz5N2j17n71aFH6fYLHdBS2ZFeEwfSRFHRunWAMjEft N0MboRhz3F9wH8UnS+RIXqNIGfi2wh0mk6GZTiYu1Ke+vHWkd/mWGE4h6aTOVcG2imwG TWBSZvG10BtG6Pqej3mObI+hAI0l8xn4j1bvvaPEkkv0LVtdDaMkN2DNb0+HgDa47y5k /3csHeKyatuor9Tx0ISJbeu5SgHLBMxy2SikApI+YkfQ4z4XUjog6h0hG654fo6u+q4u 84AA== 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=vkKqotUNjYaGDzf7fojoH8H6T8Ti31javGprGXPD9KI=; b=QdZX7UL76PjyuNoA6Ru7eRwdDgW4+kyCnwbIkwIjK/EafrKFMeWqMI9ArGgUifkCrW u7w+M1rJqw5FnPK5q3qtFU+hgXOim6zeewncz5cExDFfKQ8F2uFxwRZIR8OlUKZEL70b 5YCmrDbBJwxz2ZhmeMnWDwVR+VmIoWXFynCYwAG5V7nTNo4t4jCoCQY1IRRjV6WFR3Ib WVm6ACzltrBzbNhRpat7ocuoAKfVjtKkeZeaTFhKXnAsJgnWwxUtfuql3VpRv/Cz91+E 9FJ5MyXn/0LhRzC7PxSVr5NMbVu3yKWR08ZVQ0pAO4IcnlU49YioGq6prN8JNepIAPRh Hl0A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id e1-v6si380053ljk.0.2018.05.02.01.49.56 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 May 2018 01:49:56 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w428nubo011636 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 2 May 2018 10:49:56 +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 w428ntMN003810; Wed, 2 May 2018 10:49:55 +0200 Date: Wed, 2 May 2018 10:49:55 +0200 From: Henning Schild To: Alexander Smirnov Cc: isar-users Subject: Re: Issues with debootstrap Message-ID: <20180502104955.2a404e7a@md1pvb1c.ad001.siemens.net> In-Reply-To: References: 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: TtB6SmUJcKVg Am Tue, 1 May 2018 21:03:58 +0300 schrieb Alexander Smirnov : > Hi all, > > just a few findings in Isar: > > 1. Sometimes I have the following error building Isar on Jessie: > > ERROR: Logfile of failure stored in: > /workspace/build/Isar_asmirnov_devel/28/build/tmp/work/debian-stretch-arm64/isar-bootstrap/temp/log.do_apt_update.19671 > Log data follows: > | DEBUG: Executing shell function do_apt_update > | Ign:1 http://ftp.de.debian.org/debian stretch InRelease > | Get:2 http://security.debian.org stretch/updates InRelease [94.3 kB] > | Get:3 http://ftp.de.debian.org/debian stretch-updates InRelease > [91.0 kB] | Get:4 http://ftp.de.debian.org/debian stretch Release > [118 kB] | Get:5 http://ftp.de.debian.org/debian stretch Release.gpg > [2434 B] | Get:6 http://security.debian.org stretch/updates/main > arm64 Packages [353 kB] > | Get:7 http://security.debian.org stretch/updates/main > Translation-en [164 kB] > | Get:8 http://security.debian.org stretch/updates/contrib arm64 > Packages [1776 B] > | Get:9 http://security.debian.org stretch/updates/contrib > Translation-en [1759 B] > | Get:10 http://security.debian.org stretch/updates/non-free arm64 > Packages [1268 B] > | Get:11 http://security.debian.org stretch/updates/non-free > Translation-en [481 B] > | Get:12 http://ftp.de.debian.org/debian stretch-updates/main arm64 > Packages [10.9 kB] > | Get:13 http://ftp.de.debian.org/debian stretch-updates/main > Translation-en [6782 B] > | Get:14 http://ftp.de.debian.org/debian stretch/main arm64 Packages > [6963 kB] > | Get:15 http://ftp.de.debian.org/debian stretch/main Translation-en > [5394 kB] > | Get:16 http://ftp.de.debian.org/debian stretch/contrib arm64 > Packages [39.9 kB] > | Get:17 http://ftp.de.debian.org/debian stretch/contrib > Translation-en [45.9 kB] > | Get:18 http://ftp.de.debian.org/debian stretch/non-free arm64 > Packages [50.8 kB] > | Get:19 http://ftp.de.debian.org/debian stretch/non-free > Translation-en [80.1 kB] > | Fetched 13.4 MB in 26s (516 kB/s) > | Reading package lists...E: Dynamic MMap ran out of room. Please > increase the size of APT::Cache-Start. Current value: 25165824. (man > 5 apt.conf) > | qemu: uncaught target signal 11 (Segmentation fault) - core dumped > | WARNING: exit code 139 from a shell command. > | ERROR: Function failed: do_apt_update (log file is located at > /workspace/build/Isar_asmirnov_devel/28/build/tmp/work/debian-stretch-arm64/isar-bootstrap/temp/log.do_apt_update.19671) > > Google [1] suggests to add the following line to debconf: > > APT::Cache-Limit "100000000" > > Didn't test this yet. > > [1]: > https://stackoverflow.com/questions/11911495/increase-the-size-of-aptcache-limit Have not seen that before. But i guess you can provoke it by adding a ton of packages. Before adding the "workaround" i would suggest trying a more recent debootstrap. Adding this config parameter means having to remove it later, and detecting that it is the one introduces by isar ... and not i.e. by a package or hook. > 2. I've noticed, that Isar uses debootsrap variants. What is the idea > doing this? Old debootstrap versions, for example jessie, doesn't > support latest distributions, for example buster. So we have limited > matrix of supported configurations host_version<->target_version. Why > can't we explicitly mention list of necessary packages using > '--include' parameter for debootstrap? Sounds like an interesting improvement. It might also enable building Ubuntu and other Debian-based distros with Isar. Henning > > With best regards, > Alex >