public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/e2fsprogs/files/, sys-fs/e2fsprogs/
Date: Thu, 17 Sep 2015 18:33:47 +0000 (UTC)	[thread overview]
Message-ID: <1442514821.ff98e2caac4f8e53b51b602de9d9be06782622e6.vapier@gentoo> (raw)

commit:     ff98e2caac4f8e53b51b602de9d9be06782622e6
Author:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Thu Sep 17 18:33:20 2015 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Thu Sep 17 18:33:41 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff98e2ca

sys-fs/e2fsprogs: workaround buggy NFS when building manpages #550986

 sys-fs/e2fsprogs/e2fsprogs-1.42.13.ebuild          |  1 +
 .../files/e2fsprogs-1.42.13-subst-perms.patch      | 31 ++++++++++++++++++++++
 2 files changed, 32 insertions(+)

diff --git a/sys-fs/e2fsprogs/e2fsprogs-1.42.13.ebuild b/sys-fs/e2fsprogs/e2fsprogs-1.42.13.ebuild
index cb426fc..64b04bd 100644
--- a/sys-fs/e2fsprogs/e2fsprogs-1.42.13.ebuild
+++ b/sys-fs/e2fsprogs/e2fsprogs-1.42.13.ebuild
@@ -38,6 +38,7 @@ src_prepare() {
 		epatch "${WORKDIR}"/${PN}-1.42.9-mint-r1.patch
 	fi
 	epatch "${FILESDIR}"/${PN}-1.42.13-fix-build-cflags.patch #516854
+	epatch "${FILESDIR}"/${PN}-1.42.13-subst-perms.patch #550986
 
 	# blargh ... trick e2fsprogs into using e2fsprogs-libs
 	rm -rf doc

diff --git a/sys-fs/e2fsprogs/files/e2fsprogs-1.42.13-subst-perms.patch b/sys-fs/e2fsprogs/files/e2fsprogs-1.42.13-subst-perms.patch
new file mode 100644
index 0000000..2162f03
--- /dev/null
+++ b/sys-fs/e2fsprogs/files/e2fsprogs-1.42.13-subst-perms.patch
@@ -0,0 +1,31 @@
+From 0930fcd65ec8f135c90f673eab2a7a196103537d Mon Sep 17 00:00:00 2001
+From: Mike Frysinger <vapier@gentoo.org>
+Date: Thu, 17 Sep 2015 14:18:16 -0400
+Subject: [PATCH e2fsprogs] subst: use 0644 perms
+
+When running on NFS, opening files with 0444 perms for writing can
+sometimes fail.  Since there's no real reason for these files to be
+read-only, give the owner write permission.
+
+URL: https://bugs.gentoo.org/550986
+Signed-off-by: Mike Frysinger <vapier@gentoo.org>
+---
+ util/subst.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/util/subst.c b/util/subst.c
+index f36adb4..e4004c9 100644
+--- a/util/subst.c
++++ b/util/subst.c
+@@ -370,7 +370,7 @@ int main(int argc, char **argv)
+ 		}
+ 		strcpy(newfn, outfn);
+ 		strcat(newfn, ".new");
+-		fd = open(newfn, O_CREAT|O_TRUNC|O_RDWR, 0444);
++		fd = open(newfn, O_CREAT|O_TRUNC|O_RDWR, 0644);
+ 		if (fd < 0) {
+ 			perror(newfn);
+ 			exit(1);
+-- 
+2.5.1
+


             reply	other threads:[~2015-09-17 18:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 18:33 Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-29  0:45 [gentoo-commits] repo/gentoo:master commit in: sys-fs/e2fsprogs/files/, sys-fs/e2fsprogs/ Mike Frysinger
2018-01-07 17:08 Mike Gilbert
2018-05-16  8:56 Lars Wendler
2021-01-30 10:57 Lars Wendler
2023-04-25 19:59 Mike Gilbert
2025-01-22  7:10 Sam James

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=1442514821.ff98e2caac4f8e53b51b602de9d9be06782622e6.vapier@gentoo \
    --to=vapier@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox