From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>, Claudius Heine <ch@denx.de>
Subject: isar-bootstrap fails to rebuild after config changes
Date: Mon, 12 Aug 2019 19:18:48 +0200 [thread overview]
Message-ID: <fa96e417-2516-177d-e58b-192dd42bb927@siemens.com> (raw)
Hi,
I noticed today that I'm not getting a new bootstrap rootfs after adding a repo
to DISTRO_APT_SOURCES. Digging deeper, this revealed missing STAMPCLEAN setting,
but also more:
Why are we probing for the existence of the DEPLOY_ISAR_BOOTSTRAP link in
do_apt_config_prepare(), Claudius? This obviously exists after a first run, and
that blocks refreshing all the apt settings if they have changed.
There is CLEANFUNCS set with clean_deploy(), but that is only run on true
do_clean(), not on rebuilds.
And finally, when I look at isar_bootstrap(), run by do_bootstrap(), it protects
checking and creating DEPLOY_ISAR_BOOTSTRAP with a lock. But
do_apt_config_prepare() runs lockless. This cannot work reliably.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next reply other threads:[~2019-08-12 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 17:18 Jan Kiszka [this message]
2019-08-13 8:01 ` Claudius Heine
2019-08-13 8:14 ` Jan Kiszka
2019-08-20 19:33 ` Jan Kiszka
2019-08-21 9:02 ` Baurzhan Ismagulov
2019-08-21 9:06 ` Jan Kiszka
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=fa96e417-2516-177d-e58b-192dd42bb927@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ch@denx.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