There seems to be a circular dependency problem upgrading form CE 1.9.0.1 to CE 1.9.1.0.
When I try to upgrade Mag_Core_Modules from 1.9.0.1 to 1.9.1.0, it complains:
Checking dependencies of packages
CONNECT ERROR: Package community/Lib_Google_Checkout 1.9.1.0 conflicts
with: community/Mage_Core_Modules 1.9.0.1Checking dependencies of packages
Already installed:
community/Lib_Varien 1.9.1.0, skipping
Already installed:
community/Lib_Js_Calendar 1.51.1.1, skipping
Already installed:
community/Lib_Js_Mage 1.9.1.0, skipping
Already installed:
community/Lib_Phpseclib 1.5.0.0, skipping
Already installed:
community/Mage_Locale_en_US 1.9.1.0, skipping
Already installed:
community/Lib_Magento 1.9.1.0, skipping
Already installed:
community/Lib_Credis 1.8.0.0, skipping
Already installed:
community/Lib_Pelago 1.9.1.0, skipping
Already installed:
community/Lib_ZF 1.12.7.0, skipping
Already installed:
community/Lib_Js_Prototype 1.7.0.0.5, skipping
Already installed:
community/Lib_ZF_Locale 1.12.7.0, skippingCONNECT ERROR: Package community/Mage_Core_Modules 1.9.1.0 conflicts
with: community/Aramex_Shipping_Tracking_API 2.0.1
Package
community/Lib_Google_Checkout 1.9.1.0 conflicts with:
community/Mage_Core_Modules 1.9.0.1
Package community/Lib_Mage
1.9.1.0 conflicts with: community/Mage_Core_Modules 1.9.0.1
I'm not bothered by Aramex at this stage, but when I try to upgrade Lib_Google_Checkout 1.9.1.0, it can't because of the conflict with Mag_core
Could this mean that Aramex blocks the upgrade to Mage_Core_Modules 1.9.1.0, and the whole thing cascades from there?
Best Answer
Google checkout was discontinued awhile back, I'd say you're safe with wiping it or forcing/skipping it.
Also (if your core codebase is not hacked to bits) I wouldn't recommend upgrading via Magento Connect and would do it manually via shell, or simply overwriting the new codebase from a fresh install.