Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Rasmus Villemoes <ravi@prevas.dk>
To: openembedded-core@lists.openembedded.org
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH] sstate.bbclass: apply proper umask when fetching from SSTATE_MIRROR
Date: Fri, 13 Jun 2025 13:43:56 +0200	[thread overview]
Message-ID: <87bjqr27er.fsf@prevas.dk> (raw)
In-Reply-To: <18466AB4BE83FB99.2470@lists.openembedded.org> (Rasmus Villemoes via lists openembedded org's message of "Fri, 6 Jun 2025 11:39:05 +0200")

On Fri, Jun 06 2025, "Rasmus Villemoes via lists.openembedded.org" <rasmus.villemoes=prevas.dk@lists.openembedded.org> wrote:

> From: Rasmus Villemoes <ravi@prevas.dk>
>
> Currently, files and directories created under ${SSTATE_DIR} when
> fetching from an sstate mirror are not created with group write,
> unlike when the sstate artifacts are generated locally. That's
> inconsistent, and problematic when the local sstate dir is shared
> among multiple users.
>
> Wrap the fetching in a bb.utils.umask() context manager, and for simplicity
> move the mkdir of SSTATE_DIR inside that.
>

Ping.



       reply	other threads:[~2025-06-13 11:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18466AB4BE83FB99.2470@lists.openembedded.org>
2025-06-13 11:43 ` Rasmus Villemoes [this message]
2025-06-06  9:39 [PATCH] sstate.bbclass: apply proper umask when fetching from SSTATE_MIRROR Rasmus Villemoes
2025-06-13 16:30 ` Richard Purdie
2025-06-13 19:42   ` [OE-core] " Ryan Eatmon
2025-06-15 21:17 ` Richard Purdie
2025-06-17  7:41   ` [OE-core] " Rasmus Villemoes
2025-06-25 13:54     ` Richard Purdie
2025-06-26  6:51       ` Rasmus Villemoes
2025-06-26 10:06         ` Richard Purdie
2025-06-26 12:50           ` Rasmus Villemoes
2025-06-26 14:05             ` Richard Purdie

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=87bjqr27er.fsf@prevas.dk \
    --to=ravi@prevas.dk \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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