xenomai.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Xenomai <xenomai@lists.linux.dev>
Subject: [xenomai-images][PATCH] linux-xenomai-3: Fix race between do_prepare_build and do_prepare_debian_rules
Date: Wed, 10 Jan 2024 19:11:32 +0100	[thread overview]
Message-ID: <fefd5b13-cde9-4232-b288-a21d211c6fce@siemens.com> (raw)

From: Jan Kiszka <jan.kiszka@siemens.com>

The former copies the files that the latter first wants to adjust.
Serialize them to fix build errors like this:

ERROR: linux-xenomai-3-9999-ga72af45114-r0 do_prepare_build: ExecutionError('/builds/Xenomai/xenomai-images/build/tmp/work/xenomai-demo-amd64/linux-xenomai-3/9999-ga72af45114-r0/temp/run.do_prepare_build.57941', 1, None, None)
ERROR: Logfile of failure stored in: /builds/Xenomai/xenomai-images/build/tmp/work/xenomai-demo-amd64/linux-xenomai-3/9999-ga72af45114-r0/temp/log.do_prepare_build.57941
ERROR: Task (/builds/Xenomai/xenomai-images/build/../recipes-kernel/linux/linux-xenomai-3_latest.bb:do_prepare_build) failed with exit code '1'

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 recipes-kernel/linux/linux-xenomai-3.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-xenomai-3.inc b/recipes-kernel/linux/linux-xenomai-3.inc
index 64ed9d0..85ed105 100644
--- a/recipes-kernel/linux/linux-xenomai-3.inc
+++ b/recipes-kernel/linux/linux-xenomai-3.inc
@@ -22,4 +22,4 @@ do_prepare_debian_rules() {
     mv ${WORKDIR}/debian/rules ${WORKDIR}/debian/rules.isar
     mv ${WORKDIR}/rules ${WORKDIR}/debian/rules
 }
-addtask prepare_debian_rules after do_transform_template before do_dpkg_build
+addtask prepare_debian_rules after do_transform_template before do_prepare_build
-- 
2.35.3

                 reply	other threads:[~2024-01-10 18:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=fefd5b13-cde9-4232-b288-a21d211c6fce@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=xenomai@lists.linux.dev \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).