Answers.Body: <p>There used to be a bug in Craft 3.0 (fixed in 3.0.19) where, if an error occurred during an update, your <code>composer.json</code> file could be left in a weird state where it was directly requiring all of Craft’s dependencies (recursively). My guess is that this happened to you.</p>
  
  <p>Try opening your <code>composer.json</code> file and see if your <code>require</code> setting contains a whole bunch of dependencies, such as <code>twig/twig</code>.</p>
  
  <p>If so, then just delete all of the dependencies that don’t need to be in there. If the file is tracked in Git, then you should be able to look up its history and find the point where all of the extra dependencies were added. Otherwise you’ll need to figure that out for yourself.</p>
  
  <ul>
  <li>You definitely need <code>craftcms/cms</code>.</li>
  <li>You probably need <code>vlucas/phpdotenv</code>, if any of your environments are using a <code>.env</code> file.</li>
  <li>If you have any plugins installed, then each of them will have one corresponding dependency.</li>
  <li>Beyond that, everything else should be safe to remove (unless you intentionally added something else).</li>
  </ul>
  
  <p>Once you’ve removed everything you don’t need, try changing your <code>craftcms/cms</code> requirement to <code>^3.4.5</code> and then run <code>composer update</code>. As a sanity check, pay attention to which dependencies get <em>removed</em> in the process, in case you accidentally over-corrected.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-10T21:09:51.963Z
Answers.LastActivityDate: 2020-02-10T21:09:51.963Z
Answers.UserDisplayName: Brandon Kelly
Body: <p>I'm unfortunately dealing with a very old system that hasn't been updated in a long time. I've been able to update it up to 3.0.41.1 but once I attempt to go any further I get tons of different errors. They primarily seem to be migrations. I keep having to do a restore of the DB I'm working with over and over to try to sort this out but I'm not sure what else to be looking for.</p>
  
  <p>Any recommendations? (besides updating things at the right time?)</p>
  
  <p>UPDATE 1:</p>
  
  <p>When attempting to update from the web interface (which i think attempts to go straight to 3.4.5) I consistently get the following error:</p>
  
  <pre><code>Composer output: Package "craftcms/vue-asset" listed for update is not installed. Ignoring.
  Loading composer repositories with package information
  Updating dependencies
  Your requirements could not be resolved to an installable set of packages.
  
  Problem 1
  - Installation request for craftcms/cms 3.4.5 -&gt; satisfiable by craftcms/cms[3.4.5].
  - craftcms/cms 3.4.5 requires twig/twig ~2.12.0 -&gt; satisfiable by twig/twig[v2.12.3, v2.12.2, v2.12.1, v2.12.0] but these conflict with your requirements or minimum-stability.
  Problem 2
  - spicyweb/craft-embedded-assets 2.0.12 requires craftcms/cms ^3.0.0 -&gt; satisfiable by craftcms/cms[3.4.5].
  - spicyweb/craft-embedded-assets 2.0.12 requires craftcms/cms ^3.0.0 -&gt; satisfiable by craftcms/cms[3.4.5].
  - spicyweb/craft-embedded-assets 2.0.12 requires craftcms/cms ^3.0.0 -&gt; satisfiable by craftcms/cms[3.4.5].
  - craftcms/cms 3.4.5 requires twig/twig ~2.12.0 -&gt; satisfiable by twig/twig[v2.12.3, v2.12.2, v2.12.1, v2.12.0] but these conflict with your requirements or minimum-stability.
  - Installation request for spicyweb/craft-embedded-assets 2.0.12 -&gt; satisfiable by spicyweb/craft-embedded-assets[2.0.12].
  
  Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
  </code></pre>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-02-08T13:35:06.060Z
Comments.Text: Can you post your current `composer.json` file contents?
Comments.UserDisplayName: Brandon Kelly
Tags: <migration><updates>
Title: Updating old setup (3.0.41.1) to 3.1.0 various errors every time
ThreadText: # Updating old setup (3.0.41.1) to 3.1.0 various errors every time
  
  (Asked by: username_0 on 2020-02-08)
  
  I'm unfortunately dealing with a very old system that hasn't been updated in a long time. I've been able to update it up to 3.0.41.1 but once I attempt to go any further I get tons of different errors. They primarily seem to be migrations. I keep having to do a restore of the DB I'm working with over and over to try to sort this out but I'm not sure what else to be looking for.
  
  Any recommendations? (besides updating things at the right time?)
  
  UPDATE 1:
  
  When attempting to update from the web interface (which i think attempts to go straight to 3.4.5) I consistently get the following error:
  
  ```
  Composer output: Package "craftcms/vue-asset" listed for update is not installed. Ignoring.
  Loading composer repositories with package information
  Updating dependencies
  Your requirements could not be resolved to an installable set of packages.
  
  Problem 1
  - Installation request for craftcms/cms 3.4.5 -> satisfiable by craftcms/cms[3.4.5].
  - craftcms/cms 3.4.5 requires twig/twig ~2.12.0 -> satisfiable by twig/twig[v2.12.3, v2.12.2, v2.12.1, v2.12.0] but these conflict with your requirements or minimum-stability.
  Problem 2
  - spicyweb/craft-embedded-assets 2.0.12 requires craftcms/cms ^3.0.0 -> satisfiable by craftcms/cms[3.4.5].
  - spicyweb/craft-embedded-assets 2.0.12 requires craftcms/cms ^3.0.0 -> satisfiable by craftcms/cms[3.4.5].
  - spicyweb/craft-embedded-assets 2.0.12 requires craftcms/cms ^3.0.0 -> satisfiable by craftcms/cms[3.4.5].
  - craftcms/cms 3.4.5 requires twig/twig ~2.12.0 -> satisfiable by twig/twig[v2.12.3, v2.12.2, v2.12.1, v2.12.0] but these conflict with your requirements or minimum-stability.
  - Installation request for spicyweb/craft-embedded-assets 2.0.12 -> satisfiable by spicyweb/craft-embedded-assets[2.0.12].
  
  Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
  
  ```
  
  **Tags:** migration, updates
  
  > **Comments:**
  > **username_1**: Can you post your current `composer.json` file contents?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-02-10. Score: 1 | Accepted answer
  
  There used to be a bug in Craft 3.0 (fixed in 3.0.19) where, if an error occurred during an update, your `composer.json` file could be left in a weird state where it was directly requiring all of Craft’s dependencies (recursively). My guess is that this happened to you.
  
  Try opening your `composer.json` file and see if your `require` setting contains a whole bunch of dependencies, such as `twig/twig`.
  
  If so, then just delete all of the dependencies that don’t need to be in there. If the file is tracked in Git, then you should be able to look up its history and find the point where all of the extra dependencies were added. Otherwise you’ll need to figure that out for yourself.
  
  * You definitely need `craftcms/cms`.
  * You probably need `vlucas/phpdotenv`, if any of your environments are using a `.env` file.
  * If you have any plugins installed, then each of them will have one corresponding dependency.
  * Beyond that, everything else should be safe to remove (unless you intentionally added something else).
  
  Once you’ve removed everything you don’t need, try changing your `craftcms/cms` requirement to `^3.4.5` and then run `composer update`. As a sanity check, pay attention to which dependencies get *removed* in the process, in case you accidentally over-corrected.
  
  
  ---
  
  