From: "Noé Rubinstein" <noe.rubinstein@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/python-web2py: fix permissions
Date: Wed, 4 Nov 2015 19:46:07 +0100 [thread overview]
Message-ID: <1446662767-15730-2-git-send-email-nrubinstein@aldebaran.com> (raw)
In-Reply-To: <1446662767-15730-1-git-send-email-nrubinstein@aldebaran.com>
The PYTHON_WEB2PY_PERMISSIONS table was using the user and group names
instead of the uid and gid, causing makedevs to retrieve the uid and gid
from the host system.
Signed-off-by: No? Rubinstein <nrubinstein@aldebaran.com>
---
package/python-web2py/python-web2py.mk | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/package/python-web2py/python-web2py.mk b/package/python-web2py/python-web2py.mk
index 313114a..db9ed8d 100644
--- a/package/python-web2py/python-web2py.mk
+++ b/package/python-web2py/python-web2py.mk
@@ -32,8 +32,16 @@ define PYTHON_WEB2PY_INSTALL_INIT_SYSTEMD
$(TARGET_DIR)/etc/systemd/system/multi-user.target.wants/web2py.service
endef
+# www-data user and group are used for web2py. Because these user and group
+# are already set by buildroot, it is not necessary to redefine them.
+# See system/skeleton/etc/passwd
+# username: www-data uid: 33
+# groupname: www-data gid: 33
+#
+# So, we just need to create the directories used by web2py with the right
+# ownership.
define PYTHON_WEB2PY_PERMISSIONS
- /var/www/web2py r 750 www-data www-data - - - - -
+ /var/www/web2py r 750 33 33 - - - - -
endef
$(eval $(generic-package))
--
2.1.4
next prev parent reply other threads:[~2015-11-04 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 18:46 [Buildroot] [PATCH 1/2] package/nginx: fix a typo Noé Rubinstein
2015-11-04 18:46 ` Noé Rubinstein [this message]
2015-11-04 20:49 ` Thomas Petazzoni
2015-11-04 22:51 ` Arnout Vandecappelle
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=1446662767-15730-2-git-send-email-nrubinstein@aldebaran.com \
--to=noe.rubinstein@gmail.com \
--cc=buildroot@busybox.net \
/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