Skip to content

Instantly share code, notes, and snippets.

@iparr
Created March 14, 2019 11:25
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save iparr/3ef2a096cea7e2bdc99342dd9bf6dd44 to your computer and use it in GitHub Desktop.
Save iparr/3ef2a096cea7e2bdc99342dd9bf6dd44 to your computer and use it in GitHub Desktop.
❯ ./craft update craft
Fetching available updates ... done
Performing one update:
- craft 3.1.17.1 => 3.1.17.2
Backup the database? (yes|no) [yes]:no
Skipping database backup.
Performing update with Composer ... error: An error occurred
Output:
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: remove roave/security-advisories dev-master
- craftcms/cms 3.1.17.2 requires twig/twig ~2.6.2 -> satisfiable by twig/twig[v2.6.2].
- craftcms/cms 3.1.17.2 requires twig/twig ~2.6.2 -> satisfiable by twig/twig[v2.6.2].
- twig/twig v2.6.2 conflicts with roave/security-advisories[dev-master].
- twig/twig v2.6.2 conflicts with roave/security-advisories[dev-master].
- Installation request for roave/security-advisories dev-master -> satisfiable by roave/security-advisories[dev-master].
- Installation request for craftcms/cms 3.1.17.2 -> satisfiable by craftcms/cms[3.1.17.2].
<warning>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.</warning>
Revert the Composer changes? (yes|no) [yes]:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment