Composer update - error

Ganesha604

I am trying to install version 14, but an error appears

[a0282028@walburga flarum]$ php73 composer.phar install --prefer-dist --no-dev -a Installing dependencies from lock file Verifying lock file contents can be installed on current platform. Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you runcomposer updateorcomposer update <package name>`.
Package operations: 1 install, 0 updates, 0 removals

Installing funkeye/custom-welcome-hero (0.1.1): Extracting archive
Generating optimized autoload files
Carbon 1 is deprecated, see how to migrate to Carbon 2.
https://carbon.nesbot.com/docs/#api-carbon-2
You can run './vendor/bin/upgrade-carbon' to get help in updating carbon and other frameworks and libraries that depend on it.
63 packages you are using are looking for funding.
Use the composer fund command to find out more!
[a0282028@walburga flarum]$
`

Ganesha604

Composer update

[a0282028@walburga flarum]$ php73 composer.phar update
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires fof/oauth ⁰.1.0 -> satisfiable by fof/oauth[0.1.0].
- Root composer.json requires funkeye/custom-welcome-hero ⁰.1.1 -> satisfiable by funkeye/custom-welcome-hero[0.1.1].
- funkeye/custom-welcome-hero 0.1.1 requires flarum/core >=0.1.0-beta.12 <0.1.0-beta.14 -> satisfiable by flarum/core[v0.1.0-beta.12, v0.1.0-beta.13].
- You can only install one version of a package, so only one of these can be installed: flarum/core[v0.1.0-beta, ..., v0.1.0-beta.14.1].
- fof/oauth 0.1.0 requires flarum/core ⁰.1.0-beta.14 -> satisfiable by flarum/core[v0.1.0-beta.14, v0.1.0-beta.14.1].
- Conclusion: don't install flarum/core v0.1.0-beta.14.1 (conflict analysis result)

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

clarkwinkelmann

Ganesha604 funkeye/custom-welcome-hero seems to be the problem. You will need to remove it if it's not compatible.

Ganesha604

clarkwinkelmann The folder has been deleted, but in the admin panel it is still there, it is not deleted

askvortsov

You need to remove extensions via composer remove: just deleting the folder might cause issues.

Ganesha604

askvortsov no work(

exemple

[a0282028@walburga flarum]$ php73 composer.phar remove clarkwinkelmann/flarum-ex t-create-user-modal --with-all-dependencies
clarkwinkelmann/flarum-ext-create-user-modal is not required in your composer.js on and has not been removed
./composer.json has been updated
Running composer update clarkwinkelmann/flarum-ext-create-user-modal --with-all- dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires fof/oauth ⁰.1.0 -> satisfiable by fof/oauth[0 .1.0].
- tpokorra/flarum-ext-post-notification is locked to version 0.3.9-beta.13 a nd an update of this package was not requested.
- tpokorra/flarum-ext-post-notification 0.3.9-beta.13 requires flarum/core > =0.1.0-beta.11 <0.1.0-beta.14 -> satisfiable by flarum/core[v0.1.0-beta.11, v0.1 .0-beta.11.1, v0.1.0-beta.12, v0.1.0-beta.13].
- You can only install one version of a package, so only one of these can be installed: flarum/core[v0.1.0-beta.3, ..., v0.1.0-beta.14.1].
- fof/oauth 0.1.0 requires flarum/core ⁰.1.0-beta.14 -> satisfiable by flar um/core[v0.1.0-beta.14, v0.1.0-beta.14.1].
- Conclusion: don't install flarum/core v0.1.0-beta.14.1 (conflict analysis result)

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and re movals for packages currently locked to specific versions.

Removal failed, reverting ./composer.json to its original content.

clarkwinkelmann

Ganesha604 there must be a sync problem between your dependencies and the lock file.

I see fof/oauth appears in the output as well, but it shouldn't be installed if you are still on beta 13.

Are you able to revert to a backup from before you tried installing fof/oauth?

Another option would be to delete the lock file, delete the vendor folder, then run composer install to re-install from composer.json. Depending what's in the file you might end up in either beta 13 or beta 14, but at least the lock file should then be in sync.

Ganesha604

clarkwinkelmann

Delete folder vendor
delete lock file
composer install

[a0282028@walburga flarum]$ php73 composer.phar install
No lock file found. Updating dependencies instead of installing from lock file. Use composer update over composer install if you do not have a lock file.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.