Closed (fixed)
Project:
Drush
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Aug 2010 at 20:59 UTC
Updated:
6 Sep 2010 at 23:00 UTC
The location of this file has changed. This isnt killing aegir installs, it is killing ALL drush installs.
the url we have hard coded here : http://drupalcode.org/viewvc/drupal/contributions/modules/drush/includes...
has changed from http://cvs.php.net/viewvc.cgi/pear/Console_Table/Table.php?revision=1.28...
to http://svn.php.net/viewvc/pear/packages/Console_Table/trunk/Table.php?re...
Because php.net has switched from CVS to SVN.
This means we need to change this, and make a new release, or _ALL_ new drush installs are broken.
And I'm sorry, but the fact that we can't just include a single file in our code base is fucking ridiculous.
Comments
Comment #1
omega8cc commentedPatch submitted in http://drupal.org/node/875196
Comment #2
moshe weitzman commentedcommitted. we're going to have to issue new releases. what a drag.
Comment #3
oneguru commentedthanks guys!!! I realize its a drag but thanks! :)
Comment #4
skwashd commentedA work around for this is to use the PEAR installer to install Console_Table as released by PEAR before installing drush. "sudo pear install Console_Table" and it is done. This is also unlikely to break if PEAR ever switches to git or some other VCS.
Comment #5
onyxnz commentedIn my cPanel installation on my shared host, I needed to install Console Table in the Pear Packages, then modify drush.inc to add line 13:
include('/home/username/php/Console/Table.php');
before anything was working. Tried all versions of code, up to and including HEAD of 07-Aug-2010.
Hope this points someone else in the right direction.
Comment #6
oneguru commentedhow long does a new release take? all new installs of the aegir hosting platform as well as any other code dependent on the current release of drush will break.
Comment #7
seanrDrush does appear to report instructions for fixing the problem - it doesn't seem like it'd be too difficult for most Drush users to figure out until a release is posted. The maintainers said they're just backporting some critical patches before posting a release, so I'd expect one fairly soon.
Comment #8
moshe weitzman commentedFYI, I just issued a new release.
If you want drush to know when a new version of itself is available, see #425670: drush self update
Comment #9
oneguru commentedHey Moshe
Looks like this version of drush still has the same error, when you try to install aegir the two following error messages are received:
Drush command could not be completed.
An error occurred at function : drush_hosting_hosting_task
Let me know if there is something I can do differently.
Thanks
Jerry
Comment #10
oneguru commentedMoshe, Looks like we're good with the latest fix to Drush, I was able to install Aegir 0.4 Alpha 8 without a problem. Great Work! - Jerry
Comment #11
mstef commentedUpdated to drush 3.3 - still getting errors.
---------------------------------------------------
Comment #12
moshe weitzman commenteddelete includes/table.inc and then run a drush command. you have to run as a user that has write access to the drush files.
Comment #13
mstef commentedIf it's supposed to be deleted, why is it still in the 3.3 release (or is that release older than this issue)?
Comment #14
greg.1.anderson commentedYou've got an empty file cached there from when the bug was still in the codebase. You could also delete all of your drush files and get a fresh copy of drush, and the problem would go away. Deleting just the cached table.inc file is a faster way to fix it, though.
Comment #15
mstef commentedAh, got it. Thanks!
Comment #16
burt.lo commentedFor all the newbs (like me 20m ago)...
On shared hosting machines, where you and your site don't have complete control/access over the entire machine/configuration, you may have to do additional steps for a complete and successful installation of Drush.
Drush, as does Drupal, runs on PHP (PHP has two versions that are popular now, v4 and v5). PHP is installed for you on hosted machines, but some common extensions may not be. PEAR (PHP Extension and Application Repository) is a way to extend PHP abilities. In this case, Drush needs a "Console_Table" extension.
On Bluehost, using their cPanel, I scrolled to their "PHP PEAR Packages" section. When I clicked into that section, their cPanel did a quick diagnosis check to ensure everything was prepped for managing PEAR extensions. Once done, Bluehost gave me a form to "Install a PHP Extensions and Applications Package". I typed "Console_Table" and clicked "Install Now". This installed the Console_Table extension into my shared hosting configuration.
The last step was to follow post #5 from Onyx (above) where he told Drush where to find the Console_Table extension.
After this, Drush worked for me.
p.s. This post will likely be obsolete when Drush gets repackaged. I just felt compelled to spell out this explanation for others in the meantime.