From: Johannes Sixt <j6t@kdbg.org>
To: Ivan Uemlianin <ivan@llaisdy.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git pull works remotely but not locally
Date: Thu, 27 May 2010 21:53:54 +0200 [thread overview]
Message-ID: <201005272153.54239.j6t@kdbg.org> (raw)
In-Reply-To: <4BFE9172.9080209@llaisdy.com>
On Donnerstag, 27. Mai 2010, Ivan Uemlianin wrote:
> - I did configure with prefix=/opt
> - odd thing: nothing was installed into /opt: it all went into /root (I
> might have been root for the whole process, which I know is bad). I
> just cp'd everything over to /opt, and everything worked OK (until now).
My guess is:
- You built as root.
- I don't know what went wrong with the command that involved prefix=/opt.
- But when you finally build using 'make', it picked the default prefix, which
is /root when you are root.
- This hard-codes the libexec path to /root/libexec/git-core.
- Even after you copy the stuff to /opt, git looks in /root/libexec/...
- As a normal user you do not have access to /root, ergo, Permission denied.
Rebuild as normal user with
make prefix=/opt
and install as root with
make prefix=/opt install
(Yes, prefix must be given also for 'make install'.)
-- Hannes
next prev parent reply other threads:[~2010-05-27 19:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 13:35 git pull works remotely but not locally Ivan Uemlianin
2010-05-27 14:20 ` Ramkumar Ramachandra
2010-05-27 14:37 ` Ivan Uemlianin
2010-05-27 14:47 ` Sverre Rabbelier
2010-05-27 15:07 ` Ivan Uemlianin
2010-05-27 15:15 ` Jeff King
2010-05-27 15:21 ` Ivan Uemlianin
2010-05-27 15:28 ` Johannes Sixt
2010-05-27 15:37 ` Ivan Uemlianin
2010-05-27 15:38 ` Jeff King
2010-05-27 16:21 ` Ivan Uemlianin
2010-05-27 16:57 ` Ilari Liusvaara
2010-05-27 15:15 ` Ramkumar Ramachandra
2010-05-27 15:36 ` Ivan Uemlianin
2010-05-27 19:53 ` Johannes Sixt [this message]
2010-05-28 8:24 ` Ivan Uemlianin
2010-05-27 14:50 ` Ramkumar Ramachandra
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=201005272153.54239.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=ivan@llaisdy.com \
/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).