From: "Jacob Kroon" <jacob.kroon@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sstate: Preserve permissions when extracting tar archive
Date: Sun, 16 Jan 2022 23:28:11 -0800 [thread overview]
Message-ID: <28618.1642404491183454308@lists.openembedded.org> (raw)
In-Reply-To: <20220114074138.51861-1-jacob.kroon@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Although this is now fixed in master, I was wondering why this doesn't seem to be a problem in dunfell.
In dunfell, sstate packages are unpacked with "tar -xvzf", no -p flag, but still my buildhistory doesn't show any noise when doing:
bitbake -c cleansstate shadow-native && bitbake shadow-native && bitbake -c clean shadow-native && bitbake shadow-native
After dunfell was the switch to tar+zstd, but I don't understand why that would change the extracted permissions.
If anyone has got a clue, i'd be interested to know why.
Jacob
(testing the message reply function from the archived mailing list)
[-- Attachment #2: Type: text/html, Size: 681 bytes --]
next prev parent reply other threads:[~2022-01-17 7:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 7:41 [PATCH] sstate: Preserve permissions when extracting tar archive Jacob Kroon
2022-01-17 7:28 ` Jacob Kroon [this message]
2022-01-17 8:40 ` [OE-core] " Richard Purdie
2022-01-17 8:51 ` Jacob Kroon
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=28618.1642404491183454308@lists.openembedded.org \
--to=jacob.kroon@gmail.com \
--cc=openembedded-core@lists.openembedded.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