From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/4] Make adjust_git work in both worlds
Date: Fri, 13 Aug 2021 12:13:06 +0200 [thread overview]
Message-ID: <0a83a4d0-ecbb-e5ae-047d-c362daa8e55f@siemens.com> (raw)
In-Reply-To: <3710f21b-429e-40c2-8a8f-814bf1b734c2n@googlegroups.com>
On 13.08.21 10:31, Uladzimir Bely wrote:
> I've checked your series in CI (fast run) and it was OK.
>
> Actually, the problem with cowsay rebuild appeared on some manual work
> with ISAR, when some changes in configuration were done and rebuild was
> started on top of previous build. So, the problem was reproducable only
> in such manual conditions.
>
> I'm going to add some test to CI that will reproduce these conditions so
> that we would be sure the fix is complete.
>
Great, thanks in advance!
Jan
> On Thursday, August 12, 2021 at 2:48:54 PM UTC+3 Jan Kiszka wrote:
>
> Finally allow the adjusted git repos work both inside and outside the
> buildchroots. Also fixes the race introduced by patching links in
> DL_DIR.
>
> Changes in v2:
> - build relative alternates path so that destsuffix paths are respected
> - fix task dependencies so that devshell gets adjusted git again
>
> NOTE: Still not yet fully tested, fast CI takes 3:30h (plus retries).
>
> Jan
>
> Jan Kiszka (4):
> dpkg-base: Lock do_adjust_git against each other
> dpkg-base: Make mirror link relative
> Rework do_adjust_git to support inside and outside usage
> Revert "dpkg: adjust task order to allow using "git" for patching"
>
> meta/classes/dpkg-base.bbclass | 22 ++++++++++++++-----
> meta/conf/bitbake.conf | 1 +
> .../buildchroot/buildchroot.inc | 2 ++
> 3 files changed, 20 insertions(+), 5 deletions(-)
>
> --
> 2.31.1
>
> --
> You received this message because you are subscribed to the Google
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to isar-users+unsubscribe@googlegroups.com
> <mailto:isar-users+unsubscribe@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/3710f21b-429e-40c2-8a8f-814bf1b734c2n%40googlegroups.com
> <https://groups.google.com/d/msgid/isar-users/3710f21b-429e-40c2-8a8f-814bf1b734c2n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-08-13 10:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 11:48 Jan Kiszka
2021-08-12 11:48 ` [PATCH v2 1/4] dpkg-base: Lock do_adjust_git against each other Jan Kiszka
2021-08-13 13:55 ` Henning Schild
2021-08-15 18:55 ` Jan Kiszka
2021-08-26 8:00 ` [PATCH v3 " Jan Kiszka
2021-08-26 8:06 ` Jan Kiszka
2021-08-12 11:48 ` [PATCH v2 2/4] dpkg-base: Make mirror link relative Jan Kiszka
2021-08-13 14:04 ` Henning Schild
2021-08-13 17:49 ` [PATCH] dpkg-base: "unshare" git clones in adjust_git Henning Schild
2021-08-13 20:13 ` [PATCH v2] " Henning Schild
2021-08-13 20:14 ` Henning Schild
2021-08-15 18:55 ` [PATCH] " Jan Kiszka
2021-08-16 11:36 ` Henning Schild
2021-08-16 16:57 ` Jan Kiszka
2021-08-12 11:48 ` [PATCH v2 3/4] Rework do_adjust_git to support inside and outside usage Jan Kiszka
2021-08-12 11:48 ` [PATCH v2 4/4] Revert "dpkg: adjust task order to allow using "git" for patching" Jan Kiszka
2021-08-13 8:31 ` [PATCH v2 0/4] Make adjust_git work in both worlds Uladzimir Bely
2021-08-13 10:13 ` Jan Kiszka [this message]
2021-08-13 12:23 ` Uladzimir Bely
2021-08-13 12:28 ` Jan Kiszka
2021-08-13 12:40 ` Uladzimir Bely
2021-08-15 19:02 ` Jan Kiszka
2021-08-16 7:52 ` Uladzimir Bely
2021-08-16 7:55 ` Jan Kiszka
2021-08-16 8:27 ` Uladzimir Bely
2021-08-16 10:45 ` Jan Kiszka
2021-08-16 11:01 ` Jan Kiszka
2021-08-16 11:26 ` Henning Schild
2021-08-16 12:49 ` Uladzimir Bely
2021-08-19 6:17 ` Uladzimir Bely
2021-08-19 6:21 ` Jan Kiszka
2021-08-26 7:57 ` Jan Kiszka
2021-08-27 8:39 ` ub...@ilbers.de
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=0a83a4d0-ecbb-e5ae-047d-c362daa8e55f@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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