Fatal error: Class 'Spyc' not found in phar:///usr/local/bin/wp/vendor/wp-cli/mustangostang-spyc/includes/functions.php on line 31 about doctor-command HOT 12 CLOSED

Which WP-CLI version are you running?

from doctor-command.

1.4.1, updated to reflect this.

I'm trying to build a 1.5.0 now to see if the problem goes away.

from doctor-command.

There were a couple prior instances of this but I can't recall the source:

• #111
• wp-cli/package-command#12
• https://github.com/issues?utf8=%E2%9C%93&q=org%3Awp-cli+sort%3Aupdated-desc+spyc+

from doctor-command.

Heh, you're better at searching github than I, I couldn't find shit. I should probably learn the search terms.

from doctor-command.

yeah it's still broken with 1.5.0

from doctor-command.

Oh, I see. It looks like you're running doctor v0.1.0. Can you update doctor to latest with wp package update?

from doctor-command.

Hmm. it shouldn't be that version. I did a clean removal and reinstall in my repo before building the RPM. It's pulling from dev-master.

Maybe my build is broken. Will look into that.

from doctor-command.

Yeah, 0.1.0 is what it's reading as the current version:

# export WP_CLI_PACKAGES_DIR=/opt/wp-cli-plugins ; /usr/local/bin/wp --allow-root package update
Using Composer to update packages...
---
Loading composer repositories with package information
Updating dependencies
Resolving dependencies through SAT
Dependency resolution completed in 1.086 seconds
Analyzed 5357 packages to resolve dependencies
Analyzed 311446 rules to resolve dependencies
Package operations: 0 installs, 0 updates, 0 removals
Generating autoload files
---
Success: Packages updated.
# export WP_CLI_PACKAGES_DIR=/opt/wp-cli-plugins ; /usr/local/bin/wp --allow-root package list
+------------------------+------------------+------------+-----------+----------------+
| name                   | authors          | version    | update    | update_version |
+------------------------+------------------+------------+-----------+----------------+
| wp-cli/doctor-command  | Daniel Bachhuber | v0.1.0     | available | dev-master     |
| wp-cli/profile-command |                  | dev-master | available | dev-master     |
+------------------------+------------------+------------+-----------+----------------+

Is this not accurate?

from doctor-command.

Is this not accurate?

Nope. You'll need to update wp-cli/doctor-command to the latest dev-master because the fix hasn't been included in a tagged release yet.

from doctor-command.

How do I update to dev-master? Doing package update leaves me on v0.1.0, as shown in my previous comment.

from doctor-command.

Can you try WP_CLI_PACKAGES_DIR=/opt/wp-cli-plugins wp package install wp-cli/doctor-command, to force a re-install without a version constraint? It seems like there might be a version constraint in your /opt/wp-cli-plugins/composer.json file.

from doctor-command.

Yep that was it. Somehow the composer.json wasn't being updated by my rpm. All set now.

Thanks much for the assist.

from doctor-command.