Answers.Body: <p>I was able to take your composer.json file, run <code>composer update</code> from it without any issues, do an install of Craft from that and update Craft/plugins and install/uninstall Craft/plugins from the Control Panel without any issues.</p>
  
  <pre><code>symfony/yaml v4.1.0 requires php ^7.1.3 -&gt; your PHP version (7.2.14-1+ubuntu18.04.1+deb.sury.org+1) overridden by "config.platform.php" version (7.0) does not satisfy that requirement.
  </code></pre>
  
  <p>For that one, you've got this in your composer.json file:</p>
  
  <pre><code>  "config": {
      "sort-packages": true,
      "optimize-autoloader": true,
      "platform": {
        "php": "7.0"
      }
    },
  </code></pre>
  
  <p>Change it to this:</p>
  
  <pre><code>  "config": {
      "sort-packages": true,
      "optimize-autoloader": true,
      "platform": {
        "php": "7.2.14"
      }
    },
  </code></pre>
  
  <p>And it will go away.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-15T23:33:39.573Z
Answers.LastActivityDate: 2019-02-15T23:33:39.573Z
Answers.UserDisplayName: Brad Bell
Body: <p>I'm new to using Composer and I'm having trouble deploying to Laravel Forge. I am getting an error message that says:</p>
  
  <blockquote>
    <p>Your requirements could not be resolved to an installable set of packages.</p>
    
    <p>Problem 1
        - Installation request for illuminate/support v5.5.44 -> satisfiable by illuminate/support[v5.5.44].
        - don't install tightenco/collect v5.5.33|don't install illuminate/support v5.5.44
        - Installation request for tightenco/collect v5.5.33 -> satisfiable by tightenco/collect[v5.5.33].</p>
  </blockquote>
  
  <p>I didn't add these packages, they are dependencies of something I have added. So I have a few questions:</p>
  
  <p>First, how do I resolve this? I am thinking that I should not go in and try to change the version numbers on anything because that would break things most likely, correct? Also, since they are not in my composer.json file, I'm not sure how I would do this. </p>
  
  <p>Second, how do I determine what package I am installing uses this as a dependency? </p>
  
  <p>Third, I have a couple of plugins that I have uninstalled in the CP that are still showing up in the composer.json file.Do I need to go back into my composer.json file and remove them? I thought this was done automatically when a plugin was uninstalled, but that may be my mistake. I am wondering if one or more of those plugins might be the culprit.</p>
  
  <p>Thanks,</p>
  
  <p>Brian</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-02-11T03:23:30.310Z
Comments.Text: Can you 1) let us know what version of Craft you're running and 2) share your composer.json file?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-02-11T14:54:11.573Z
Comments.Text: Thanks Brad. I'm running Craft 3.1.8. Here's a link to the composer json file:
  
  https://www.dropbox.com/s/kgwjmspl7sjedvq/composer.json?dl=0
Comments.UserDisplayName: Brian Rivet
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-02-11T23:21:51.360Z
Comments.Text: I don't know if it is relevant but I'm also getting errors when updating plugins in my local dev environment. I am getting errors when trying to update the Architect and ImageOptimize plugins.
Comments.UserDisplayName: Brian Rivet
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-02-11T23:24:39.030Z
Comments.Text: For Architect I get a lot of errors like this:
  
  - symfony/yaml v4.1.0 requires php ^7.1.3 -> your PHP version (7.2.14-1+ubuntu18.04.1+deb.sury.org+1) overridden by "config.platform.php" version (7.0) does not satisfy that requirement. 
  
  
  Along with:
  
  - pennebaker/craft-architect 2.2.12 requires symfony/yaml ^4.1 -> satisfiable by symfony/yaml[v4.1.10, v4.2.2, v4.1.9, v4.2.1, v4.2.0, v4.1.8, v4.1.7, v4.1.6, v4.1.5, v4.1.4, v4.1.3, v4.1.2, v4.1.1, v4.1.0].
  - Installation request for pennebaker/craft-architect 2.2.12 -> satisfiable by pennebaker/craft-architect[2.2.12].
Comments.UserDisplayName: Brian Rivet
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-02-11T23:26:58.333Z
Comments.Text: For Image Optimize I get: 
  - Installation request for nystudio107/craft-imageoptimize 1.5.3 -> satisfiable by nystudio107/craft-imageoptimize[1.5.3].
  - nystudio107/craft-imageoptimize 1.5.3 requires nystudio107/craft-imageoptimize-imgix ^1.0.2 -> no matching package found.
  
  I've already confirmed with Andrew that the tags are correct.
