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

DT-743: Project creation, updates fail due to conflicting dependencies #3835

Closed
danepowell opened this issue Sep 3, 2019 · 2 comments
Closed
Labels
Bug Something isn't working

Comments

@danepowell
Copy link
Contributor

danepowell commented Sep 3, 2019

This is not a BLT bug per se, but an upstream problem with Drupal, webflo/drupal-core-require-dev, and Mink:

This makes it impossible to create new BLT projects, or to run composer install / update in some circumstances. Errors like this:

Problem 1
    - Installation request for webflo/drupal-core-require-dev 8.7.6 -> satisfiable by webflo/drupal-core-require-dev[8.7.6].
    - webflo/drupal-core-require-dev 8.7.6 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.

The best workaround I see is to add a branch alias as described here: minkphp/MinkSelenium2Driver#313 (comment)

I think end users should do this manually for now while we wait to see how the upstream issues are or aren't resolved, and then BLT can do it via an update hook if necessary.

Long term, we should consider removing webflo to decrease the risk of issues like this: #3838

@danepowell danepowell added the Bug Something isn't working label Sep 3, 2019
danepowell added a commit to danepowell/blt that referenced this issue Sep 3, 2019
@danepowell danepowell changed the title Cannot create new BLT project due to conflicting dependencies Project creation, updates fail due to conflicting dependencies Sep 3, 2019
@danepowell danepowell added this to the Backlog milestone Sep 4, 2019
@danepowell danepowell changed the title Project creation, updates fail due to conflicting dependencies DT-743: Project creation, updates fail due to conflicting dependencies Sep 4, 2019
@josephdpurcell
Copy link

If using Lightning 4, see #3840 for a recommendation on how to work around this issue.

@danepowell
Copy link
Contributor Author

This has been fixed upstream, any users that applied a workaround should remove it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants