From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.com
Subject: [ptxdist] strange permission behavior
Date: Tue, 19 Feb 2019 19:59:39 -0500 [thread overview]
Message-ID: <CAMwGMjzshPAxULXyD78SLLp_Dk=PZ48pbPKYis4Stdh3Uv9_rg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 876 bytes --]
I've got a strange permission problem when I build on our build server that
was recently updated from Ubuntu-14.04 to Ubuntu-16.04.
On our Ubuntu-16.04 server, on most of the platform/packages/
subdirectories the packages are getting created with other having no
permissions at all:
rootfs/platform-ec1c/packages$ tree -d -L 1 -p
.
├── [drwxr-x---] attr-2.4.47
├── [drwxr-x---] avahi-0.7
├── [drwxr-x---] bash-4.3.30
├── [drwxr-x---] boost_1_67_0
├── [drwxr-x---] busybox-1.29.3
├── [drwxr-x---] coreutils-8.29
...
This results in all files contained within those directories to also have
no perms for other, and get installed on my target in the same way. This in
turn then causes permission problems to occur.
I'm at a loss as to what to look for to resolve this problem.
Suggestions?
Regards,
-Jon
[-- Attachment #1.2: Type: text/html, Size: 1151 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-02-20 0:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 0:59 Jon Ringle [this message]
2019-02-20 13:17 ` Ian Abbott
2019-02-20 13:22 ` Ian Abbott
2019-02-20 14:09 ` Jon Ringle
2019-02-20 14:42 ` Michael Olbrich
2019-02-20 15:10 ` Jon Ringle
2019-02-20 15:20 ` Michael Olbrich
2019-02-20 15:29 ` Jon Ringle
2019-02-20 15:43 ` Michael Olbrich
2019-02-21 13:47 ` Jon Ringle
2019-02-20 14:23 ` Michael Olbrich
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='CAMwGMjzshPAxULXyD78SLLp_Dk=PZ48pbPKYis4Stdh3Uv9_rg@mail.gmail.com' \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.com \
--cc=ptxdist@pengutronix.de \
/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