Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Can't update Jetpack #781

Closed
mpeshev opened this Issue Sep 20, 2013 · 3 comments

Comments

2 participants
Contributor

mpeshev commented Sep 20, 2013

I've tried updating Jetpack on a local install from 2.0.2 to latest with

wp plugin update jetpack

After waiting for several minutes I got this message:

Warning: The package could not be installed. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature

This is coming from WP and the forums suggest that it's usually related to incorrect extract from the archive, usually due to the lack of disc space, but I have some 200 gigs here so it's not this.

It works for other plugins so it's not a permission issue as well.

This might be completely a WP/Jetpack issue, but wanted to note it as it could be due to some timeout or something like that (other plugins take 2-5sec to update).

Owner

scribu commented Sep 20, 2013

Can't reproduce:

User@air:wp$ wp core version
3.7-alpha-25000
User@air:wp$ wp plugin install jetpack --version=2.0.2
Installing Jetpack by WordPress.com (2.0.2)
Downloading install package from http://downloads.wordpress.org/plugin/jetpack.2.0.2.zip...
Unpacking the package...
Installing the plugin...
Plugin installed successfully.
User@air:wp$ wp plugin update jetpack
Success: Updated 1/1 plugins.
Enabling Maintenance mode...
Downloading update from http://downloads.wordpress.org/plugin/jetpack.2.5.zip...
Unpacking the update...
Installing the latest version...
Removing the old version of the plugin...
Plugin updated successfully.
Disabling Maintenance mode...

Does downloading the zip manually and running wp plugin install jetpack.2.5.zip work?

Contributor

mpeshev commented Sep 20, 2013

Now I think it might be related to the fact that wp-content is outside of the WP directory. It works for the other plugins and wp plugin list returns the results, but the installer says that the directory no longer exists.

It still works for the other plugins, maybe some edge case with timeout + trying to install in the wrong place after that.

Contributor

mpeshev commented Sep 20, 2013

I was able to update properly now, my only guess leaves the timeout issue with incomplete or wrong download after some time (when the connectivity is wonky and it takes longer to download).

@mpeshev mpeshev closed this Sep 20, 2013

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