From: rroyce@textronsystems.com
To: "Ross Burton" <ross.burton@arm.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Do_package is changing permissions of files
Date: Thu, 22 May 2025 07:02:50 -0700 [thread overview]
Message-ID: <26223.1747922570855214978@lists.yoctoproject.org> (raw)
In-Reply-To: <DC492DE1-8638-494E-8DBB-E865BBF78924@arm.com>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
I'll see what i can do with reproducing it from walnascar package but i'm not a strong user of bitbake and yocto. I mostly work on recipes from an existing build structure.
The permissions changes on the source files normally isn't a problem, however, we have some source that have the exec bit set on them in the repo we are pulling from. One of the checks we perform involves checking with mercurial if anything in the source clone has changed from the version checked out and capturing that as part of the binary. It is probably not the "right" way to do it but it is what i'm working with for now. Changed permissions are seen by mercurial as a delta from the source clone.
Thanks for the headsup on the hard links. It looks like they are hardlinks from the source in WORKDIR/package to S. I don't need that source package for my use case and it is missing key files we need to be a real source rpm anyway. Can I disable the creation of it?
[-- Attachment #2: Type: text/html, Size: 1019 bytes --]
next prev parent reply other threads:[~2025-05-22 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 10:31 Do_package is changing permissions of files rroyce
2025-05-22 10:45 ` [yocto] " Alexander Kanavin
2025-05-22 13:02 ` rroyce
2025-05-22 13:19 ` Alexander Kanavin
2025-05-22 13:37 ` Ross Burton
2025-05-22 14:02 ` rroyce [this message]
2025-05-22 14:16 ` Ross Burton
2025-05-22 20:00 ` rroyce
2025-05-22 13:30 ` Ross Burton
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=26223.1747922570855214978@lists.yoctoproject.org \
--to=rroyce@textronsystems.com \
--cc=ross.burton@arm.com \
--cc=yocto@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.