All of lore.kernel.org
 help / color / mirror / Atom feed
From: TJ <git@iam.tj>
To: git@vger.kernel.org
Subject: [PATCH 0/1] Introduce new build variables INSTALL_MODE_EXECUTABLE and INSTALL_MODE_DATA.
Date: Thu, 31 Jan 2013 02:08:29 +0000	[thread overview]
Message-ID: <5109D21D.8010701@iam.tj> (raw)

During a build/install cycle of the current HEAD whilst attempting to identify the cause of a bug in
git version 1.8.0.3 whilst doing:

GIT_CURL_VERBOSE=1 git clone -v https://git01.codeplex.com/typescript

* GnuTLS recv error (-9): A TLS packet with unexpected length was received.
* Closing connection #0
error: RPC failed; result=56, HTTP code = 200

I hit a local install failure whilst installing to the prefix /usr/local/ where the $(INSTALL)
command reported a Permission Denied error.

This was due to the $(INSTALL) modes being 755/644 but the file-system modes being 775/664.
In this case ownership and permissions are:

$ ls -ald /usr/local
drwxrwxr-x 13 root adm 4096 Sep 26 04:16 /usr/local

Users belonging to the 'adm' group have permission to install local packages.

The fix I've implemented is to convert the hard-coded 755/644 modes to variables which can
be over-ridden on the make command-line if necessary.

                 reply	other threads:[~2013-01-31  2:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5109D21D.8010701@iam.tj \
    --to=git@iam.tj \
    --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.