Webflo and Behat problem prevent patches through Composer

I am trying to install a patch for the SMTP module on a Drupal 8.8.4 Vagrant Dev instance.

Attempting to do this fails with the following error:

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

  Problem 1
    - webflo/drupal-core-require-dev 8.8.4 requires behat/mink 1.7.x-dev -> no matching package found.
    - webflo/drupal-core-require-dev 8.8.4 requires behat/mink 1.7.x-dev -> no matching package found.
    - Installation request for webflo/drupal-core-require-dev 8.8.4 -> satisfiable by webflo/drupal-core-require-dev(8.8.4).

I have no need to behat / mink at all. This bug seems to be completely unrelated to SMTP and I have never seen it in other updates.

I understand that behat / mink 1.7 doesn't exist, but there is a 1.8 version. However, when I try to install it, I get the following:

  Problem 1
    - Installation request for webflo/drupal-core-require-dev (locked at 8.8.4, required as ^8.6.0) -> satisfiable by webflo/drupal-core-require-dev(8.8.4).
    - Can only install one of: behat/mink(1.7.x-dev, 1.8.x-dev).
    - Can only install one of: behat/mink(1.8.x-dev, 1.7.x-dev).
    - Can only install one of: behat/mink(1.7.x-dev, 1.8.x-dev).
    - Conclusion: install behat/mink 1.7.x-dev
    - Installation request for behat/mink 1.8.x-dev -> satisfiable by behat/mink(1.8.x-dev).

I feel like I've tried every possible version of 1.8: 1.8, 1.8.0, 1.8.x-dev. Regardless of which version I ask for Composer, every time I try to install 1.7, the installation of behat / mink is not allowed.

How can I fix it? I need it at all webflo/drupal-core-require-dev? I'm still not quite sure what it's doing.

Version control – problem with Drupal 7 Composer dependencies

When trying to install a juicebox that requires libraries, the dependencies do not result in a working configuration. This is because Juicebox defines a version requirement in the .info file that is not translated correctly into the corresponding Composer restriction.

Juicebox defines it dependencies as follows:

core = 7.x
dependencies() = image
dependencies() = libraries (>1.0)

This means that any version of libraries higher than 1.0 would work (i.e. 1.1, 2.0).

The following versions are installed when installing libraries and Juicebox with Composer:

"name": "drupal/juicebox",
"version": "dev-2.x",

"name": "drupal/libraries",
"version": "dev-1.x",

However, this does not correspond to the actual requirements in Drupal:

Enter the image description here

If you try to manually install the correct version of the libraries:

"drupal/juicebox": "^2.1",
"drupal/libraries": "^2.0",

it doesn't work and that composer update Outputs:

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

  Problem 1
    - Conclusion: remove drupal/juicebox 2.1.0
    - Conclusion: don't install drupal/juicebox 2.1.0
    - Conclusion: don't install drupal/libraries 2.5.0
    - Conclusion: don't install drupal/libraries 2.4.0
    - Conclusion: don't install drupal/libraries 2.3.0
    - Conclusion: don't install drupal/libraries 2.2.0
    - Conclusion: don't install drupal/libraries 2.1.0
    - Conclusion: don't install drupal/libraries 2.0.0
    - Conclusion: don't install drupal/libraries 2.0.0-alpha2
    - Installation request for drupal/juicebox ^2.1 -> satisfiable by drupal/juicebox(2.x-dev, 2.1.0).
    - Conclusion: don't install drupal/libraries 2.0.0-alpha1
    - drupal/juicebox 2.x-dev requires drupal/libraries ^1.1 -> satisfiable by drupal/libraries(1.x-dev).
    - Can only install one of: drupal/libraries(1.x-dev, 2.x-dev).
    - Can only install one of: drupal/libraries(2.x-dev, 1.x-dev).
    - Installation request for drupal/libraries ^2.0 -> satisfiable by drupal/libraries(2.x-dev, 2.5.0, 2.4.0, 2.3.0, 2.2.0, 2.1.0, 2.0.0, 2.0.0-alpha2, 2.0.0-alpha1).

This clearly shows the problem, namely that > by doing juicebox.info is translated into a composer restriction of ^1.1 it's not the same:

  • ^ in the composer everything means until the next major version
  • > in drupal .info Files means everything above

I didn't know where to post this issue since Drupal forums reported it as spam and I couldn't find a repository where this was implemented.

How to fix "UNRESOLVED DEPENDENCY" error after using Composer to install modules

I will pull my hair out if I stare at this problem longer. I've seen the similar questions and tried everything, but I can't fix this problem with module dependency versions.

I use Composer require drupal/ and I also tried to include certain versions, but that didn't work. I see that the current version number does not appear at the end of the error message, which asks me if the system knows which version is installed at all.

I also don't understand how many modules can ask for different versions of the same dependency. How can you possibly fix this:

The mistake

Composer – SatisPress – Keep upper / lower case letters in the name of the subject index?

