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 v2 2/4] ccache: fix CCACHE_DIR owner for sbuild
Date: Mon, 13 Feb 2023 09:56:09 +0200	[thread overview]
Message-ID: <20230213075611.5694-3-amikan@ilbers.de> (raw)
In-Reply-To: <20230213075611.5694-1-amikan@ilbers.de>

If CCACHE_DIR do not exist before sbuild execution it is created with root
privileges. Previous 'install' implementation did not work for some reason.
This results in permissions issues during the next usage by the imager.
Create CCACHE_DIR before sbuild to fix that.

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

diff --git a/meta/classes/sbuild.bbclass b/meta/classes/sbuild.bbclass
index 6e3c790..ea3fb34 100644
--- a/meta/classes/sbuild.bbclass
+++ b/meta/classes/sbuild.bbclass
@@ -128,12 +128,12 @@ EOSUDO
 }
 
 schroot_configure_ccache() {
+    mkdir -p "${CCACHE_DIR}"
     sudo -s <<'EOSUDO'
         set -e
 
         sbuild_fstab="${SBUILD_CONF_DIR}/fstab"
 
-        install --group=sbuild --mode=2775 -d ${CCACHE_DIR}
         fstab_ccachedir="${CCACHE_DIR} /ccache none rw,bind 0 0"
         grep -qxF "${fstab_ccachedir}" ${sbuild_fstab} || echo "${fstab_ccachedir}" >> ${sbuild_fstab}
 
-- 
2.34.1


  parent reply	other threads:[~2023-02-13  7:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  7:56 [PATCH v2 0/4] Fix ccache issues Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 1/4] ccache: fix dirs creation Anton Mikanovich
2023-02-13  7:56 ` Anton Mikanovich [this message]
2023-02-13  7:56 ` [PATCH v2 3/4] meta: unify cross selection Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 4/4] ccache: separate cache based on cross compile Anton Mikanovich
2023-02-13  8:01 ` [PATCH v2 0/4] Fix ccache issues Anton Mikanovich
2023-03-27  5:27 ` Uladzimir Bely
2023-03-28 15:51   ` Moessbauer, Felix
2023-03-28 15:56     ` Uladzimir Bely
2023-03-29 12:43       ` Moessbauer, Felix
2023-03-30  7:37         ` Uladzimir Bely
2023-04-02 18:44         ` Baurzhan Ismagulov
2023-04-05 11:56           ` Moessbauer, Felix
2023-04-05 13:28             ` Baurzhan Ismagulov
2023-04-10  5:44               ` Moessbauer, Felix

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=20230213075611.5694-3-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