From: "Anatol Pomozov" <anatol.pomozov@gmail.com>
To: git@vger.kernel.org
Subject: Commit templates are not readable after 'make install'
Date: Tue, 9 Sep 2008 08:41:38 -0700 [thread overview]
Message-ID: <3665a1a00809090841l5d34f57ax8ad99d99a28bd494@mail.gmail.com> (raw)
In-Reply-To: <3665a1a00809090835g2a8ea4aas6cfa2ebc922f12b2@mail.gmail.com>
Hi,
I build git from sources and I have one small permissions issue that
(I think) should be fixed.
So I build it as described in INSTALL file
make prefix=/usr all
sudo make prefix=/usr install
Everything goes fine here and we have a new version of git installed
$ git --version
git version 1.6.0.1.285.g1070
But when I want to create a new repo, I have a fatal problem
$ git init
fatal: cannot copy /usr/share/git-core/templates/
hooks/applypatch-msg.sample to
/personal/sources/opensource/1/.git/hooks/applypatch-msg.sample
Because of the template files are readable only for root
$ ls -l /usr/share/git-core/templates/hooks/
total 44
-rwxr-x--- 1 root root 452 2008-08-29 11:04 applypatch-msg.sample
-rwxr-x--- 1 root root 894 2008-08-29 11:04 commit-msg.sample
-rwxr-x--- 1 root root 160 2008-08-29 11:04 post-commit.sample
-rwxr-x--- 1 root root 553 2008-08-29 11:04 post-receive.sample
I could fix the problem by running
$ sudo chmod a+r -R /usr/share/git-core/templates
But I think it should do 'make' when it installs git-core, isnt it?
--
anatol
next parent reply other threads:[~2008-09-09 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3665a1a00809090835g2a8ea4aas6cfa2ebc922f12b2@mail.gmail.com>
2008-09-09 15:41 ` Anatol Pomozov [this message]
2008-09-09 19:02 Commit templates are not readable after 'make install' Anatol Pomozov
2008-09-09 19:19 ` Junio C Hamano
2008-09-09 20:18 ` Junio C Hamano
2008-09-10 6:34 ` Johannes Sixt
2008-09-10 7:23 ` Junio C Hamano
2008-09-11 17:21 ` Anatol Pomozov
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=3665a1a00809090841l5d34f57ax8ad99d99a28bd494@mail.gmail.com \
--to=anatol.pomozov@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).