Issues with debootstrap

Issues with debootstrap

[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


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?

With best regards,
Alex

Re: Issues with debootstrap

[Henning Schild]

Am Tue, 1 May 2018 21:03:58 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:

> 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
>