Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I get the following output:
> drush up media-7.x-1.x-dev
Refreshing update status information ...
Done.
Update information last refreshed: Fri, 05/06/2011 - 10:32
Update status information on all installed and enabled Drupal projects:
Name Installed version Proposed version Status
Media 7.x-1.0-beta4 7.x-1.0-beta4 Specified version not found
Menu block 7.x-2.2 7.x-2.2 Up to date
Mollom 7.x-1.0 7.x-1.0 Up to date
No code updates available. [ok]
I'm not using git to handle packages, just svn for version control (which seems to work as expected when downloading or updating modules). It seems like whenever there's a new recommended release, drush is able to update the module without an issue. But when I want to specify the version that I want drush to update to, it doesn't work anymore (it used to work back before D7 was released).
Comment | File | Size | Author |
---|---|---|---|
#5 | drush-1149284.patch | 1.01 KB | jonhattan |
Comments
Comment #1
jonhattan7.x-1.0-beta4 is the latest supported release (see
drush pm-releases media
), so drush up won't update to 7.x-1.x-dev, you can "update" by dl'ing the release you want. In that case, when a new version of 7.x-1.x-dev is available, drush up will show a line like:Media 7.x-1.x-dev 7.x-1.x-dev Update available
Comment #2
jonhattanThat said, I've fixed a regresion we did introduce time back: it was converting dashes to underscores so media-7.x-beta3 was media_7.x_beta3. This problem is not present in 4.x series. http://drupalcode.org/project/drush.git/commit/66c2bcb
Also found other problem: if you have installed devel-6.x-1.20 and latest available version is devel-6.x-1.24 it is possible to specify
drush up devel-6.x-1.22
and drush will update to this intermediate version.I've realized it doesn't work in d7: it seems update.module now doesn't load the list of all available releases. Looking further into this. I also wonder what's going on with --security-only flag.
Comment #3
safetypinDrush used to be able to handle "updating" to any version of the module (or at least I thought that was what it was doing). I thought I could use the syntax I showed (*-7.x-*.*) to update a module to any official release version. I thought I even remembered drush rolling the db updates up and down. Was I misunderstanding what was happening? It sounds like (from what you said) that drush is not supposed to work like that.
Comment #4
jonhattanI was to say that media-7.x.1-x-dev is not a supported release but you're right @idlewilder. The problem is the same I describe in 2nd paragraph of #2.
Problem is that http://api.drupal.org/api/drupal/modules--update--update.compare.inc/fun... strips all the releases but the recommended one and we need all of them for this to work.
It is already fixed in master.
Comment #5
jonhattan... and needs to be ported.
@mark it is to be applied after #1002658: Drush does not correctly handle D7 project status queries.
Comment #6
msonnabaum CreditAttribution: msonnabaum commentedBackported. And just FYI, it looks like I needed #1023120 too.