Comments.UserDisplayName: Brian Rivet
Tags: <craft3><composer><deployment>
Title: How do I resolve dependency conflicts in Composer?
ThreadText: # How do I resolve dependency conflicts in Composer?
  
  (Asked by: username_0 on 2019-02-08)
  
  I'm new to using Composer and I'm having trouble deploying to Laravel Forge. I am getting an error message that says:
  
  > Your requirements could not be resolved to an installable set of packages.
  >
  > Problem 1
  > - Installation request for illuminate/support v5.5.44 -> satisfiable by illuminate/support[v5.5.44].
  > - don't install tightenco/collect v5.5.33|don't install illuminate/support v5.5.44
  > - Installation request for tightenco/collect v5.5.33 -> satisfiable by tightenco/collect[v5.5.33].
  
  I didn't add these packages, they are dependencies of something I have added. So I have a few questions:
  
  First, how do I resolve this? I am thinking that I should not go in and try to change the version numbers on anything because that would break things most likely, correct? Also, since they are not in my composer.json file, I'm not sure how I would do this.
  
  Second, how do I determine what package I am installing uses this as a dependency?
  
  Third, I have a couple of plugins that I have uninstalled in the CP that are still showing up in the composer.json file.Do I need to go back into my composer.json file and remove them? I thought this was done automatically when a plugin was uninstalled, but that may be my mistake. I am wondering if one or more of those plugins might be the culprit.
  
  Thanks,
  
  username_0
  
  **Tags:** craft3, composer, deployment
  
  > **Comments:**
  > **username_1**: Can you 1) let us know what version of Craft you're running and 2) share your composer.json file?  
  > **username_0**: Thanks username_1. I'm running Craft 3.1.8. Here's a link to the composer json file:  https://www.dropbox.com/s/kgwjmspl7sjedvq/composer.json?dl=0  
  > **username_0**: I don't know if it is relevant but I'm also getting errors when updating plugins in my local dev environment. I am getting errors when trying to update the Architect and ImageOptimize plugins.  
  > **username_0**: For Architect I get a lot of errors like this:  - symfony/yaml v4.1.0 requires php ^7.1.3 -> your PHP version (7.2.14-1+ubuntu18.04.1+deb.sury.org+1) overridden by "config.platform.php" version (7.0) does not satisfy that requirement.    Along with:  - pennebaker/craft-architect 2.2.12 requires symfony/yaml ^4.1 -> satisfiable by symfony/yaml[v4.1.10, v4.2.2, v4.1.9, v4.2.1, v4.2.0, v4.1.8, v4.1.7, v4.1.6, v4.1.5, v4.1.4, v4.1.3, v4.1.2, v4.1.1, v4.1.0]. - Installation request for pennebaker/craft-architect 2.2.12 -> satisfiable by pennebaker/craft-architect[2.2.12].  
  > **username_0**: For Image Optimize I get:  - Installation request for nystudio107/craft-imageoptimize 1.5.3 -> satisfiable by nystudio107/craft-imageoptimize[1.5.3]. - nystudio107/craft-imageoptimize 1.5.3 requires nystudio107/craft-imageoptimize-imgix ^1.0.2 -> no matching package found.  I've already confirmed with Andrew that the tags are correct.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-02-15. Score: 0 | Accepted answer
  
  I was able to take your composer.json file, run `composer update` from it without any issues, do an install of Craft from that and update Craft/plugins and install/uninstall Craft/plugins from the Control Panel without any issues.
  
  ```
  symfony/yaml v4.1.0 requires php ^7.1.3 -> your PHP version (7.2.14-1+ubuntu18.04.1+deb.sury.org+1) overridden by "config.platform.php" version (7.0) does not satisfy that requirement.
  
  ```
  
  For that one, you've got this in your composer.json file:
  
  ```
    "config": {
      "sort-packages": true,
      "optimize-autoloader": true,
      "platform": {
        "php": "7.0"
      }
    },
  
  ```
  
  Change it to this:
  
  ```
    "config": {
      "sort-packages": true,
      "optimize-autoloader": true,
      "platform": {
        "php": "7.2.14"
      }
    },
  
  ```
  
  And it will go away.
  
  
  ---
  
  