The module I'm trying to update is image_fupload dev snapshot. I already have a snapshot installed from sept 21, but the current snapshot is from sept 29. So there's new code in the module but the version number remains the same.

When I run drush update image_fupload-6.x-3.x-dev it tells me the versions of all my modules and lists this module as such:

 Image FUpload                 6.x-3.x-dev     6.x-3.x-dev     Specified version already installed

Then it tells me that no code updates are available. This is the case with other modules too, this is just the example I chose. Is there any way to force drush to update the code even though the version is still the same?

Comments

frankcarey’s picture

frankcarey commented

same issue: cvs_deploy and update_module have the date information, and suggest even dev updates based on new dev snapshots. Is there any fundamental limitation to be able to do this in drush?

Shai’s picture

Shai commented

I'm new to Drush, so I can't answer regarding what Drush is supposed to do.

However, a very fast workaround for the problem would be to delete the module and then download it.

Shai

hadsie’s picture

hadsie commented

Deleting the module folder and re-downloading with drush isn't really an option for me as all my code is stored in subversion. So deleting the module directory would also delete my subversion files. Basically leaves me in the same place where I need to manually move the .svn files over and any patches I've applied to the module, which is what I'm doing now.

brad.bulger’s picture

brad.bulger commented

as a workaround, you can explicitly download the version - drush dl image_fupload-6.x-3.x-dev - and you should get the current release. i've also got the modules in Subversion and do this all the time. plus you should then be able to use svn diff to confirm that in fact you have new code.

hadsie’s picture

hadsie commented
Status: Active » Fixed

thanks brad. I was using the update command previously, and dl does indeed update the existing code as well.

frankcarey’s picture

frankcarey commented
Status: Fixed » Active

this is really more of a workaround than a final solution, marking as active.

fletchgqc’s picture

fletchgqc commented
Status: Active » Closed (duplicate)

I think this is a duplicate of #346183: pm update to specific version fails with dev?

geerlingguy’s picture

geerlingguy commented
Status: Closed (duplicate) » Active

Doesn't seem to be a duplicate.

This issue has to do specifically with -dev releases, which are not updated if you use the 'drush up' command, even if a newer -dev release is encountered. I think it would be much more convenient if drush would update a dev release if you explicitly identified the release in the up command, like so:

drush up backup_migrate-6.x-2.x-dev

greg.1.anderson’s picture

greg.1.anderson commented

I think that drush dl backup_migrae-6.x-2.x-dev does what you suggest.

geerlingguy’s picture

geerlingguy commented

True... but then I still have to manually do a drush updatedb afterwards... I think it would be more intuitive to allow users to do an explicit 'up' to get the latest dev release...

greg.1.anderson’s picture

greg.1.anderson commented

Well, until it does, you've got a reasonable workaround...

jonhattan’s picture

jonhattan
Primary language Spanish
Location Plasencia
commented
Component: Code » PM (dl, en, up ...)
Status: Active » Fixed

It is already fixed. Now there's a date based check.

 Content Construction Kit (CCK)                          6.x-3.x-dev        6.x-3.x-dev       Update available

Status: Fixed » Closed (fixed)

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