This might be a drupal bug. I am using git to deploy all contributed modules (as submodules). I am at the latest dev versions for migrate and wordpress_migrate as of today (05/02/2012).

I've added the git_deploy contributed module which takes care of fetching release information for the modules. The modules page shows no dependency errors after enabling git_deploy. However, update.php will not execute since it believes the dependency has not been met. The only way I could get around this was to leave off the (>2.3) version requirement on the dependencies statement for migrate in the wordpress_migrate.info file.

Comments

mikeryan’s picture

Yes, I've seen this too, haven't looked too closely yet - I'm imagining the problem is in git_deploy, but I could be wrong.

mikeryan’s picture

David4514’s picture

@mikeryan -- It looks like a can of worms! I'll keep watching for a solution. I assume, for the moment, I can just remove the version dependency from the wordpress_migrate.info file, run update.php, then put the version dependency back in the .info file.

mikeryan’s picture

Status: Active » Closed (won't fix)

The only thing we could do about this on our end, as far as I can tell, is remove the dependency on the version, which would cause pain for people trying to use Wordpress Migrate with Migrate 2.3 or earlier. The problem is only going to occur for those of us using a git clone of Migrate, and even then I think it would only happen on a local development environment where $_SERVER['REMOTE_ADDR'] is not defined. I.e., it would only happen to people like us who are perfectly capable of working around it by temporarily removing the version dependency from the .info file. Therefore, I'm marking this "won't fix".

mikeryan’s picture

Status: Closed (won't fix) » Active

This was reraised for Migrate Extras (#1791178: Problems with dependency of migrate module and cloning from http://git.drupal.org), and looking at the Migrate installation stats, with 70% of Migrate installs being on 2.4 or later, maybe we can go without the version check.

mikeryan’s picture

Status: Active » Fixed

Done.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.