I use SatisPress (https://github.com/cedaro/satispress) to make some premium plugins and themes available as composer packages because I want to use the Roots / Bedrock boilerplate.

Now I have the following problem:
The Divi topic (https://www.elegantthemes.com/gallery/divi/) uses a capital letter for the topic directory ("Divi", not "Divi"). Now when i use

composer require satispress/divi

It downloads the package and installs it in the correct directory. The topic is displayed and can be used.

However, the topic directory is now only in lower case letters ("divi", not "Divi"), which breaks down subordinate topics based on Divi.

What I found:

  • The behavior occurs both on the bedrock and in an empty directory
  • The zip files for packages created by SatisPress have the correct capitalization in the ZIP name and also in the contained files

While it should be possible to change the entry of the subtopic template to lower case only, this could be problematic if (for whatever reason) the main topic is installed in a "normal" way, now contains upper case letters again and the Site is damaged.

In order to:
Is there any way to change the behavior of SatisPress or Composer to take capital letters into account names?

The composer behaves differently at home and when hosting

One of my websites doesn't update properly with Composer. I manually inserted the new 8.8.4 core into the web and then:

[~ / www] # rm -rf manufacturer composer.lock [~ / www] # composer update –no-dev
– with dependencies
1/2: http://repo.packagist.org/p/provider-latest$62ccd99f861def4651d7187b8892e7ab1e12003d285d1817c6aa66796e035b1e.json
2/2: http://repo.packagist.org/p/provider-2020-01$261d358a81566da6ca3f23ccf0659f42c20962c69646d22663fe5c0dc4384eab.json

Done: Success: 2, Skipped: 0, Failure: 0, Total: 2

DrupalProject composer ScriptHandler :: checkComposerVersion Load Composer repositories with package information Update dependencies
[~ / www] # composer install –no-dev
DrupalProject composer ScriptHandler :: checkComposerVersion Load Composer repositories with package information Update dependencies

[~ / www] # ls cgi-bin / composer.json dr @ drush / robots.txt
scripts / vendor.old / web /

However, the new provider and composer.lock are not created. I don't see the highlighted lines on any of my other websites. What is wrong?

composer.json

Composer is working properly with this site at home and I have transferred the entire public_html directory to my provider, but Composer does not update there as shown above.

php – Composer error when running dumpautoload

I am using Laravel 5.7 and when I execute the command:

composer dumpautoload -o

I get the following composer mistake

[RuntimeException]
The file at "/vendor/phpdocumentor/reflection-common/src/Location.php" could not be parsed as PHP. It may be binary or corrupt

I tried to delete the folder and carry out the update. I also deleted the entire folder / provider and cleared the cache of Laravel and also the composer, but nothing happened.

I appreciate everyone's help

Error installing Magento Composer

(UnexpectedValueException)
  The checksum verification of the file failed (downloaded from https://repo.
  magento.com/archives/magento/google-shopping-ads/magento-google-shopping-ad
  s-3.0.1.0.zip)

Everything went smoothly until I got this error and cannot install Composer

Autoload error
Vendor autoload is not found. Please run 'composer install' under application root directory.

drush – Is it possible to update / remove / install 1 package with Composer without updating everything?

I have seen some posts responding to it saying that "Composer Require Package" or "Composer Update Package" will do this. But absolutely everything I do with Composer tries to update everything listed in the "require" section of composer.json.

I thought maybe removing the required lines in composer.json would avoid this mess. The composer then removes these modules from my Docroot.

I just want to remove my broken (not sure why) version of drush on the server and replace it with a new one without updating the core or any Contrib modules.

Remove composer Drush / Drush – but removal fails and then tries to update everything

xxx: ~ / www / d8 $ composer remove drush / drush drush / drush is not required
in your composer.json and has not been removed

DrupalProject composer ScriptHandler :: checkComposerVersion The package "drush / drush" listed for the update is not installed. To ignore. Loading
Composer repositories with package information Update dependencies
(including require-dev) Your requirements could not be resolved
installable set of packages.

Every Composer command I try (rmeove, update, require) seems to want to update everything. Then it fails due to dependency conflicts (which is good; since I don't want anything to be updated anyway).

7 – How do I set my own module dependency on a Composer package?

You can add dependencies to your module.

Navigate to the root folder of your module. Run composer init. If you come to the question Would you like to define your dependencies (require) interactively, Say yes. You can then declare any Composer libraries that your module depends on.

You can also create one manually composer.json File that looks something like this:

{
    "name": "uniquenamespace/packagename",
    "description": "This module does some stuff",
    "type": "drupal-module",
    "authors": (
        {
            "name": "Some Guy",
            "homepage": "https://www.example.com/some_guy",
            "role": "Maintainer"
        }
    ),
    "require": {
        "somevendor/somepackage": "^1.9"
    },
    "license": "    GPL-2.0-or-later"
}

Run composer validate to check if your composer.json File is valid.