From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/2] Various bug fixes
Date: Fri, 10 Aug 2018 12:31:48 +0200 [thread overview]
Message-ID: <20180810103150.28342-1-mosipov@ilbers.de> (raw)
Hello everybody,
This series contains fixes for bugs
discovered during CI server migration to Debian 9.x (stretch).
* The first patch fixes the bug when home directory path name was too long for 'gpg'.
* The second patch fixes the bug discovered when qemu-user-static package (containing qemu-debootstrap) was not installed
by occasion, which leaded to wrong behaviour:
=====
/workspace/build/isar_mosipov_next/24/build/tmp/work/debian-stretch-amd64/isar-bootstrap-target/temp$ cat log.do_bootstrap
DEBUG: Executing shell function do_bootstrap
sudo: qemu-debootstrap: command not found
<snip>
sed: can't read /workspace/build/isar_mosipov_next/24/build/tmp/work/debian-stretch-amd64/isar-bootstrap-target/rootfs/etc/locale.gen: No such file or directory
chroot: failed to run command ‘/usr/sbin/locale-gen’: No such file or directory
'/workspace/build/isar_mosipov_next/24/build/tmp/work/debian-stretch-amd64/isar-bootstrap-target/chroot-setup.sh' -> '/workspace/build/isar_mosipov_next/24/build/tmp/work/debian-stretch-amd64/isar-bootstrap-target/rootfs/chroot-setup.sh'
Target '/workspace/build/isar_mosipov_next/24/build/tmp/work/debian-stretch-amd64/isar-bootstrap-target/rootfs' does not exist or does contain required directories
<snip>
mount: mount point /workspace/build/isar_mosipov_next/24/build/tmp/work/debian-stretch-amd64/isar-bootstrap-target/rootfs/dev does not exist
mount: mount point /workspace/build/isar_mosipov_next/24/build/tmp/work/debian-stretch-amd64/isar-bootstrap-target/rootfs/proc does not exist
chroot: failed to run command ‘/usr/bin/apt-get’: No such file or directory
chroot: failed to run command ‘/usr/bin/apt-get’: No such file or directory
DEBUG: Shell function do_bootstrap finished
====
Kind regards,
Maxim.
Maxim Yu. Osipov (2):
isar-bootstrap: Fix gpg error file name too long
isar-bootstrap: exit if command fails under flock
.../recipes-core/isar-bootstrap/isar-bootstrap.inc | 32 +++++++++++-----------
1 file changed, 16 insertions(+), 16 deletions(-)
--
2.11.0
next reply other threads:[~2018-08-10 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 10:31 Maxim Yu. Osipov [this message]
2018-08-10 10:31 ` [PATCH 1/2] isar-bootstrap: Fix gpg error file name too long Maxim Yu. Osipov
2018-08-13 8:16 ` Henning Schild
2018-08-27 22:07 ` Maxim Yu. Osipov
2018-08-10 10:31 ` [PATCH 2/2] isar-bootstrap: exit if command fails under flock Maxim Yu. Osipov
2018-08-11 15:52 ` Jan Kiszka
2018-08-12 8:46 ` Maxim Yu. Osipov
2018-08-13 8:34 ` Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180810103150.28342-1-mosipov@ilbers.de \
--to=mosipov@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox