Skip to content
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

Is patch provenance reported correctly? #561

Open
5 tasks done
cweagans opened this issue Mar 20, 2024 · 0 comments
Open
5 tasks done

Is patch provenance reported correctly? #561

cweagans opened this issue Mar 20, 2024 · 0 comments
Labels
bug Inconsistencies or issues which will cause a problem for users or implementors.

Comments

@cweagans
Copy link
Owner

Verification

  • I have updated Composer to the most recent stable release (composer self-update)
  • I have updated Composer Patches to the most recent stable release (composer update cweagans/composer-patches)
  • I am using one of the supported PHP versions (8.0+)
  • I have searched existing issues and discussions for my problem.
  • My problem is not addressed in the troubleshooting guide.

What were you trying to do (and why)?

Patches lock supplied in #559 doesn't seem to be reporting provenance correctly. Patches applied to drupal/ctools are reported as being from drupal/ctools, but the upstream repo is not doing that

What happened? What did you expect to happen?

a

Contents of composer.json

a

Contents of patches.lock.json

a

Full output of composer patches-doctor

a

Full output of relevant Composer command with the -vvv flag added

a
@cweagans cweagans added the bug Inconsistencies or issues which will cause a problem for users or implementors. label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Inconsistencies or issues which will cause a problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

1 participant