Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I am not sure what is going wrong here, but it doesn't look good. I cannot update core with composer, it is stating there is a broken package dependency.
$ composer-update
> DrupalProject\composer\ScriptHandler::checkComposerVersion
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- remove drupal/file_entity 2.x-dev|keep drupal/file_entity dev-2.x
- drupal/file_entity 2.x-dev requires drupal/core-file * -> no matching package found.
- drupal/file_entity dev-2.x requires drupal/core-file * -> no matching package found.
- Installation request for drupal/file_entity 2.x-dev -> satisfiable by drupal/file_entity[2.x-dev].
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
Comments
Comment #2
nicholas.alipaz CreditAttribution: nicholas.alipaz commentedI ended up removing file_entity from my composer.json and then manually adding this one module to my modules directory. Not the best solution overall but it got me past my issue.
It is strange that I can't have it in my composer.json any longer.
Comment #3
killua99 CreditAttribution: killua99 as a volunteer commentedI'm guessing the file_entity.info.yml is wrong plus the composer.json also has some extra lines.
The .info.yml file should be:
Also the composer.json should be:
If we compare to others info.yml and composer.json
The composer.json maybe is nothing wrong there. But the `require: { }` look useless there because the .info.yml is taking care of it.
Comment #4
Berdirhttps://github.com/drupal-media/file_entity/pull/17
Comment #5
killua99 CreditAttribution: killua99 as a volunteer commentedI'm wonder if we could build a new tag (when this issue is merged into mastet 8.x), so composer might be enable to get the new version on Drupal 8.2.
I don't want to put a tag into my composer file, but if you're thinking to add extra issues I can definitive handle this by commit hash.
Comment #7
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedCommitted. Thanks!