All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Sarajärvi Tony" <Tony.Sarajarvi@digia.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git --file doesn't override $HOME in version 1.8.1.2
Date: Tue, 09 Jul 2013 05:00:41 -0700	[thread overview]
Message-ID: <7vmwpwvt7a.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <C8A88C530F38AE47B22BDC434090CBB0ED26E0@IT-EXMB01-HKI.it.local> ("Sarajärvi Tony"'s message of "Tue, 9 Jul 2013 11:05:46 +0000")

Sarajärvi Tony <Tony.Sarajarvi@digia.com> writes:

> Using Ubuntu 13.04 with Git 1.8.1.2 I stumbled upon a problem using Puppet.
>
> In Puppet we launch Git with the command: '/usr/bin/git config --file /home/qt/.gitconfig --get "user.name" "Qt Continuous Integration System"'

Hmph.  What does this even mean?

    git config --get user.name "Qt CIS"

I have a feeling that the command will exit with an error status 1.

> However, puppet logs: "fatal: unable to access
> '/root/.config/git/config': Permission denied".
>
> Puppet is run as root, so HOME points to /root, but still -file
> should override the environment variable.

Probably.

> If the same command is run directly from terminal as root, it works as well.

I am not sure what you mean by "works as well".  It behaves
differently and does not fail the same way?

> With 1.8.3.2 the problem didn't reoccur.

That is probably due to b1c418e1 (Merge branch
'jn/config-ignore-inaccessible' into maint, 2013-06-09)

But it is puzzling.

The "error out upon an inaccessible configuration file in usual
places" check we had since v1.8.1.1 was meant to make sure that you
will not be missing a basic configuration before running any command
(including "git config" itself).  As "root", you shouldn't even have
triggered the "unable to access: Permission denined" in the first
place.  There is something else going on.

  parent reply	other threads:[~2013-07-09 12:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 11:05 Git --file doesn't override $HOME in version 1.8.1.2 Sarajärvi Tony
2013-07-09 11:49 ` Thomas Rast
2013-07-09 19:24   ` Jeff King
2013-07-09 12:00 ` Junio C Hamano [this message]
2013-07-09 12:12   ` Sarajärvi Tony

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=7vmwpwvt7a.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Tony.Sarajarvi@digia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.