-
-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A patch with all new files & directories creates with a b/ prefix #199
Comments
Correction - the patch was committed by the maintainer, so -p1 doesn't apply but -p0 does by making the b/ directory |
Seeing this too. Believe it is this dependency, https://github.com/contentacms/contenta_jsonapi, which specific this patch, https://www.drupal.org/files/issues/drupal-n2788777-105.patch |
Same problem with https://www.drupal.org/files/issues/2570593-30.patch |
Could be related to #43 |
Dupe of #43. |
…er Patches struggles with patches that introduce new file. The solution is to upgrade to the 1.x-dev branch of Composer Patches and add some extra config to Composer.json See: - cweagans/composer-patches#199 - cweagans/composer-patches#43 - cweagans/composer-patches#101 - rwohleb/composer-patches#1
Seeing this with version 1.6.4
I have a path for a contrib module:
Config schema #2918157
Source: https://www.drupal.org/files/issues/entity-reference-uuid-schema.patch
when this patch is applied the files end up nested an extra level in a b/ subdirectory.
Possibly this is because all the files and directories are new, so the patch can apply while creating the directory and -p0?
The text was updated successfully, but these errors were encountered: