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.
Ever since upgrading my sites to Drush 5.5, I get the following (what I assume to be debug) output several times when running pm-update:
string(2) "?"
array(1) {
[1]=>
int(35615)
}
Example in context:
$ drush up --security-only
[...]
Security updates will be made to the following projects: Chaos tool suite (ctools) [ctools-6.x-1.9], Mime Mail [mimemail-6.x-1.1]
Note: A backup of your project will be stored to backups directory if it is not managed by a supported version control system.
Note: If you have made any modifications to any file that belongs to one of these projects, you will have to migrate those modifications after updating.
Do you really want to continue with the update process? (y/n): y
string(2) "?"
array(1) {
[1]=>
int(35615)
}
string(2) "?"
array(1) {
[1]=>
int(35615)
}
Project ctools was updated successfully. Installed version is now 6.x-1.9.
Backups were saved into the directory /home/mydomain/drush-backups/mydomain/20120809165203/modules/ctools. [ok]
string(2) "?"
array(1) {
[1]=>
int(35615)
}
string(2) "?"
array(1) {
[1]=>
int(35615)
}
Project mimemail was updated successfully. Installed version is now 6.x-1.1.
Backups were saved into the directory /home/mydomain/drush-backups/mydomain/20120809165203/modules/mimemail.
Settings initial status to 'minor' since functionality doesn't seem to be affected, it just has some extra output.
Comments
Comment #1
Larry Jones CreditAttribution: Larry Jones commentedI see the same error when simply running drush status:
Reverting to drush 5.4 until this is fixed.
Comment #2
jonhattanI'm sorry. It's now fixed in master.
Comment #3
stewart.adam CreditAttribution: stewart.adam commentedThanks!
For those wanting to patch this away, here's a direct link to the commit's diff: http://drupalcode.org/project/drush.git/patch/48f3a4a:/includes/drush.inc
Comment #4
Joel MMCC CreditAttribution: Joel MMCC commentedI just upgraded to 7.x-5.5 via “drush dl drush --select” (using 7.x-5.4) this morning, almost ¾ of a day after #2 when @jonhattan said that it was fixed in master. I get the debug strings as well.
Does “fixed in master” not mean that it’s fixed in the version that “drush pm-download” would access?
Comment #5
stewart.adam CreditAttribution: stewart.adam commentedFixed in master means it's in the git repository and will be included in the next stable release. You can use the latest dev release to get the patch included or patch your 5.5 installation manually using the patch link above.