Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: openembedded-core@lists.openembedded.org
Subject: [master, jethro][PATCH 0/1] Make devtool handle read-only .git/hooks directories
Date: Wed, 27 Jan 2016 15:39:51 +0100	[thread overview]
Message-ID: <cover.1453905512.git.pkj@axis.com> (raw)

When running "devtool extract <recipe> <dir>", it failed for us if the
recipe contained any patches. This was due to devtools modification of
the commit-msg and applypatch-msg Git hooks.

We have a bit unusal setup where .git/hooks is a symbolic link to a
directory in /usr/share, which means that it is not writable by the
user. This of course caused devtool to fail when it tried to modify
the hooks.

The solution provided here temporarily moves away the .git/hooks
directory (or link) instead, which should be safe since the .git
directory should be writable.

We also need this applied to Jethro. Do I need to supply a separate
patch for that?

//Peter

The following changes since commit 3d2c0f5902cacf9d8544bf263b51ef0dd1a7218c:

  cmake: update to 3.4.2 (2016-01-26 22:49:40 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib pkj/devtool_hooks
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/devtool_hooks

Peter Kjellerstedt (1):
  lib/oe/patch: Make GitApplyTree._applypatch() support read-only
    .git/hooks

 meta/lib/oe/patch.py | 26 ++++++++++++--------------
 1 file changed, 12 insertions(+), 14 deletions(-)

-- 
2.1.0



             reply	other threads:[~2016-01-27 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 14:39 Peter Kjellerstedt [this message]
2016-01-27 14:39 ` [master, jethro][PATCH 1/1] lib/oe/patch: Make GitApplyTree._applypatch() support read-only .git/hooks Peter Kjellerstedt

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=cover.1453905512.git.pkj@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=openembedded-core@lists.openembedded.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