- Issue created by @ananthakrishnan.kr
- ๐ฎ๐ณIndia kbk1992 Hyderabad
bharath-kondeti โ made their first commit to this issueโs fork.
- Merge request !37Issue-3456654: Addressing patch not applying issue on 10.3.x โ (Open) created by Unnamed author
- last update
6 days ago 32 pass - Status changed to Needs review
6 days ago 11:36am 24 June 2024 - ๐ฎ๐ณIndia abhiyanshu_rawat
@bharath-kondeti,
Have you checked if the patch is working correctly?
When I apply the patch manually by placing it in the root directory of the module and runninggit apply -v 2869592-disabled-update-module-63.patch
, it throws an error regarding a missing file or directory. The same patch may also encounter issues when applied via Composer. - ๐บ๐ธUnited States justcaldwell
Even after applying the patch from the MR, composer kept using the outdated version of the patch from โจ Disabled update module shouldn't produce a status report warning Needs work .
- Applying patches for drupal/core https://www.drupal.org/files/issues/2869592-remove-update-warning-7.patch (2869592 - Disabled update module shouldn't produce a status report warning)
This has previously been an issue for others but isn't consistent as described ๐ Update patch that no longer applies Needs review in ๐ Update patch that no longer applies Needs review .
If you don't have Update disabled anywhere (or don't care whether the message is a Warning rather than just Info), you can ignore the patch entirely by updating your root composer.json:
extra: { ... "patches-ignore": { "drupal/lightning_core": { "drupal/core": { "2869592 - Disabled update module shouldn't produce a status report warning": "https://www.drupal.org/files/issues/2869592-remove-update-warning-7.patch" } } }
- ๐ฎ๐ณIndia ananthakrishnan.kr
I am also getting the same error again after applying the patch from the MR.