Breaks with Git 2.14.0 #148

joergLin · 2017-08-08T17:13:18Z

Using Git 2.14.0 breaks appying Patches (Alpine Edge, Composer 1.5). Latest Working Version is 2.13.4.

Applying patches for drupal/core
    https://www.drupal.org/files/issues/2551373-35.patch (...)
cd 'web/core' && git --git-dir=. apply --check '-p1' '/tmp/5989b7ae422cc.patch'
warning: unable to access 'config': Is a directory
warning: unable to access 'config': Is a directory
fatal: unknown error occurred while reading the configuration files

cd 'web/core' && git --git-dir=. apply --check '-p0' '/tmp/5989b7ae422cc.patch'
warning: unable to access 'config': Is a directory

warning: unable to access 'config': Is a directory
fatal: unknown error occurred while reading the configuration files

cd 'web/core' && git --git-dir=. apply --check '-p2' '/tmp/5989b7ae422cc.patch'
warning: unable to access 'config': Is a directory
warning: unable to access 'config': Is a directory
fatal: unknown error occurred while reading the configuration files

patch '-p1' --no-backup-if-mismatch -d 'web/core' < '/tmp/5989b7ae422cc.patch'
patch: unrecognized option: no-backup-if-mismatch

BusyBox v1.25.1 (2016-10-26 16:15:20 GMT) multi-call binary.

Usage: patch [OPTIONS] [ORIGFILE [PATCHFILE]]

	-p,--strip N		Strip N leading components from file names
	-i,--input DIFF		Read DIFF instead of stdin
	-R,--reverse		Reverse patch
	-N,--forward		Ignore already applied patches
	-E,--remove-empty-files	Remove output files if they become empty

patch '-p0' --no-backup-if-mismatch -d 'web/core' < '/tmp/5989b7ae422cc.patch'
patch: unrecognized option: no-backup-if-mismatch

BusyBox v1.25.1 (2016-10-26 16:15:20 GMT) multi-call binary.

Usage: patch [OPTIONS] [ORIGFILE [PATCHFILE]]

	-p,--strip N		Strip N leading components from file names
	-i,--input DIFF		Read DIFF instead of stdin
	-R,--reverse		Reverse patch
	-N,--forward		Ignore already applied patches
	-E,--remove-empty-files	Remove output files if they become empty

patch '-p2' --no-backup-if-mismatch -d 'web/core' < '/tmp/5989b7ae422cc.patch'
patch: unrecognized option: no-backup-if-mismatch

BusyBox v1.25.1 (2016-10-26 16:15:20 GMT) multi-call binary.

Usage: patch [OPTIONS] [ORIGFILE [PATCHFILE]]

	-p,--strip N		Strip N leading components from file names
	-i,--input DIFF		Read DIFF instead of stdin
	-R,--reverse		Reverse patch
	-N,--forward		Ignore already applied patches
	-E,--remove-empty-files	Remove output files if they become empty

   Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/2551373-35.patch

In the Release Notes (https://github.com/git/git/blob/master/Documentation/RelNotes/2.14.0.txt) are changes to "gitdir" and "git apply", maybe its one of them?

cweagans · 2017-08-08T18:24:19Z

Oh boy. Thanks for reporting this. Really not looking forward to debugging this. :/

git--

andypost · 2017-08-09T23:28:46Z

yep, there's changes in git https://lkml.org/lkml/2017/8/4/481

probably

Git now avoids blindly falling back to ".git" when the setup sequence said we are not in Git repository.

tstoeckler · 2017-09-06T02:49:03Z

Was also hitting this, see PR for something that fixes this on my system

RalfEisler · 2017-09-27T07:40:22Z

Having issues installing and updating Drupal Lightning on FreeBSD

composer update -vvv
Running 1.5.2 (2017-09-11 16:59:25) with PHP 7.1.9 on FreeBSD / 10.3-RELEASE-p20

- Applying patches for drupal/core
    https://www.drupal.org/files/issues/2652138-41.patch (2652138 - ImageFormatter does not support SVGs)
Downloading https://www.drupal.org/files/issues/2652138-41.patch
cd 'docroot/core' && git --git-dir=. apply --check '-p1' '/tmp//59ca7004e02cf.patch'
Executing command (CWD): cd 'docroot/core' && git --git-dir=. apply --check '-p1' '/tmp//59ca7004e02cf.patch'
warning: unable to access 'config': Is a directory
warning: unable to access 'config': Is a directory
fatal: unknown error occurred while reading the configuration files

timcosgrove · 2017-09-28T18:51:56Z

Just adding a voice, that I'm also seeing this. Issue posted in acquia/lightning, cross-posting here: https://github.com/acquia/lightning/issues/473

I've confirmed that it does not happen under git 2.13.3, but does happen under git 2.14.1.

timcosgrove · 2017-09-28T19:42:10Z

I can also confirm, anecdotally, that #152 fixes the issue I'm seeing.

danepowell · 2017-11-06T21:53:11Z

I'm also seeing these errors when running composer update -vvv, but the patches do seem to be applied correctly in the end, at least in my test cases.

Can anyone explain that discrepancy, and/or provide a clear case where these errors actually prevent a patch being applied?

This needs to be fixed regardless, but I want to understand the exact scope and severity of this bug.

RalfEisler · 2017-11-07T09:53:44Z

@danepowell

I am working with the Drupal Lightning distribution on a shared hosting provider. The actual Git-version is 2.15.0. I became aware of the problem with Git-version 2.14.3.

The problem is severe, because the projects are not maintainable on this server, which is important for small projects.

The Drupal Lightning projects are managed with Composer and the Drupal shell Drush. Composer patches are managed with cweagans/composer-patches.

Clean installations and updates fail since patches are not applied. However, I can download the patches and apply them manually.

Software:
"cweagans/composer-patches": "^1.6.0",
Drush Commandline Tool 9.0-dev-g809c7fc3 (global install)
Drush Commandline Tool 9.0.0-beta8 (local install in the project)
Composer version 1.5.2 2017-09-11 16:59:25
PHP 7.1.11 (cli) (built: Oct 30 2017 11:34:00) ( NTS )

installation-protocoll.txt

danepowell · 2017-11-07T15:33:49Z

I get the same error messages as you when running verbose composer commands, but in the end the patches do seem to be applied. I'm trying to understand why the patches are correctly applied for me but not for you (regardless of the error messages).

RalfEisler · 2017-11-07T21:06:01Z

On my installation, the patches are clearly not applied.
In the above installation, I download and apply the first patch:

$ cd docroot
$ wget https://www.drupal.org/files/issues/1356276-408--8.4.x.patch
$ patch -p1 < 1356276-408--8.4.x.patch

patching.txt

All I know is comping from this post:

#152

By the way:

The installation can be done with an other shared hosting provider and an old Git-version, without issues. The installations and updates run also on my local machines with older Git-versions.

danepowell · 2017-11-08T00:17:03Z

Okay I think I've figured out the discrepancy. This is an interplay between composer-patches, Git, and GNU patch.

composer-patches starts throwing errors for Git versions >= 2.14.0

However, depending on the version of GNU patch on your system, these errors may or may not actually be harmful. It appears that newer versions can recover more gracefully from this problem.

With Git 2.15.0 and Patch 2.5 (the default for Mac OS), I get errors and the patches fail to apply.

With Git 2.15.0 and Patch 2.7.5 (the default for Ubuntu), I get errors but the patches still successfully apply.

RalfEisler · 2017-11-08T09:43:21Z

uname -a

FreeBSD 10.3-RELEASE-p21 #13 r322349M: Thu Aug 10 09:47:17 UTC 2017

danepowell · 2017-11-08T18:24:21Z

See my new PR for this here, including an in-depth explanation of why patches were still applying in spite of the errors: #165

Also note that this PR reveals another bug, which is that git apply probably can't be used to apply patches in this context.

danepowell · 2017-11-15T16:40:20Z

n.b. if you need to update your Patch version on Mac OS: brew install gpatch and restart your session/shell

Fixes #148: Incompatible with Git 2.14+.

danepowell · 2017-11-30T18:01:45Z

This may have introduced a regression for older versions of Git :(

#174

pwolanin · 2017-12-07T03:08:04Z

Yes, this is causing patch install to fail on the git version from Ubuntu 16.04
git version 2.7.4

mortenson · 2017-12-07T16:09:02Z

Installing gpatch on OS X 10.12.5 didn't fix this for me, I had to upgrade to High Sierra (10.13.2).

grasmash · 2017-12-08T17:38:17Z

@pwolanin @mortenson Even when using composer-patches 1.6.4?

mortenson · 2017-12-08T17:44:44Z

@grasmash It looks like that released the day I made my comment, so I'm not sure we were on it at the time.

pwolanin · 2017-12-08T18:09:58Z

The 1.6.4 release seems to have fixed it.

RalfEisler · 2017-12-14T21:48:12Z

Unfortunately, my hosting provider will not update patch. So 1.6.4 does not fix the problem.

git version 2.15.1
patch 2.0-12u10 FreeBSD
"cweagans/composer-patches": "^1.6.4"

Error messages:
Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/1356276-408--8.4.3.patch
etc.

danepowell · 2017-12-15T00:13:43Z

@RalfEisler it's unlikely that this bug would produce that particular error. The bug related to patch version generally fails silently. Are you absolutely sure that the patch you are referencing applies cleanly outside of Composer?

RalfEisler · 2017-12-15T08:18:17Z

Are you absolutely sure that the patch you are referencing applies cleanly outside of Composer?

@danepowell -- I am failing to clean install or update Drupal Lightning projects in a specific context. Patches are not applied.

php --version
PHP 7.1.12 (cli) (built: Dec 11 2017 19:54:55) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies
    with Zend OPcache v7.1.12, Copyright (c) 1999-2017, by Zend Technologies

git version 2.15.1

patch 2.0-12u10 FreeBSD

Composer version 1.5.2 2017-09-11 16:59:25

Drupal Lightning version 2.2.5

"cweagans/composer-patches": "^1.6.4"

lightning-installation.txt

However, I could apply them manually:

wget https://www.drupal.org/files/issues/1356276-408--8.4.3.patch

patch -p1 < 1356276-408--8.4.3.patch

patch-install.txt

danepowell · 2017-12-15T18:50:05Z

Oh it's not just the one core patch, it's every patch not applying. Yeah that seems like a bug, but you should probably open a new issue.

tstoeckler added a commit to tstoeckler/composer-patches that referenced this issue Sep 6, 2017

Issue cweagans#148: Fix --git-dir usage

ec3d3f2

tstoeckler mentioned this issue Sep 6, 2017

Issue #148: Fix --git-dir usage #152

Closed

greylabel mentioned this issue Nov 6, 2017

Running blt setup fails acquia/blt#2251

Closed

cweagans closed this as completed in d759a72 Nov 22, 2017

cweagans added a commit that referenced this issue Nov 22, 2017

Merge pull request #165 from danepowell/issue-148

3466175

Fixes #148: Incompatible with Git 2.14+.

danepowell added a commit to danepowell/composer-patches that referenced this issue Nov 22, 2017

Fixes cweagans#148: Incompatible with Git 2.14+.

4909c4a

cweagans added a commit that referenced this issue Nov 22, 2017

Merge pull request #171 from danepowell/issue-148-1.x

730f0f6

Fixes #148: Incompatible with Git 2.14+.

danepowell mentioned this issue Nov 28, 2017

"b" and duplicate "core" folder appears after composer operations acquia/blt#2309

Closed

danepowell mentioned this issue Dec 15, 2017

Fixes #148: Incompatible with Git 2.14+. #165

Merged

ineffyble mentioned this issue Dec 18, 2017

Add 'patch' to apk add command (used by composer-patches) composer/docker#36

Closed

lukasz-zaroda mentioned this issue Jul 24, 2019

D7: Error about not being able to apply patch on composer install drupal-composer/drupal-project#498

Closed

mvorisek mentioned this issue Jan 8, 2020

Make git apply working in non-root-git directories #294

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Breaks with Git 2.14.0 #148

Breaks with Git 2.14.0 #148

joergLin commented Aug 8, 2017

cweagans commented Aug 8, 2017

andypost commented Aug 9, 2017

tstoeckler commented Sep 6, 2017

RalfEisler commented Sep 27, 2017

timcosgrove commented Sep 28, 2017 •

edited

Loading

timcosgrove commented Sep 28, 2017

danepowell commented Nov 6, 2017

RalfEisler commented Nov 7, 2017

danepowell commented Nov 7, 2017

RalfEisler commented Nov 7, 2017 •

edited

Loading

danepowell commented Nov 8, 2017 •

edited

Loading

RalfEisler commented Nov 8, 2017 •

edited

Loading

danepowell commented Nov 8, 2017

danepowell commented Nov 15, 2017 •

edited

Loading

danepowell commented Nov 30, 2017

pwolanin commented Dec 7, 2017

mortenson commented Dec 7, 2017

grasmash commented Dec 8, 2017

mortenson commented Dec 8, 2017

pwolanin commented Dec 8, 2017

RalfEisler commented Dec 14, 2017

danepowell commented Dec 15, 2017

RalfEisler commented Dec 15, 2017 •

edited

Loading

danepowell commented Dec 15, 2017

Breaks with Git 2.14.0 #148

Breaks with Git 2.14.0 #148

Comments

joergLin commented Aug 8, 2017

cweagans commented Aug 8, 2017

andypost commented Aug 9, 2017

tstoeckler commented Sep 6, 2017

RalfEisler commented Sep 27, 2017

timcosgrove commented Sep 28, 2017 • edited Loading

timcosgrove commented Sep 28, 2017

danepowell commented Nov 6, 2017

RalfEisler commented Nov 7, 2017

danepowell commented Nov 7, 2017

RalfEisler commented Nov 7, 2017 • edited Loading

danepowell commented Nov 8, 2017 • edited Loading

RalfEisler commented Nov 8, 2017 • edited Loading

danepowell commented Nov 8, 2017

danepowell commented Nov 15, 2017 • edited Loading

danepowell commented Nov 30, 2017

pwolanin commented Dec 7, 2017

mortenson commented Dec 7, 2017

grasmash commented Dec 8, 2017

mortenson commented Dec 8, 2017

pwolanin commented Dec 8, 2017

RalfEisler commented Dec 14, 2017

danepowell commented Dec 15, 2017

RalfEisler commented Dec 15, 2017 • edited Loading

danepowell commented Dec 15, 2017

timcosgrove commented Sep 28, 2017 •

edited

Loading

RalfEisler commented Nov 7, 2017 •

edited

Loading

danepowell commented Nov 8, 2017 •

edited

Loading

RalfEisler commented Nov 8, 2017 •

edited

Loading

danepowell commented Nov 15, 2017 •

edited

Loading

RalfEisler commented Dec 15, 2017 •

edited

Loading