- Issue created by @kreatIL
- 🇺🇸United States dmudie
Same issue here. After composer update (composer require 'drupal/blazy:^2.15'), blazy.info.yml still showed "version: 8.x-2.x"
Curious as to why it left the 8.x version.I resolved by removing blazy module entirely then re-adding.
- 🇺🇸United States bcobin
Same here, but the message is slightly different:
Unresolved dependency Blazy (Version >= 2.14 required) Slick requires this module and version. Currently using Blazy version 2.x
I'm on Drupal 10.
When you say "removed," do you mean uninstall and reinstall? I just ran composer require 'drupal/blazy:^2.15' and got the following:
./composer.json has been updated Running composer update drupal/blazy Loading composer repositories with package information Info from https://repo.packagist.org: #StandWithUkraine Updating dependencies Lock file operations: 0 installs, 1 update, 0 removals - Upgrading drupal/blazy (dev-2.x 208c84c => 2.15.0) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 0 installs, 1 update, 0 removals - Syncing drupal/blazy (2.15.0) into cache - Upgrading drupal/blazy (dev-2.x 208c84c => 2.15.0): Checking out 8.x-2.15 from cache Generating autoload files 44 packages you are using are looking for funding. Use the `composer fund` command to find out more!
But system reports:
Machine name: blazy
Version: 8.x-2.xAny suggestions greatly appreciated!
- Status changed to Postponed: needs info
over 1 year ago 3:22am 26 May 2023 - 🇮🇩Indonesia gausarts
Thank you.
Mind providing more details for a repro and project docs:
- What is your entire
composer update
command line? - Paste the
require-dev
directive from your composer.json?
At slick.info.yml file:
#version: 8.x-2.x
Ignore this, only concerns the one without#
.At /admin/modules:
Version: 8.x-2.x
should be8.x-2.8
, etc.- Normally happens when you
git clone
. Usecomposer require drupal/slick:^2.0
instead. Composer will update it up to the latest versions within its constraints. Unless you want specific versions such as non-breaking versions. - Failing composer downloads due to connections, and it still reads your last git clone. Manually verify
/contribs/slick/slick.info.yml
file.
Just hints, take it with a grain of salts:
- Add parameter
-w
or-W
along with others to yourcomposer update
if not already. - Remove unneeded/ conflicting items from
require-dev
directive, if any - At worst, if all fails, remove or better rename composer.lock, and run
composer install
orcomposer update --no-install
(writing without downloading packages), and re-run yourcomposer update
with needed params. Be sure to remove unneededrequire-dev
items first, not all. - Run
drush updb
anddrush cr
, or use UI.
Please verify against official docs in case I missed things above, and always do this first at local or staging environments for safety and little speed.
If you resolved it, consider sharing your solutions to benefit others.
Let me know?
- What is your entire
- 🇩🇪Germany kreatIL
I solved it by:
composer remove drupal/slick_views./composer.json has been updated Running composer update drupal/slick_views Gathering patches for root package. Loading composer repositories with package information Updating dependencies Lock file operations: 0 installs, 0 updates, 3 removals - Removing drupal/blazy (2.15.0) - Removing drupal/slick (2.8.0) - Removing drupal/slick_views (2.6.0) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 0 installs, 0 updates, 3 removals - Removing drupal/slick_views (2.6.0) - Removing drupal/slick (2.8.0) - Removing drupal/blazy (2.15.0) Deleting web/modules/contrib/slick_views - deleted Deleting web/modules/contrib/slick - deleted Deleting web/modules/contrib/blazy - deleted
composer require drupal/slick_views
Using version ^2.6 for drupal/slick_views ./composer.json has been updated Running composer update drupal/slick_views Gathering patches for root package. Loading composer repositories with package information Updating dependencies Lock file operations: 3 installs, 0 updates, 0 removals - Locking drupal/blazy (2.15.0) - Locking drupal/slick (2.8.0) - Locking drupal/slick_views (2.6.0) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 3 installs, 0 updates, 0 removals - Downloading drupal/blazy (2.15.0) Gathering patches for root package. Gathering patches for dependencies. This might take a minute. - Installing drupal/blazy (2.15.0): Extracting archive - Installing drupal/slick (2.8.0): Extracting archive - Installing drupal/slick_views (2.6.0): Extracting archive
This makes absolutely no sense, but it helps.
- 🇺🇸United States bcobin
Below is my result from #4. Status: no change.
composer remove drupal/slick_views
./composer.json has been updated Running composer update drupal/slick_views Loading composer repositories with package information Updating dependencies Lock file operations: 0 installs, 0 updates, 1 removal - Removing drupal/slick_views (2.6.0) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 0 installs, 0 updates, 1 removal - Removing drupal/slick_views (2.6.0) Deleting /[site}/web/modules/contrib/slick_views - deleted Generating autoload files
composer require drupal/slick_views
Info from https://repo.packagist.org: #StandWithUkraine ./composer.json has been updated Running composer update drupal/slick_views Loading composer repositories with package information Updating dependencies Lock file operations: 1 install, 0 updates, 0 removals - Locking drupal/slick_views (2.6.0) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 1 install, 0 updates, 0 removals - Installing drupal/slick_views (2.6.0): Extracting archive Generating autoload files
- 🇮🇩Indonesia gausarts
Thank you.
Hm, #5 vs #6 had the same actions, but different results? This might explain unique problems per installs which should not happen under normal circumstances specific to the OP.
At least #5 did resolve, which is good, thanks.
I just updated two old sites with just
composer update -w -n
....etc, and saw no evils.I don't bother requiring one module. Perhaps that is another suspect? If so, be sure to specify the caret ^ and explicit 2.0, etc.
If no joy, see #4.
That was why I asked about the entire single line of your
composer update
...What are the other paramaters you put in there. If they are the same with me, but different results, we could narrow down to other specific stuffs mentioned in #4.
- 🇺🇸United States bcobin
Thanks for responding, gausarts - much appreciated!
What is your entire composer update command line?
Various for the session. Here are the relevant commands and results, in order:
composer update drupal/slick
Loading composer repositories with package information Updating dependencies Lock file operations: 0 installs, 1 update, 0 removals - Upgrading drupal/slick (2.7.0 => 2.8.0) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 0 installs, 1 update, 0 removals - Downloading drupal/slick (2.8.0) - Upgrading drupal/slick (2.7.0 => 2.8.0): Extracting archive Generating autoload files
composer update drupal/blazy -W
Loading composer repositories with package information Info from https://repo.packagist.org: #StandWithUkraine Updating dependencies Lock file operations: 0 installs, 2 updates, 0 removals - Upgrading guzzlehttp/guzzle (7.5.1 => 7.5.3) - Upgrading guzzlehttp/promises (1.5.2 => 1.5.3) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 0 installs, 2 updates, 0 removals - Downloading guzzlehttp/promises (1.5.3) - Downloading guzzlehttp/guzzle (7.5.3) - Upgrading guzzlehttp/promises (1.5.2 => 1.5.3): Extracting archive - Upgrading guzzlehttp/guzzle (7.5.1 => 7.5.3): Extracting archive Generating autoload files
See slick_views commands/results, above.
I just updated two old sites with just composer update -w -n ....etc, and saw no evils.
Not familiar with the commands - I'm just trying to get stuff to work!
Site still reports (five times):
Unresolved dependency
Blazy (Version >= 2.14 required)
Slick requires this module and version. Currently using Blazy version 2.xThanks again for taking the time - I really appreciate this...
- 🇩🇪Germany kreatIL
In my case: Drupal 9.5.9, PHP 8.1, Composer version 2. When I run
composer update
I don't use the -w -n options, because I haven't any dev dependencies or scripts in my composer.json. - 🇮🇩Indonesia gausarts
@kreatil, thanks. Yes, should be fine under normal circumstances. However there are reports similar to @bcobin concerning failing updates:
https://www.drupal.org/docs/updating-drupal/updating-drupal-core-via-com... →@bcobin, try the flag
-w
(--with-dependencies).More detailed steps
:
https://www.drupal.org/docs/updating-drupal/updating-modules-and-themes-... →Try:
composer update drupal/slick --with-all-dependencies
If that doesn't work, please detail;
- Your Drupal, PHP, and Composer versions? If still Composer 1, please upgrade to 2.
- Is it upgrading from Slick 1.x to 2.x? More steps are required, see the above link. Skip if just Slick 2.x minor version updates.
- Visit /admin/modules, and compare the new Slick versions, against the reports.
If you see the version at /admin/modules as expected, but reports say the opposite, and things work properly, it may not be your problem, likely core or composer issues as outlined above, not immediately synced. See the first link above in this comment.
If both admin pages are still outdated or out of sync, most likely your ends along with core and composer. You may want to do more troubleshootings if you like with the provided links. And back to #4.
The easiest is to update the entire site with
composer update -w -n
...etc. The ...etc may be just--prefer-dist
, but that all depends on your expected setups, that is why I left it out, see more:
https://getcomposer.org/doc/03-cli.md - 🇮🇩Indonesia gausarts
@bcobin, also try @dmudie at #2:
composer remove drupal/blazy composer require drupal/blazy:^2.0
The only difference is the module name, not slick_views, but blazy in your case.
At worst, remove all slick, slick_views, blazy, like @kreatIL, and then re-add.
As to why, it is likely composer.lock not being synced. Removing will likely force updating the lock file better than just update.
That is why I said at #4 to remove composer.lock, and regenerate for the worst scenarios.
- Status changed to Fixed
over 1 year ago 9:39am 27 May 2023 - 🇮🇩Indonesia gausarts
I could reproduce it:
- Drupal 9.5 - 10 with PHP8.2
Only if I git clone Blazy resulting in
version: 8.x-2.x
Once I use regular composer, things are OK.I could not reproduce it:
- Drupal 9.5, PHP8.1
- Drupal 9.5, PHP8.2
- Drupal 10, PHP8.2
when I use regular composer.
Solutions:
- Manually verify your
blazy.info.yml
file has this:
version: 8.x-2.15
with# version: 8.x-2.x
, notversion: 8.x-2.x
. If not check below. - If you are using contrib distros, try Drupal Standards profile installer. There was one that failed versioning, forgot.
- Plus the above removals.
Conclusions:
Nothing related to this module or Blazy.It is PHP8.2, or likely composer.lock not being updated.
Feel free to share your solutions. Thanks.
- 🇺🇸United States bcobin
Try: composer update drupal/slick --with-all-dependencies
Result:
Loading composer repositories with package information Info from https://repo.packagist.org: #StandWithUkraine Updating dependencies Nothing to modify in lock file Installing dependencies from lock file (including require-dev) Nothing to install, update or remove
Your Drupal, PHP, and Composer versions? If still Composer 1, please upgrade to 2.
Is it upgrading from Slick 1.x to 2.x? More steps are required, see the above link. Skip if just Slick 2.x minor version updates.
Visit /admin/modules, and compare the new Slick versions, against the reports.Drupal version: 10.0.9
PHP: 8.1.19
Composer version 2.5.1
Machine name: blazy Version: 8.x-2.xcomposer remove drupal/blazy
Result:
./composer.json has been updated Running composer update drupal/blazy Loading composer repositories with package information Info from https://repo.packagist.org: #StandWithUkraine Updating dependencies Nothing to modify in lock file Writing lock file Installing dependencies from lock file (including require-dev) Nothing to install, update or remove Generating autoload files
Command: composer require drupal/blazy:^2.0 drupal/slick:^2.0 drupal/slick_views:^2.0
Result:
./composer.json has been updated Running composer update drupal/blazy drupal/slick drupal/slick_views Loading composer repositories with package information Updating dependencies Nothing to modify in lock file Writing lock file Installing dependencies from lock file (including require-dev) Nothing to install, update or remove Generating autoload files
No change.
- 🇮🇩Indonesia gausarts
Hm, weird.
What is your Drupal profile installer?
Problems and solutions were already identified at #12 so this time it is likely your ends.
> Nothing change
In your case, I saw inconsistencies.Different commands always say the same thing:
Running composer update ...
Perhaps something wrong with your commands?
Or you pasted wrong messages?While it should say:
removing
anddownloading
, etc...Could you try again and screenshot it?
Aside from PHP8.2, PHP > 8.1 looks like having the same problem. No biggies here, already identified.
- 🇺🇸United States bcobin
Thank you for responding so quickly!
Here's how the site was installed:
composer create-project drupal/recommended-project:10.0.0 ""
composer update "drupal/core-*" --with-all-dependenciesBut...
On an unrelated issue, my host is currently having problems with the server node my sites are on and they need to migrate everything. They say it's best for me not to make any changes until we're on the new node - and I heartily agree. So I'll resume once everything's stable again - perhaps this evening or tomorrow morning. There's nothing more fun than dealing with stuff like this on a weekend... Gah! Thanks and until then...
- 🇮🇩Indonesia gausarts
> not to make any changes
Pretty much explained it. Your node must be in read mode, no write. That is why you see no changes :) - 🇺🇸United States bcobin
No - I don't think that's it - the advice was not to make any changes, but it was advisory only:
We would need another 5-6 Hours to do migration of your VPS as around 130 GB archive will be moved and unpacked on new location, It would be best if no changes are made in this time.
I'll get to the bottom of this, but it'll have to wait - thanks again!
- 🇺🇸United States bcobin
Site has been moved - end result is basically the same, though. Difference is with:
composer update drupal/slick --with-all-dependencies
Loading composer repositories with package information Info from https://repo.packagist.org: #StandWithUkraine Updating dependencies Lock file operations: 0 installs, 9 updates, 0 removals - Upgrading symfony/console (v6.2.10 => v6.2.11) - Upgrading symfony/dependency-injection (v6.2.10 => v6.2.11) - Upgrading symfony/error-handler (v6.2.10 => v6.2.11) - Upgrading symfony/http-foundation (v6.2.10 => v6.2.11) - Upgrading symfony/http-kernel (v6.2.10 => v6.2.11) - Upgrading symfony/process (v6.2.10 => v6.2.11) - Upgrading symfony/serializer (v6.2.10 => v6.2.11) - Upgrading symfony/validator (v6.2.10 => v6.2.11) - Upgrading symfony/var-dumper (v6.2.10 => v6.2.11) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 0 installs, 9 updates, 0 removals - Downloading symfony/console (v6.2.11) - Downloading symfony/validator (v6.2.11) - Downloading symfony/serializer (v6.2.11) - Downloading symfony/http-foundation (v6.2.11) - Downloading symfony/process (v6.2.11) - Downloading symfony/var-dumper (v6.2.11) - Downloading symfony/error-handler (v6.2.11) - Downloading symfony/http-kernel (v6.2.11) - Downloading symfony/dependency-injection (v6.2.11) - Upgrading symfony/console (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/validator (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/serializer (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/http-foundation (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/process (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/var-dumper (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/error-handler (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/http-kernel (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/dependency-injection (v6.2.10 => v6.2.11): Extracting archive Generating autoload files
The rest of it, staring with composer remove drupal/blazy is the same and the error remains. Thoughts? Thanks...
- 🇩🇪Germany kreatIL
@bcobin: Did you already try to clear composer caches after removing drupal/blazy and before re-adding it?
composer cc
You could also runcomposer diagnose
to see if there is a config issue with composer. - 🇺🇸United States bcobin
OK - here goes:
composer remove drupal/blazy
./composer.json has been updated Running composer update drupal/blazy Loading composer repositories with package information Info from https://repo.packagist.org: #StandWithUkraine Updating dependencies Lock file operations: 0 installs, 9 updates, 0 removals - Upgrading symfony/console (v6.2.10 => v6.2.11) - Upgrading symfony/dependency-injection (v6.2.10 => v6.2.11) - Upgrading symfony/error-handler (v6.2.10 => v6.2.11) - Upgrading symfony/http-foundation (v6.2.10 => v6.2.11) - Upgrading symfony/http-kernel (v6.2.10 => v6.2.11) - Upgrading symfony/process (v6.2.10 => v6.2.11) - Upgrading symfony/serializer (v6.2.10 => v6.2.11) - Upgrading symfony/validator (v6.2.10 => v6.2.11) - Upgrading symfony/var-dumper (v6.2.10 => v6.2.11) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 0 installs, 9 updates, 0 removals - Downloading symfony/console (v6.2.11) - Downloading symfony/validator (v6.2.11) - Downloading symfony/serializer (v6.2.11) - Downloading symfony/http-foundation (v6.2.11) - Downloading symfony/process (v6.2.11) - Downloading symfony/var-dumper (v6.2.11) - Downloading symfony/error-handler (v6.2.11) - Downloading symfony/http-kernel (v6.2.11) - Downloading symfony/dependency-injection (v6.2.11) - Upgrading symfony/console (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/validator (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/serializer (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/http-foundation (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/process (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/var-dumper (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/error-handler (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/http-kernel (v6.2.10 => v6.2.11): Extracting archive - Upgrading symfony/dependency-injection (v6.2.10 => v6.2.11): Extracting archive Generating autoload files
composer cc
Clearing cache (cache-vcs-dir): /[site]/.composer/cache/vcs Clearing cache (cache-repo-dir): /[site]/.composer/cache/repo Clearing cache (cache-files-dir): /[site]/.composer/cache/files Clearing cache (cache-dir): /[site]/.composer/cache All caches cleared.
composer require drupal/blazy:^2.0 drupal/slick:^2.0 drupal/slick_views:^2.0
Info from https://repo.packagist.org: #StandWithUkraine ./composer.json has been updated Running composer update drupal/blazy drupal/slick drupal/slick_views Loading composer repositories with package information Updating dependencies Nothing to modify in lock file Writing lock file Installing dependencies from lock file (including require-dev) Nothing to install, update or remove Generating autoload files
composer diagnose
Checking composer.json: WARNING require.drupal/domain : exact version constraints (2.0.x-dev@dev) should be avoided if the package follows semantic versioning require.drupal/domain_theme_switch : exact version constraints (1.x-dev@dev) should be avoided if the package follows semantic versioning require.drupal/fontyourface : exact version constraints (3.x-dev@dev) should be avoided if the package follows semantic versioning require.drupal/image_focus : exact version constraints (2.0.x-dev@dev) should be avoided if the package follows semantic versioning require.drupal/views_ical : exact version constraints (1.x-dev@dev) should be avoided if the package follows semantic versioning Checking platform settings: OK Checking git settings: OK git version 2.38.3 Checking http connectivity to packagist: OK Checking https connectivity to packagist: OK Checking github.com rate limit: OK Checking disk free space: OK Checking pubkeys: FAIL Missing pubkey for tags verification Missing pubkey for dev verification Run composer self-update --update-keys to set them up Checking composer version: You are not running the latest stable version, run `composer self-update` to update (2.5.1 => 2.5.7) Composer version: 2.5.1 PHP version: 8.1.19 PHP binary path: /opt/cpanel/ea-php81/root/usr/bin/php OpenSSL version: OpenSSL 1.1.1t 7 Feb 2023 cURL version: 8.0.1 libz 1.2.7 ssl OpenSSL/1.1.1t zip: extension present, unzip present, 7-Zip not available
Checking pubkeys: FAIL is suspect.
I'll forward this thread along to my hosting company (Imageleet) and see what they think as opposed to running self-update from terminal. (I've never come up with a problem they haven't been able to solve - and that's been for 17 years now!)
Thanks again SO much for your input - I'll let you know what they say..
- 🇮🇩Indonesia gausarts
No other ideas :)
Just in case a miss, there is an option to fetch
source
which is a wrapper forgit clone
:
https://getcomposer.org/doc/06-config.md#preferred-installOr similar to
--prefer-source
flag in your CLI.These will result in non-packaged installs like your issues similar to
git clone
:
Version: 8.x-2.x
while should beVersion: 8.x-2.15
Be sure to remove nor use them, if you did, unless you are planning to patch, etc. for dev purposes..
If you resolved, kindly share to benefit others.
Thanks.
Automatically closed - issue fixed for 2 weeks with no activity.