Tried a clean install using composer as described here: https://www.drupal.org/docs/develop/using-composer/using-composer-to-ins...

composer create-project drupal-composer/drupal-project:8.x-dev www --no-interaction

Your requirements could not be resolved to an installable set of packages.

Problem 1
- webflo/drupal-core-require-dev 8.8.x-dev requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.x-dev requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.7 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.6 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.5 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.4 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.3 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.2 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.1 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.0-rc1 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.0-beta2 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.0-beta1 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.0-alpha2 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.0-alpha1 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- webflo/drupal-core-require-dev 8.7.0 requires behat/mink-selenium2-driver 1.3.x-dev -> no matching package found.
- Installation request for webflo/drupal-core-require-dev ^8.7.0 -> satisfiable by webflo/drupal-core-require-dev[8.7.0, 8.7.0-alpha1, 8.7.0-alpha2, 8.7.0-beta1, 8.7.0-beta2, 8.7.0-rc1, 8.7.1, 8.7.2, 8.7.3, 8.7.4, 8.7.5, 8.7.6, 8.7.7, 8.7.x-dev, 8.8.x-dev].

I believe is to fix is to remove the require-dev parameter from the composer.json.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

gisle created an issue. See original summary.

gisle’s picture

Status: Active » Needs review
FileSize
377 bytes

Uploaded patch.

cilefen’s picture

gisle’s picture

Yes, I see from #3078671: Pin behat/mink and behat/mink-selenium2-driver to use resolvable release that one of proposed workarounds is this:

Most projects do not actually need webflo/drupal-core-require-dev; you may simply remove it from your require-dev section and then run composer update.

This is what I propose here, so this probably should be closed as a duplicate. However, the status of the related issue is set to "Postponed" - so fixing this is not likely to happen any time soon.

This is the thing: When 8.7.7 was released yesterday, none of my sites could be upgraded. I spent a lot of hours trying to figure out why. If this had been a security release, that would have been quite catastrophic.

What I do not understand is this: Why was this not fixed before the release of 8.7.7 - or if you knew about it - mentioned in the release notes?

The carelessness and lack of QA that seems to be the hallmark of the composer-thingy from the start has made Drupal 8 maintenance a terrible nightmare.

cilefen’s picture

Status: Needs review » Closed (duplicate)

Hi @gisele,

This sort of thing cannot happen in most cases in security releases, because of they way security releases are built. I can get you documentation on that if interested.

Just for the record, the entire Drupal community—you and I, and everyone else—is permitted to test development branches before release. There isn't actually a dedicated team of testers for bugfix releases working in an office somewhere who decided not to test this. Now, the issue at hand is actually about drupal-project, which, yes, although it is the recommended installation on the drupal.org manual, is not really supported here. I think the actual issue is https://github.com/drupal-composer/drupal-project/issues/511. The patch in #2 cannot be committed to Drupal because it is for drupal-project.

Good idea on the release notes. I'll ping the team.

gisle’s picture

Hi @gisele,

It is gisle (a male name - "gisele" is the female variant).

This sort of thing cannot happen in most cases in security releases, because of they way security releases are built. I can get you documentation on that if interested.

I am more interested in practice. Drupal 8.5.6 was a security relase: https://www.drupal.org/SA-CORE-2018-005

And yes, webflo/drupal-core-require-dev was making that update a nightmare as well:
https://www.drupal.org/forum/support/upgrading-drupal/2018-08-02/cant-up...

Just for the record, the entire Drupal community—you and I, and everyone else—is permitted to test development branches before release. There isn't actually a dedicated team of testers for bugfix releases working in an office somewhere who decided not to test this.

I think it would not have made any difference if I had tested this. It is clear from #3078671: Pin behat/mink and behat/mink-selenium2-driver to use resolvable release that the problem was known by core maintainers before 8.7.7 was released. The team just didn't care.

Now, the issue at hand is actually about drupal-project, which, yes, although it is the recommended installation on the drupal.org manual, is not really supported here. I think the actual issue is https://github.com/drupal-composer/drupal-project/issues/511. The patch in #2 cannot be committed to Drupal because it is for drupal-project.

OK, I get it, now. I think that crucial piece of documentation should to be added to the documentation page.

cilefen’s picture

Sorry I mistyped the user id! Sorry.

#3078671: Pin behat/mink and behat/mink-selenium2-driver to use resolvable release was (rightly) marked as critical. I don't know why it didn't prevent release if it should have done. I have been too involved with my paid work to volunteer personal time towards release management so I haven't been able to help. I did not design Drupal 8, I've just been part of its "care and feeding". The Composer library situation has evolved since D8 launched, for sure.

drupal-projects's support is the same as that of Drush's. We get issues opened on drupal.org about Drush all the time. In a small fraction of cases, Drupal itself is actually to blame, and they can stay, but most belong on github.

Should drupal-project, or something like it, be part of Drupal itself and supported on drupal.org? Yes. There are efforts underway. As a community member I am not content with the amount of dependency management complaints we get in D8. I always try to help as they come up.

