Solution to the problem reported below
Original report
Hi,
When I trying to update Drupal core to 8.7.0 using composer I am getting the following error.
$ composer require drupal/core:8.7.0 --update-with-dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Can only install one of: egulias/email-validator[2.0.x-dev, 1.2.14].
- Can only install one of: egulias/email-validator[2.0.x-dev, 1.2.14].
- Can only install one of: egulias/email-validator[2.0.x-dev, 1.2.14].
- drupal/core 8.7.0 requires egulias/email-validator ^2.0 -> satisfiable by egulias/email-validator[2.0.x-dev].
- Installation request for drupal/core 8.7.0 -> satisfiable by drupal/core[8.7.0].
- Installation request for egulias/email-validator (locked at 1.2.14, required as ^1.2) -> satisfiable by egulias/email-validator[1.2.14].
When I try to update the egulias/email-validator[ package separately it shows:
$ composer require egulias/email-validator:2.0.1 --update-with-dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for egulias/email-validator 2.0.1 -> satisfiable by egulias/email-validator[2.0.1].
- Can only install one of: egulias/email-validator[2.0.1, 1.2.x-dev].
- Installation request for egulias/email-validator ^1.2 -> satisfiable by egulias/email-validator[1.2.x-dev].
Drupal 8.6.15 reqquires email-validator with ^1.2 version and 8.7.0 requires ^2.0 email-validator.
Any solution? help please.
Comments
Comment #2
xjmComment #3
maskedjellybeanI'm sorry I don't have an answer, but I'm facing the same issue. We seem to be stuck in a loop here.
Comment #4
maskedjellybeanOh wow. I found a solution. I'm sure it is not the correct solution but it does work. From within your drupal directory, open core/composer.json.
Search for "egulias/email-validator". Change the version to "^2.0".
Run
composer update egulias/email-validator drupal/core --with-dependenciesSo many wasted hours chasing down why Composer does not update.
Comment #5
cilefen commentedIf egulias/email-validator is specified in your composer.json, you have to do something like #4.
Comment #6
websiteworkspace commentedThis problem is occurring when - egulias/email-validator - is not in the composer.json!
The fact that this problem is occurring implies a problem buried deep in the package dependency lists in drupal core.
composer is issuing the following nonsense sorts of responses after trying every variation imaginable!
Note that: egulias/email-validator is NOT in the composer.json prior to the command!
Comment #7
websiteworkspace commentedHERE IS A HACK TO RESOLVE THIS ANNOYING PROBLEM!
While working on this update problem, I finally remembered that similar sorts of nonsense occurs with nearly every update from x.y.* to x.z.* version (for example 8.6.x to 8.7.x).
I even built a shell script a while ago that performs all the required steps.
Do the following:
0) create a full site backup
1) delete the core and vendor directories
2) delete the composer.lock file
3) edit the composer.json to hard code the desired drupal core version (such as 8.7.1 in this instance)
3) run - composer update (update everything)
- - since the core and vendor directories don't exist, composer will recreate them with all new contents
4) run - drush -n -y updb (does database updates)
5) run - drush -n -y cr (rebuilds the site code/cache)
6) test the site
7) re-edit composer.json to "^8.7" for the drupal core version.
Comment #8
cilefen commentedThe composer subcommand to use is ‘why-not drupal/core:8.7.1’ if memory serves. Yes the messages are impossible to interpret sometimes.
P.S. For more help post composer.json and composer.lock so some of us have even a chance to recreate the problem and to help. I think I’ll make that my policy from now on.
Comment #9
portulacaI changed the desired Drupal version in composer.json with
composer require [...] --no-updateas suggested here: https://www.drupal.org/project/drupal/issues/3052057#comment-13094021 and it worked, the update went through, and the egulias/email-validator was updated in the process.Is there a better way to state the desired Drupal version in composer.json so it doesn't have to be changed this way between minor versions?
@cilefen I posted some info in the comment below the one I linked to. I'm repeating it here:
Prohibits (why-not):
How I fixed it:
Comment #10
websiteworkspace commented@cilefen
This problem is not created by specifics in a site level composer.json.
This problem is created by problems deep within the package dependencies of drupal core itself.
This particular package conflict occurs because 8.6.16 wants and installs egulias/email-validator (^1.2) - but - drupal/core 8.7.x wants egulias/email-validator (^2.1)
(note the results of the following composer command when core 8.6.16 is installed)
(note the results of the following composer command when core 8.6.16 is installed)
(then a composer update attempt outputs the following error(s)
Every recent major core update has contained a dependency problem like this that can only be overcome by deleting the composer.lock, /core, /vendor, and then running composer update, upon which composer rebuilds all /core and /vendor contents from scratch.
Comment #11
websiteworkspace commentedHere is the output of the composer analysis command suggested by @cilefen.
(note that the drupal core version when running the command below is 8.6.16)
Comment #12
cilefen commented@websiteworkspace Do you have the Composer merge plugin configured to merge core/composer.json? If so, you should not.
Comment #13
cilefen commentedI'm just guessing because you have not posted the files...
Comment #14
websiteworkspace commentedHACK TO SOLVE THIS PROBLEM
Assuming that there aren't any other package dependency problems, the following command in a shell script file will work around the catch22 created by the egulias/email-validator version requirements in the source and target drupal core versions.
or
Comment #15
websiteworkspace commented@cilefen wrote
Please expound and clarify, including an explanation of "If so, you should not.", explaining why not.
Comment #16
cilefen commented#11 and #2912387: Stop using wikimedia/composer-merge-plugin explain in a way why not and in fact this particular problem didn't become a problem until some (I don't remember which) version of Composer.
I'm guessing (still haven't seen the files!) that the 'name' key in composer.json is 'drupal/drupal', right? #11 is basically saying that composer.json that drupal/core (from Packagist or whatever) conflicts with the core/composer.json that is currently sitting there, because it is being merged into the site's own composer.json (aka drupal/drupal).
Comment #17
websiteworkspace commented@cilefen
I just downloaded the 8.7.1 base core package from the following link:
https://www.drupal.org/project/drupal/releases/8.7.1
The default composer.json included in the archive at the link just above includes the:
directives.
However, @cilefen, your post tersely implies that this "should not" be used, but without explanation.
Please provide an explanation, and please include links / citation of documentation that documents the various behaviors of these directives.
Comment #18
cilefen commentedAlso #3020337: Composer returns "Your requirements could not be resolved to an installable set of packages" when core/composer.json is included in the merge plugin configuration.
Comment #19
cilefen commentedThe compressed download composer.json has to be modified in order to manage the site fully with Composer. This is still being worked out and yes, it has been messy. There are lots of issues about improving the state of play.
Comment #20
websiteworkspace commented@cilefen
As I've just carefully documented in my most recent post, drupal core archive package continues to contain a composer.json that includes "merge-plugin" directives.
-
How does the "merge-plugin" directive impact the problem that I and others have experienced and documented, the basic composer updating problem which inspired the bug report that is under examination in this discussion thread?
Comment #21
websiteworkspace commentedIf the "merge-plugin" directives are deprecated, why does the official drupal core archive, even as of today, continue to ship with a deprecated composer.json, which surely thousands of people are using as a gold standard for maintaining their sites with the composer utility?
Comment #22
cilefen commentedI just explained in #16 and linked to issues. I am trying to help you for free, with no appreciation but more demands of my time. The fact is that the current documentation recommends a different approach than downloading a compressed archive. That's new since you and I first installed Drupal 8 sites. See #19 about this being a messy process as 8 has evolved.
Issues exist like #2845378: Stop offering .tar.gz downloads, for example.
Comment #23
websiteworkspace commentedOnly by accident or necessity after having a problem would one stumble upon the following page:
https://www.drupal.org/project/drupal/issues/3020337
More importantly, the discussion at the link just above DOES NOT fully explain the reasons for the problem or explain why the change is needed, i.e. including what behaviors occur with and/or without the directive in question.
Comment #24
websiteworkspace commentedThe really annoying drupal file/directory setup created by the following really annoying configuration is not available to a huge portion of the drupal dev/user base!
https://www.drupal.org/docs/develop/using-composer/using-composer-to-ins...
Myself and tens of thousands other drupalers aren't/can't going to spend person years of work retooling existing person years of work built on the standard directory setup.
Comment #25
websiteworkspace commented@cilefen
I believe that I have contributed significantly and generously to this thread, to hopefully help thousands of other drupalers who have experienced this problem, by providing a practical solution for updating existing drupal 8 code bases, and explanations of what and why the solutions I've suggested provide.
Also, and quite importantly, I too have provided those solutions for free to anybody who reads this thread.
Comment #26
cilefen commentedI explained it in #16. I feel like you think core contributors are doing this to you just for fun and I'm sorry you don't like it and continue sort-of yelling at me. And I can tell you are animated by this problem—and let me be clear I myself was "bitten" by this very issue—anyone can edit documentation, but in fact someone put in some work on https://www.drupal.org/docs/8/install/add-composer-to-an-existing-site. Just for the record, below is a composer.json what was converted from the default zip to Composer-managed. You may want to avoid webflo/drupal-core-strict unless you know you need it, as it introduces more stringent requirements and Composer knowledge when using.
Comment #27
websiteworkspace commented@cilefen
Based on your entirely arrogant and inappropriate comment as quoted below:
You have some serious social interaction/perception problems, and possibly some social maturely problems as well.
You need to grow up and learn to stay focused on the code/coding problem and stop personalizing and getting your emotions involved, and/or incorrectly thinking/believing that anyone else is as ego and emotion involved as you are.
Comment #28
cilefen commentedIf there is nothing further I am presently going to duplicate this onto #3020337: Composer returns "Your requirements could not be resolved to an installable set of packages" when core/composer.json is included in the merge plugin configuration. Its issue summary could use an update with a good explanation. Some prose from #16 would do.
Comment #29
mmjvb commented@portulaca The version constraint ~8.7.0 keeps you within 8.7, allowing to go to 8.8 and 8.9 it should be ^8.7.0 or ~8.7.
My preference is ~8.7.0, making the change in minor a more conscious decision.
Our solution works for those that understand the difference between drupal/drupal and drupal-composer/drupal-project or any other proper distribution for site building. Not sure which distribution the OP is using. Looks like this issue has been hijacked !
Comment #30
cilefen commentedI think @portulaca is dealing with how to update in a webflo/drupal-core-require-dev context, which as far as I can tell is different than the OP's issue.
Comment #31
mmjvb commentedNo, we are not dealing with the update in a webflo/drupal.... context.
As you can see we are dealing from an unknown context. Use "composer prohibits" to find out your context!
It happens to be webflo/drupal-core... that blocks, but you need to find out what blocks you because your project is unique. Depending on those blocks, you need to decide for option --with-dependencies or whitelisting blocking packages.
Or use --dry-run on "composer update" to see what gets updated. When you don't care about what gets updated, feel free to use "composer update". When you do, whitelist what needs updating.
In addition, make sure you are running most recent version of composer. Older versions are known to cause these issues.
"$ sudo composer selfupdate"
Comment #32
Karthikavn commentedTried the solution #4 and it results:
Still waiting for a solution.
Comment #33
aburrows commentedJust stepping in here. This issue is starting to become personal and should not be in anyway. I to experience issues with composer and dependencies but there is no need to get personal with @cilefen
So can you @websiteworkspace please take a break from this issue and come back later on.
Please see https://www.drupal.org/dcoc for more on our code of conduct whilst using Drupal.org and interacting with others in the issue queue.
Alex - For and on behalf of Drupal community working group
Comment #34
Karthikavn commentedTried the solution #7 by @websiteworkspace and it results:
Comment #35
handkerchief#4 works for me. After the change in core/composer.json I had to execute this:
composer update egulias/email-validator symfony/http-foundation drupal/core --with-dependenciesComment #36
Karthikavn commented@handkerchief Can you please tell me what are the steps you follow to update the core? other than updating core/composer.json to
"egulias/email-validator": "^2.0"
And also can you please confirm, after the core update did you face any error like https://www.drupal.org/project/drupal/issues/3053583
The feedback should be appreciated.
Comment #37
handkerchiefOf course:
1.
drush sset system.maintenance_mode 12.
drush cr3. Change your own composer.json of your drupal installation in the require section:
"drupal/core": "8.7.1",But I guess ^8.7 will do it too.
4. Change core/composer.json
"egulias/email-validator": "^2.0"5. Run
composer update egulias/email-validator drupal/core --with-dependencies6. If a composer error appears which report other projects, add this projects to your composer command.
e.g.
composer update egulias/email-validator symfony/http-foundation drupal/core --with-dependencies7. If it worked, run
drush updbanddrush entity-updates8.
drush sset system.maintenance_mode 09.
drush crThats all. No error has appeared.
Comment #38
cilefen commentedIf anyone has core/composer.json in the merge configuration, read #3020337: Composer returns "Your requirements could not be resolved to an installable set of packages" when core/composer.json is included in the merge plugin configuration or this will happen to you again in the future.
Comment #39
Karthikavn commented@handkerchief Thanks for the update.
I followed the same steps and it results Drupal core finally updated to 8.7.1. Thanks once again.
(The extra step I have done is to remove the composer.lock file)
But after the update, when I tested the site I got this error: https://www.drupal.org/project/drupal/issues/3053583.
Is that something you could help me out to resolve this issue?
Also which version of PHP are you using?
Comment #40
cilefen commentedEveryone: Please read the P.S. in #8. These files vary by site. Attach them in a comment if you experience difficulty upgrading.
Comment #41
Karthikavn commentedComment #42
handkerchiefWatch out: On another instance I additionally had this problem #3040129: Fatals in make_menu_link_content_revisionable when combined with make_taxonomy_term_revisionable with this solution:
https://www.drupal.org/project/drupal/issues/3040129#comment-13096630
@Karthikavn sorry for this error, I'm afraid I really don't know. I'm using PHP 7.2.17. I hope you will find help from the community in the other issue #3053583: Drupal core update 8.7.1 throws an error in Drupal\\serialization\\Normalizer\\EntityNormalizer
Comment #43
unsettlingtrend#37 worked for me. Also want to voice my opinion that it's a huge pain constantly dealing with issues when updating drupal/core through composer.
Comment #44
Karthikavn commented@handkerchief Thanks for update. Your comments really helpful for me.
Comment #45
cilefen commentedRe #43, #37 will work...until this happens again. It will happen to you again if #3020337: Composer returns "Your requirements could not be resolved to an installable set of packages" when core/composer.json is included in the merge plugin configuration applies to your sites.
Comment #46
mxr576Comment #47
zorax@handkerchief Thanks for this clear update! You save my time !
Comment #48
alienzed commentedI was ultimately able to resolve this by download Drupal core and uploading it manually, at which point I ran into composer.lock preventing the update. After manually updating the version of egulias/email.... and re-running composer up, it worked. What I don't understand is the following.
the core/composer.json for 8.7 specifies the newer version of egulias/email..., but it seems like composer up checks the old (8.6) composer.json for versions and decides 8.7 won't like what is installed. Why doesn't the 8.7 composer.json, which would get a new core/composer.json with the right requirements take precedence? My project doesn't require egulias/email... itself, it is a requirement of Core.
It seems like manually updating composer.lock is a bad thing to do, but that's what I need to do to get this working. Shouldn't requirements be met in order? Like, first core/composer.json requirements and then up?
Comment #49
cilefen commentedSee #45. I feel like a broken record. It may apply to you.
Comment #50
NatDevD commented@handkerchief Thank you very much indeed, that worked for me too.
Specifically, when updating from the latest 8.6 to 8.7.1, for your step #6 I needed to do:
composer update egulias/email-validator drupal/core webflo/drupal-core-require-dev --with-dependencies
@cilefen @websiteworkspace and all others, your contribrutions are appreciated.
Comment #51
cilefen commentedI am converting this now to a support request because every issue to date has been about understanding the upgrade commands needed for drupal-project (as of this moment, supported on GitHub), or, #3020337: Composer returns "Your requirements could not be resolved to an installable set of packages" when core/composer.json is included in the merge plugin configuration. More importantly, no commit to Drupal Core is likely to result from this issue. And there are major initiatives and issues open elsewhere to facilitate Composer use in Drupal.
But I will leave this open for further discussion. Thanks everyone for sharing tips.
Comment #52
makazimtingwa commentedAfter trying all the options listed here and failing, the only thing that worked for me was to remove the following from my composer.json file
After the upgrade work, I placed the section back in composer.json. I'm concerned something will break in the future with the missing section.
Comment #53
cilefen commentedMerging core/composer.json will only cause problems. Take it out.
Comment #54
remyyyyy@cilefen Thank you very much, that worked for me.
Comment #57
Anitta commentedupdate composer.json
If your current version is 8.x(below 8.6.16), then upgrade to 8.6.16
"drupal/core": "8.6.16"
If the composer update shows an error related to this module "egulias/email-validator"
"egulias/email-validator": "^2.0" - Add this to your composer.json or edit the existing version
run composer update
check your composer version upgrade it to 1.8
edit composer.json "drupal/core": "8.7.1",
rename folders core and vendor
run composer install
It worked for me
Comment #58
mingsong#7 works to me.
Comment #59
kirkkalaI got past this issue with updating 8.6.16 -> 8.7.1, inspired by #4:
Comment #60
cilefen commentedI wish that #16, #45, #51 would inspire people because they represent the correct fix. If you find yourself editing core/composer.json, you are not really fixing the problem.
Comment #61
_san_ commented#59 worked for me!
Comment #62
mmjvb commented@ssteigen Good for you. Do you also understand why it is wrong?
Comment #63
SpursFan commented@mmjvb Ok i'll ask..I'm new to Drupal. I am having the exact same issue, composer update will not update. I am tempted to go #59's route. But everything inside me says never edit core files. is it safe to do so in Drupal? Again sorry for my ignorance, as I'm new to Drupal. Thanks sir!
Comment #64
cilefen commentedComment #65
mmjvb commentedYou started with the wrong distribution! When you download the distribution of Drupal, you get something that is meant for software developers. NOT for site builders. For site building you require a different distribution. The package for software developers is different from those for site builders. In addition there are quite a few distributions for site builders. They all use drupal/core and drupal-composer/drupal-scaffold as requirement because they are needed when you want your site to update its code base.
For development the core/composer.json is integrated with the composer.json via the merge plugin. That is why drupal/core is mentioned in the replace section. Rather than having it included via drupal/core it is put in the package itself and replacing drupal/core. Moving it from the replace to the require section is causing problems when not removing it from the merge plugin.
Rather than trying to solve every issue at the time you are running into it, you can do things the right way from the start. Sure, there are developers that fully understand how the drupal/drupal package is designed to work and turn that into a package that can be used for site building. Considering the amount of issues that is not an easy job for a site builder. And proven difficult for developers as well. Start your project the right way and pick one of the available distributions or the popular package drupal-composer/drupal-project. They have been set up for site building and allow you to update the code base with composer.
Once started the right way you need to maintain your code base by following the instructions of that particular distribution. They have documented what you need to do for updating to a new version of their distribution. When you want to stay current in the mean time, use the composer commands below:
- composer outdated -Dm
- composer prohibits vendor/package version
- composer show vendor/package
- composer show vendor/package -a
- composer depends vendor/package -t
- composer outdated -m
- composer outdated
- composer update vendor/package --with-dependencies --dry-run
- composer require vendor/package:constraint --no-update
- composer update vendor/package vendor/package vendor/package
These commands allow you to find out whether you need to do something and what it is that you need to do. Not only updating your code base, also put in support requests for changes to requirements of packages or new releases.
Comment #66
Karthikavn commented#7, #37 - Fixed the issue.
Comment #67
cilefen commentedNevertheless, #28 is the full solution.
Comment #68
mmjvb commentedRemoved PHP 7.3 because it has nothing to do with it.
Also, #7 and #37 DID NOT fix the issue. There are many ways to get to Drupal 8.7.0. Staying on drupal/drupal is NOT the right thing to do. Trying to convert from drupal/drupal to something that is meant for site building IS. Unfortunately, that is not provided yet, but they are working on it. Some people still don't understand it is a little bit more than moving drupal/core from replace to require. Even removing drupal/core composer.json from the merge plugin is not enough.
The proper fix is to go to a distribution meant for site building.
Comment #69
keithdoyle9 commentedI removed the merge-plugin section and now I'm getting email validation errors. We're on 8.6.16. If I leave that in, I get dependency errors
@MakaziMtingwa
Comment #70
cilefen commentedIt would be interesting to know how you executed composer after removing the merge plugin configuration and what the output was.
Comment #71
cilefen commented...and post the composer.json because we are merely guessing at solutions without it.
Comment #72
kellyimagined commentedUsing #59 with the following additional steps
Clear out vendor directory except simplesamlphp because simplesamlphp is just so dang finicky
Remove composer.lock
#59 steps
composer install
composer require drupal/core:^8.7.2
This worked.
Comment #73
karenann commentedAfter reading this entire thread, and the linked ones, I found my way to:
Update core PHP dependencies before 8.7.0
In my situation, I do NOT have egulias/email-validator in my composer.json so figured it was an underlying dependency. So, I didn't want to add it to my composer.json.
I see egulias/email-validator in that list.
I haven't solved my implementation yet as it's time to go home, but wanted to share this here for anyone else who might find value in it.
Comment #74
cilefen commentedRead #28.
Comment #75
mmjvb commented@karenann Migrate to a proper distribution for a clean solution or continue on the road of solving each issue at the time.
The combination of drupal/core as requirement and core/composer.json included by merge plugin is the cause.
That is why it is documented that drupal/drupal doesn't allow updating drupal/core.
Removing core/composer.json from the merge plugin will solve this issue for you. When not used for other things you can remove the merge plugin and the rest of its code in the extra key as well.
Assume you added scaffold. Not sure about remaining issues.
Comment #76
karenann commentedI had read #28. It is bookmarked. And thanks for the guidance, mmjvb and cilefen.
I'm working with inherited code and gathering info. I still need to get my house in order, as mentioned. However, there's a lot of info in this thread and I thought that https://www.drupal.org/project/drupal/issues/3032693 was informationally relevant, so I shared. YMMV.
Comment #77
terminalc commented#37 was pretty close
I had to remove wikimedia/composer-merge-plugin configs in composer.json
I also had to
composer require symfony/http-foundation:~3.4.27 --no-update
Comment #79
patrick.thurmond@gmail.comI found that I just had to run `composer update` with no qualifying package names and it resolved this exact issue. This is because it looks for updates to all modules and packages and becomes more flexible.
Comment #80
mmjvb commentedAgain, you haven't solved anything when staying on drupal/drupal. For site building you need to move away from drupal/drupal. It is meant for development of drupal itself, not for site management.
Advice against `composer update` without whitelisting packages. Yes, it will resolve your requirements if it can, but will update anything allowed. Unfortunately, that trusts the version constraints used. Currently a bad thing to do. There is a poor understanding of the version constraints and most don't provide the upper limit.
Comment #81
doncheks commentedModifying the version of drupal or projects to run a composer update is definitely a temporary solution, as you would have to keep doing same for other minor updates.
When the composer update command below fails,
composer update drupal/core --with-dependenciesYou may want to investigate your composer.json file. If you have
"core/composer.json"in the merge plugin configuration, try removing it for a more permanent fix, as stated by @cilefenTo do that, Delete the following lines, if they exist
Also, delete these if they exist.
Then run the composer update command as stated at the top of this post again.
It should work this time.
You may need to run composer update command twice if doesn't update to the latest version of drupal or download all dependencies.
The following has been tested for updating from 8.6.x to 8.7.x and from 8.7.x to 8.7.x
Comment #82
mmjvb commentedAdvice against the above! Again, you haven't solved anything when staying on drupal/drupal. For site building you need to move away from drupal/drupal. It is meant for development of drupal itself, not for site management.
Suggest to wait for https://www.drupal.org/project/drupal/issues/3047468 or do the right thing instead.
EDIT: No longer suggest to wait for that. Unfortunately, the scope of that issue was changed and no longer useful. Leaves you with the manual work.
Comment #83
zyla commentedI've tried solution in #9 and it works for me. Thanks!
Comment #84
zyla commentedI've tried solution in #9 and it works for me. Thanks!
Comment #85
rakesh.gectcrLooks like the #9 works!,
And my colleagues suggested me too, I ended up running like this
composer update drupal/core egulias/email-validator --with-dependenciesComment #86
semiaddict commented#9 worked for me as well.
As stated in https://github.com/webflo/drupal-core-require-dev, webflo/drupal-core-require-dev should have the same version constraint as the one used for drupal/core in composer.json
Comment #87
mmjvb commentedIndeed, #9 works. Do understand that it is the procedure that works, not the range of commands. Welcome to dependency management with Composer.
Procedure to update Drupal:
- Find out what is stopping you to update: composer prohibits
- Take away each blocking factor
-- Remove dev requirement of webflo when not needed: composer remove webflo/drupal-core... --no-update
-- Change version constraints of requirements: composer require ... --no-update
-- Find out what uses egulias/email-validator: composer depends egulias/email-validator
- Dry run the update: composer update drupal/core --with-dependencies --dry-run
- Whitelist allowable updates
- Run the update without --dry-run with --with-dependencies or whitelisted updates
There is no need to whitelist egulias/email-validator as it is a dependency of drupal/core. Suggest to remove webflo/drupal-core... or keep it in sync with drupal/core.
Obviously, your situation may be different, which is the reason you need to follow the procedure instead of the commands themselves. The commands themselves are just an example.
For those stubborn enough staying on drupal/drupal, good luck!
Comment #88
rhip commentedIf you just need to update Drupal this might work:
composer require drupal/core egulias/email-validatorPerhaps not ideal but it might start you off.
Comment #89
lhguerra commentedI went around this by just requiring the conflicting libs and then removing them:
composer require drupal/core egulias/email-validator typo3/phar-stream-wrappercomposer remove egulias/email-validator typo3/phar-stream-wrapperThis way, composer can install the new Drupal version and then we can remove the libs we don't want in our composer.json
It is safe to remove these libs because they are already required by drupal/core
Comment #90
sistocarta commentedI took the core composer.json from de new Core version. Than the update works perfect.