Skip to content

Conversation

@danielbachhuber
Copy link
Member

Hopefully this fixes:

 Problem 1
    - Installation request for wp-cli/package-command dev-2a4ac19b859ac77c92e60efc972e539c6b834fb1 -> satisfiable by wp-cli/package-command[dev-2a4ac19b859ac77c92e60efc972e539c6b834fb1].
    - wp-cli/wp-cli dev-master requires wp-cli/package-command ^1.0 -> satisfiable by wp-cli/package-command[v1.0.0].
    - Can only install one of: wp-cli/package-command[v1.0.0, dev-2a4ac19b859ac77c92e60efc972e539c6b834fb1].
    - Installation request for wp-cli/wp-cli dev-master -> satisfiable by wp-cli/wp-cli[dev-master].

From https://travis-ci.org/wp-cli/package-command/jobs/213828196
Related wp-cli/package-command#2

@danielbachhuber
Copy link
Member Author

@schlessera Does this seem sensible to you?

@schlessera
Copy link
Member

No, this should be handled with the following set of Composer options:

	"minimum-stability": "dev",
	"prefer-stable": true,

@danielbachhuber
Copy link
Member Author

No, this should be handled with the following set of Composer options

Like 46995f2 ?

@schlessera
Copy link
Member

Yes. That should have the same effect, using the latest matching stable as far as possible, and falling back to dev-master if no stable fits the requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants