*edit*
Nevermind.
The below didn't fix it... drush dl --select gave the error, while drush dl didn't.
For other who find this: A custom module, non d.o, was missing the version= line in its info file.
*/edit*
While using drush I got this error: #1043038: Error while trying to find the common path for enabled extensions of [error] project fusion. Base Theme and Sub Theme separate.
Except instead of fusion it was from taxonomy_csv
This module is located at sites/some_site/modules/taxonomy_csv , and using 'drush pm-download' in sites/some_site/ gives the above error. After I removed the first 'project=taxonomy_csv' line from the top of the .info file drush worked normal again.
This is from the documentation:
http://drupal.org/node/542202
project (Discouraged, packaging use only)
Module maintainers should not use this at all. The packaging script on drupal.org will automatically place a string here to identify what project the module came from. This is primarily for the Update status module, so that Drupal installations can monitor versions of installed packages and notify administrators when new versions are available.
Comments
Comment #0.0
jhr commenteddrush dl != drush dl --select
Comment #1
jhr commentedOnly way to change the title...
Comment #2
Daniel_KM commentedHi,
Thanks, I removed this line from the info file.
However, I can't reproduce your error, whether with
drush dl --select taxonomy_csvordrush dl taxonomy_csv. It's probably related to my Drush version (4.5, the current Debian one). I wait for the Drush 5.x release on Debian to check one more time.Sincerely,
Daniel Berthereau
Infodoc & Knowledge management
Comment #3
jhr commentedYea...
Sorry, crappy testing on my part.
I tracked it down to a custom module without version in it's .info file. It was in the same subsite as taxonomy_csv.
After I found the 'project' line issue above, this was the first module I found w/ duplicates, but later found like 5 or 6 more.
BTW, it was 'drush dl some_other_module(not taxonomy_csv) --select' that gave the error. Drush builds a list of other modules, or something and the 'version'-less .info file was causing the error.
Comment #4.0
(not verified) commentednvm git_deploy only works with modules checkedout from d.o