alar’s picture

Thank you for pointing out the fix @gisle. By deleting the three lines in composer.json I was able to return to the command line and run $composer update to complete my install of drupal 8.7.7
Phew! I almost was going to go back to drush ;)

gisle’s picture

I almost was going to go back to drush

You can't. Drupal 8 is deliberately being designed to maintainable with composer only.

Composer is probably a well-engineered dependency manager, but the current documentation available on Drupal.org is, IMNSHO, not great.

tjtj’s picture

webflo is not in my composer.json, and I still can't do the update...
Composer says:
Read for further common problems.
Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.

gisle’s picture

Status: Closed (duplicate) » Needs review

Reopening. #3078671: Pin behat/mink and behat/mink-selenium2-driver to use resolvable release is tagged with version 8.8.x-dev - intended for release in December. We can't wait until then. This need to be fixed in the 8.7 track.

This bug is currently preventing the current production branch (8.7) from being installed and updated with composer.

There exists workarounds, such as tweaking composer.json manually. But I think this is large enough impact to warrant it being fixed ASAP and released as a patch release 8.7.8.

gisle’s picture

Status: Needs review » Closed (cannot reproduce)

Tried to install from scratch this morning after extercising the thermonuclear option, using the exact same command as yesterday:

composer create-project drupal-composer/drupal-project:8.x-dev www --no-interaction

It now installed correctly. Looked in vendor/webflo/. The drupal-core-require-dev subdirectory was no longer there.

So I can no longer reproduce this.

Michelle’s picture

Thanks for posting this. I ran into the same issue and was at a loss. I did composer remove webflo/drupal-core-require-dev and that made a bunch of changes, which makes me nervous, but it fixed the problem and the site seems to be working ok.

smutek’s picture

Thanks as well, though I'm still stuck. I ran into this issue this afternoon after updating our BLT/Lightning based install to core 8.7.8

All appeared to be well and my local install was running as expected but my build failed when I tried to deploy to our dev server with:

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

Running composer remove webflo/drupal-core-require-dev resulted in webflo/drupal-core-require-dev is not required in your composer.json and has not been removed. Despite this, I can now run composer install successfully, and now I end up with a fatal error and a broken site:

Fatal error: require(): Failed opening required '/var/www/sitename/vendor/composer/../justinrainbow/json-schema/src/JsonSchema/Validator.php' (include_path='/var/www/sitename/vendor/pear/archive_tar:/var/www/sitename/vendor/pear/console_getopt:/var/www/sitename/vendor/pear/pear-core-minimal/src:/var/www/sitename/vendor/pear/pear_exception:.:/usr/share/php') in /var/www/sitename/vendor/symfony/class-loader/ApcClassLoader.php on line 112

I'm not sure, maybe my issue is with BLT, or maybe it's Lightning, but I'm posting here because it may be related to this error as well.

mbatterton’s picture

Thanks @smutek after removing 'webflo/drupal-core-require-dev' this fixed my install composer remove webflo/drupal-core-require-dev

mirsoft’s picture

Confirmed, experienced that issue on 2 projects after upgrading Drupal to 8.7.10. `composer remove webflo/drupal-core-require-dev` solved problem to me and just replaced `behat/mink-selenium2-driver` from `dev-master` to `1.3.x-dev` and nothing else. Which seems to me it doesn't have any negative implications, but who knows...

Botond’s picture

Hi All,

By trying to upgrade from 8.7.7 to 8.7.10 with

composer update drupal/core --with-dependencies

it just did not happen.

drupal site:status

still showed 8.7.7 version.

Checking

composer prohibits drupal/core:8.7.10

I've got the

webflo/drupal-core-require-dev 8.7.7 requires drupal/core (8.7.7)

message.

So, I updated that with composer too:

drupal site:status
composer prohibits drupal/core:8.7.10
composer update drupal/core "webflo/drupal-core-require-dev" --with-dependencies
drupal site:status
drupal debug:update
drupal update:execute
drupal cache:rebuild
drupal site:status

Now it shows 8.7.10 :)

Hope, it helps!

Regards

mirsoft’s picture

It seems it was fixed on the creator's side, because right now it already works also on projects where it didn't work before.

weynhamz’s picture

Had the same issue today, resolved with composer update webflo/drupal-core-require-dev --with-dependencies

shahankitb1982’s picture

#17 Works. Thanks a lot.

tce’s picture

Got this today when upgrading from 8.7.5 to 8.8.5. Simply doing the below worked:

composer update webflo/drupal-core-require-dev --with-dependencies

ldwyer’s picture

I also got this today when updating from 8.8.4 to 8.8.5 and #21 did the trick - thank you!

geneatwell’s picture

Webflo problem is back with 8.9.1 core update from 8.9.0.

pranav45’s picture

Thanks,#15 & #21 solves my problem when updating from drupal 8.7.10 to Drupal 8.9.2 faces some issue regarding webflow packages issue.Have follows two command as below:
`composer remove webflo/drupal-core-require-dev` & then `sudo composer update drupal/core --with-dependencies`