-
Notifications
You must be signed in to change notification settings - Fork 1k
Closed
Description
Bug Report
$ wp package install wp-cli/i18n-command
[...]
Dependency resolution completed in 0.002 seconds
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires wp-cli/i18n-command dev-master, found wp-cli/i18n-command[dev-fix/adapt-branch-alias, dev-main, dev-gettext-5, v2.0.0, v2.0.1, v2.0.2, v2.0.3, v2.1.0, v2.1.1, v2.1.2, v2.2.0, v2.2.1, v2.2.2, v2.2.3, v2.2.4, v2.2.5, v2.2.6, v2.2.7, v2.2.8, v2.2.9, v2.2.10, v2.2.11, v2.2.12, v2.2.13, 2.x-dev (alias of dev-main)] but it does not match the constraint.
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.
---
Error: Package installation failed (Composer return code 2).
git clone -b master https://github.com/wp-cli/i18n-command
Cloning into 'i18n-command'...
fatal: Remote branch master not found in upstream origin
These renamings (#5598) (happening for totally futile pretexts) are causing actual trouble to developers (who are the primary audience of such a software)
Metadata
Metadata
Assignees
Labels
No labels