Problem/Motivation

If the current site uses Drupal 6, then the installation instructions$ drush dl drush_sup
recommended in README.txt fail because drush looks for a 6.x release of drush_sup.

Proposed resolution

Update the instructions in README.txt: either$ drush dl drush-sup-7.x-2.x --select
as recommended in #3 or$ drush @none dl drush_sup
as suggested in #4.

Remaining tasks

Wait until the maintainer decides to make a new release.

This issue has been fixed. The instructions in #3 have been added to README.txt, as you can see by downloading the project using git. As soon as there is a new release, its README.txt will include these instructions.

Please do not re-open this issue (as in #6) in the hope of getting the updated instructions into the packaged README.txt. If you feel that the suggestion in #4 is simpler/better than the one in #3, please think about whether it makes enough of a difference to be worth re-opening the issue.

User interface changes

Update README.txt.

API changes

None.

Original report by benjifisher

The command
drush dl drush_sup
recommended in README.txt fails because my current Drupal site is 6.x and so drush looks for a 6.x release of drush_sup.

The attached patch to README.txt recommends checking the project page for the current version and then running something like
drush dl drush_sup-7.x-2.0
instead. (This seems to work today even though the current version is 7.x-2.0-beta1.)

CommentFileSizeAuthor
drush_sup-install.patch575 bytesbenjifisher

Comments

greg.1.anderson’s picture

greg.1.anderson commented
Status: Needs review » Fixed

The provided instructions will work fine if you run them from your home directory. I updated the README.txt on the 7.x-2.x branch to more fully explain the installation options.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Status: Fixed » Needs work

I tried the instructions from the new README.txt while I was in a D6 directory:

$ drush dl drush_sup-7.x
No release history available for drush_sup 6.x.
$

That is why I suggested drush dl drush_sup-7.x-2.0 in my patch.

It does work as expected from my home directory, so that part of the instructions is an improvement.

greg.1.anderson’s picture

greg.1.anderson commented
Status: Needs work » Fixed

You are correct -- drush_sup-7.x does not work from within a Drupal 6 site; even default-major=7 does not work. I changed the recommendation to drush dl drush-sup-7.x-2.x --select to avoid the warning message (and so that the command is still accurate when there is a 2.1 release).

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented

OK, that works. I found another solution, directly addressing the cause of the problem (that I am doing it from a D6 directory):

$ drush @none dl drush_sup
Project drush_sup (7.x-2.0-beta1) downloaded to                      [success]
/home/drupal/.drush/drush_sup.
Project drush_sup contains 0 modules: .
$

(Yes, my user name is drupal.)

Status: Fixed » Closed (fixed)

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

dhigby’s picture

dhigby commented
Category: bug » task
Status: Closed (fixed) » Needs work

Forgive me for re-opening this, but I was looking all over for the answer to why I couldn't install drush_sup and finally found the answer here and not in the README.txt file.

Please include benjifisher's installation command in the readme and on the project page:

drush @none dl drush_sup

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Status: Needs work » Reviewed & tested by the community

@dhigby:

The solution described in #3 has already been committed. Unless you downloaded the project using git (some time after 10/11/2012) it will not be in the README.txt file on your system, but going forward, there will be a new release (sooner rather than later, we hope) and from then on anyone who downloads the tarball will have that set of instructions. So the problem is as fixed as it is going to get in this forum. You can see the git version of README.txt here: http://drupalcode.org/project/drush_sup.git/blob/refs/heads/7.x-2.x:/REA... (link from the project page). Come to think of it, I can claim some credit for that: see #1809090: Update links on the project page..

Naturally, I agree that my solution in #4 is simpler than the one that got committed in #3, but I did not think it was worth re-opening the issue. Maybe if I mark the issue RTBC, one of the maintainers will take notice.

Short version: drush @none dl drush_sup is simpler than drush dl drush-sup-7.x-2.x --select.

Erich Schulz’s picture

Erich Schulz commented
Status: Reviewed & tested by the community » Active

I'm on drush 5.8 - I had to use @none:

antarqld@bsd34:~$ <strong>drush dl drush_sup</strong>
No release history available for drush_sup 6.x.                                     [warning]
antarqld@bsd34:~$ <strong>drush <em>@none</em> dl drush_sup</strong>
bzr: not found
Project drush_sup (7.x-2.0-beta1) downloaded to                                     [success]
/hsphere/local/home/antarqld/.drush/drush_sup.
Project drush_sup contains 0 modules: .
benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Status: Active » Fixed

This issue has been fixed. See #3 and 191a1a3. If you disagree, please read the issue summary (which I just added) before reopening this issue.

greg.1.anderson’s picture

greg.1.anderson commented

I talked with moshe about this at BADcamp, and concurred that using @none is a bit odd. Naming the specific version is better, but takes more typing. I think that the advice in the currently checked-in README.txt is clear; I added a brief section on installation on the project page that recommends cd'ing to your home directory before downloading drush_sup.

Thanks for all of the feedback.

Status: Fixed » Closed (fixed)

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

Anonymous’s picture

(not verified) commented
Issue summary: View changes

Add an issue summary to discourage people from reverting the status.