Hi
Trying to upgrade a D6 website, I run drush site-upgrade @go inside the D6 repertory.

Got a long list of warnings like

The project video has no releases in version 7 [warning]
The project views has no releases in version 7 [warning]
The project views_accordion has no releases in version 7 [warning]
The project views_attach has no releases in version 7

which is... strange as of course, there's a D7 version of those modules

Any help welcome
Best regards
D

CommentFileSizeAuthor
#2 D7.txt12.37 KBdbourrion
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

greg.1.anderson’s picture

greg.1.anderson CreditAttribution: greg.1.anderson commented

When you get to the upgrade report, does it contain the correct D7 release for all of those modules?

dbourrion’s picture

dbourrion CreditAttribution: dbourrion commented
FileSize
D7.txt12.37 KB

Hi
Here's all I got (see d7.txt joined)
Thx for help.
D

greg.1.anderson’s picture

greg.1.anderson CreditAttribution: greg.1.anderson commented
Status: Active » Postponed (maintainer needs more info)

My guess is that Drush is having trouble calling back in to Drush in your configuration. Drush Site Upgrade does this for many purposes, including determining the available releases for the upgrade path. With this configuration problem, you should also find that in Drush core, that pm-update does not call updatedb as it should, and that sql-sync cannot determine the source and destination database settings unless you copy them into your alias record.

I'm not sure why Drush cannot call back into Drush; this used to happen frequently in the past when folks would make a shell alias for the 'drush' command, and not include the --php and --php-options flags that the standard 'drush' script provides to drush.php. Calling drush.php directly via a shell alias, as was recommended in Drush 3's README.txt, is now a deprecated technique. I presume you are using Drush 5.8 or Drush 6.x-dev?

Run your command again with --debug and post the result.