public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH 1/2] image: Make mount points imagetype-specific
Date: Tue, 28 Dec 2021 09:29:31 +0300	[thread overview]
Message-ID: <20211228062932.167496-2-amikan@ilbers.de> (raw)
In-Reply-To: <20211228062932.167496-1-amikan@ilbers.de>

When building two multiconfigs of the same target with different image
types they will share deploy, rootfs and work buildchrot mountpoints
with the same names. This can cause the following error:

DEBUG: Executing shell function do_cpiogz_image
/usr/bin/find: failed to read file names from file system at or below '.': No such file or directory
799078 blocks
ERROR: [Errno 2] No such file or directory: 'tmp/work/debian-buster-amd64/isar-image-base-qemuamd64-cpiogz-img/1.0-r0/temp/fifo.17814'

To fix the issue mountpoints should be splitted based on the image
suffix.

Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
 meta/classes/image.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index e98856b..bd58056 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -28,7 +28,7 @@ INITRD_IMAGE ?= "${IMAGE_FULLNAME}-initrd.img"
 DTB_FILES ?= ""
 
 # Useful variables for imager implementations:
-PP = "/home/builder/${PN}"
+PP = "/home/builder/${PN}-${IMAGE_SUFFIX}"
 PP_DEPLOY = "${PP}/deploy"
 PP_ROOTFS = "${PP}/rootfs"
 PP_WORK = "${PP}/work"
-- 
2.25.1


  reply	other threads:[~2021-12-28  6:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28  6:29 [PATCH 0/2] Protect parallel image building Anton Mikanovich
2021-12-28  6:29 ` Anton Mikanovich [this message]
2021-12-28  6:29 ` [PATCH 2/2] image: Protect shared deploy directory usage Anton Mikanovich
2022-01-10  7:50 ` [PATCH 0/2] Protect parallel image building Anton Mikanovich

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=20211228062932.167496-2-amikan@ilbers.de \
    --to=amikan@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