From: Mario Domenech Goulart <mario@ossystems.com.br>
To: openembedded-core@lists.openembedded.org
Subject: Ownership issue in package contents
Date: Fri, 27 Mar 2015 17:31:55 +0000 [thread overview]
Message-ID: <87d23uibxw.fsf@email.parenteses.org> (raw)
Hi,
I'm observing an issue with directory ownership in package
contents. Not sure if I'm overlooking something really basic or
if I hit a bug.
Here's a minimal recipe to illustrate the problem:
$ cat foo.bb
LICENSE = "CLOSED"
inherit useradd
USERADD_PACKAGES = "${PN}"
USERADD_PARAM_${PN} = "foo"
do_install() {
install -d -m 755 ${D}${libdir}/foo
touch ${D}${libdir}/foo/bar
chown -R foo:foo ${D}${libdir}/foo
}
Here's the package content:
$ dpkg -c foo_1.0-r0.0_cortexa9hf-vfp-neon.ipk
drwxrwxrwx root/root 0 2015-03-27 13:37 ./
drwxr-xr-x root/root 0 2015-03-27 13:37 ./usr/
drwxr-xr-x root/root 0 2015-03-27 13:37 ./usr/lib/
drwxr-xr-x root/root 0 2015-03-27 13:37 ./usr/lib/foo/
-rw-r--r-- foo/foo 0 2015-03-27 13:37 ./usr/lib/foo/bar
Note that, although I run "chown -R foo:foo ${D}${libdir}/foo" in
the recipe, ./usr/lib/foo/ in the package is owned by root.
However, its content has the right ownership.
I also generated and checked the rpm package and observed the
same issue.
Best wishes.
Mario
--
http://www.ossystems.com.br
next reply other threads:[~2015-03-27 17:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 17:31 Mario Domenech Goulart [this message]
2015-03-27 17:43 ` Ownership issue in package contents Otavio Salvador
2015-03-31 13:50 ` Burton, Ross
2015-03-31 17:20 ` Mario Domenech Goulart
2015-03-31 18:23 ` Mark Hatle
2015-03-31 20:12 ` Burton, Ross
2015-03-31 20:18 ` Otavio Salvador
2015-03-31 20:33 ` Mario Domenech Goulart
2015-03-31 20:51 ` Mark Hatle
2015-03-31 21:01 ` Mario Domenech Goulart
2015-03-31 21:09 ` Mark Hatle
2015-03-31 21:21 ` Mario Domenech Goulart
2015-03-31 21:47 ` Mark Hatle
2015-04-06 12:59 ` Mario Domenech Goulart
2015-04-06 14:53 ` Mark Hatle
2015-04-06 14:57 ` Otavio Salvador
2015-04-06 16:49 ` Mark Hatle
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=87d23uibxw.fsf@email.parenteses.org \
--to=mario@ossystems.com.br \
--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 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.