There seems to be a circular dependency problem upgrading form CE to CE

When I try to upgrade Mag_Core_Modules from to, it complains:

Checking dependencies of packages

CONNECT ERROR: Package community/Lib_Google_Checkout conflicts with: community/Mage_Core_Modules

Checking dependencies of packages
Already installed: community/Lib_Varien, skipping
Already installed: community/Lib_Js_Calendar, skipping
Already installed: community/Lib_Js_Mage, skipping
Already installed: community/Lib_Phpseclib, skipping
Already installed: community/Mage_Locale_en_US, skipping
Already installed: community/Lib_Magento, skipping
Already installed: community/Lib_Credis, skipping
Already installed: community/Lib_Pelago, skipping
Already installed: community/Lib_ZF, skipping
Already installed: community/Lib_Js_Prototype, skipping
Already installed: community/Lib_ZF_Locale, skipping

CONNECT ERROR: Package community/Mage_Core_Modules conflicts with: community/Aramex_Shipping_Tracking_API 2.0.1
Package community/Lib_Google_Checkout conflicts with: community/Mage_Core_Modules
Package community/Lib_Mage conflicts with: community/Mage_Core_Modules

I'm not bothered by Aramex at this stage, but when I try to upgrade Lib_Google_Checkout, it can't because of the conflict with Mag_core

Could this mean that Aramex blocks the upgrade to Mage_Core_Modules, and the whole thing cascades from there?

1 Answer 1


Google checkout was discontinued awhile back, I'd say you're safe with wiping it or forcing/skipping it.

Google Checkout has been retired. You can no longer process orders. The last day to process refunds will be December 20, 2013.

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.

  • There are significant hacks in our code, so overwriting is not the route for me. I've tried to remove lib_google_checkout, but it claims it is needed by Magento. I'm making a copy of the VM to play with so I can figure out what to do and I'll report back when I have a result.
    – Lifeboy
    Nov 25, 2014 at 12:12
  • 1
    If there are hacks, then Connect will most likely overwrite them. I would do a diff to compare and re-apply (without core hacks, obviously to avoid these headaches in the future)
    – B00MER
    Nov 25, 2014 at 12:14
  • Thinking about this: The hacks are done correctly, ie, they are not changes to core files, but additional files in the right directories. I guess then whether I upgrade with connect or do it from the shell, the changes will stay. I'll first try it on my test copy and see how it works.
    – Lifeboy
    Nov 25, 2014 at 12:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.