From: Ben Hutchings <ben@decadent.org.uk>
To: linux-kernel@vger.kernel.org
Cc: maximilian attems <max@stro.at>, Frans Pop <elendil@planet.nl>
Subject: [PATCH] builddeb: Fix packaged file permissions
Date: Thu, 03 Sep 2009 23:00:31 +0100 [thread overview]
Message-ID: <1252015231.3475.9.camel@localhost> (raw)
The packaged files' permissions are implicitly dependent on the
current umask. Not only can this result in surprisingly restrictive
permissions, but dpkg-deb will fail if the DEBIAN directory does not
have permissions 755 or 775. Therefore, set the umask to 022 before
building a package.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
---
scripts/package/builddeb | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index 8b357b0..24cfd80 100644
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -12,6 +12,8 @@
set -e
+umask 022
+
create_package() {
local pname="$1" pdir="$2"
--
1.6.3.3
next reply other threads:[~2009-09-03 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 22:00 Ben Hutchings [this message]
2009-09-04 18:55 ` [PATCH] builddeb: Fix packaged file permissions Frans Pop
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=1252015231.3475.9.camel@localhost \
--to=ben@decadent.org.uk \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
/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