Drush broken - a "no" answer to the unethical "Do you want to update drush 4.5 to 5.4" when using drush updated anyways.

Now I cannot use drush or aegir properly - and this is the 2nd time you guys have done this in the last few months. You have not tested drush 5.4 on my server, so you shold not have the right to force users to upgrade to 5.4 like you are doing. It is a huge problem, and you should not be allowed to put that upgrade notice in all drush commands. Users should have to manually update drush.

I am now getting Fatal Errors Cannot redeclare class DrushMakeProject_Core

Why do you guys keep on doing this? It is wrong and harmful to force drush upgrades on uers.

Comments

webmaster-eddie’s picture

webmaster-eddie commented
Title: Drush broken - a "no" answer to the unethical "Do you want to update drush 4.5 to 5.4" when using drush updated anyways. » Fatal Error: Cannot redeclare class DrushMakeProject_Core
Version: 7.x-4.5 » 7.x-5.4

I did not want to or try to upgrade my working drush from 4.5 to 5.4 - you guys forced it on me, AGAIN.

Now there are errors: Fatal Error: Cannot redeclare class DrushMakeProject_Core

webmaster-eddie’s picture

webmaster-eddie commented

Update and additional information:

The command that aborted was updb - a database update, and I still cannot use drush successfully to run that command.

It appears that cc all and core-cron are working properly

webmaster-eddie’s picture

webmaster-eddie commented
Version: 7.x-5.4 » 7.x-4.5
Priority: Critical » Minor
Status: Active » Fixed

This problem appears to have gone away magically after 15 minutes and 10 failed drush updb commands on 3 different sites. In fact, although the terminal return told me that drush 5.4 downloaded anyways (after I answered "no" to the querry to update drush), I am , it appears, still using drush 4.5 on my server. SO i have re-classified as a 4.5 phenomena - which corrected itself, after 4 cc all's on a few different sites. My mistake, perhaps, but the terminal return was misleading, and I as aegir user could not update any site's database from the command line. In fact the error went away when I tried it on the only D6 site I run, my aegir hostmaster platform site. After drush updb ran successfully for the first time on the aegir hostmaster site, then I no longer had problems on the D7 platform sites (at least not on the 3 I have tested so far). So I am listing this as fixed.

webmaster-eddie’s picture

webmaster-eddie commented

Actually the problem only went away on all sites BUT the site I was working on when drush 5.4 did download in to a separate drush folder in that particular site/modules/.

I had to delete that drush directory and all files in it to return to the standard drush command line functioning for that site only.

Status: Fixed » Closed (fixed)

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