Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I'm getting some errors with select modules, I can't tell if it's an issue with the module or drush. Drush successfully updates some modules, such as views, but is unable to update other modules such as taxonomy_csv and rules. I get the following output:
Code updates will be made to the following projects: Rules [rules-6.x-1.4]
Note: A backup of your project will be stored to backups directory if it is not managed by a supported version control system.
Note: If you have made any modifications to any file that belongs to one of these projects, you will have to migrate those modifications after updating.
Do you really want to continue with the update process? (y/n): y
Password:
Password:
Unable to checkout rules from cvs.drupal.org. [error]
Project rules was updated successfully. Installed version is now 6.x-1.4.
You should consider committing the new code to your Subversion repository.
If this version becomes undesireable, use Subversion to roll back.
Drush was unable to get the svn status on /Users/Matthew/The Institute/tuci.d6/sites/all/modules/contrib-stable/rules. Check that you have Subversion [error]
installed and that this directory is a subversion working copy.
The specific errors are below:
svn: '/Users/Matthew/The' is not a working copy
svn: '/Users/Matthew/The' does not existThe issue is that it says the project is updated successfully, but then the module displays as being out of date. I included the full message because drush is seemingly unable to get the svn status of the module code. One of the parent directories does have a space, as can be seen in the error message, and the svn error seems to be because drush is not properly escaping the space in the file path.
I'll try renaming the directory to not have a space in the name and see if this resolves the CVS checkout issue.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | drush-1019148.patch | 4.8 KB | jonhattan |
Comments
Comment #1
safetypinRemoving the space from the file path resolved the svn status error, but did not resolve the cvs checkout error:
Comment #2
safetypinMost recently, this is affecting drupal core in addition to the two modules I mentioned earlier. Drush seems to download some supporting directories and files from CVS, but doesn't update everything properly.
Now that I think about it, is this because I didn't initially check these modules out from CVS? If that's what's happening, I know what to do for the modules, I think I just remove the module code from svn and download the module with drush again. But, how do I do that for drupal core? Do I remove all directories, make a backup copy of the sites directory and drush dl drupal? Or do I need to do a site-install?
Comment #3
jonhattanNow that I think about it, is this because I didn't initially check these modules out from CVS?
No. drush will do
cvs updateorcvs checkoutdepending on this.paste the full output with --debug so we can examine in detail what's happening.
Also: you've fixed the space in the path but perhaps you are working under /users/matthew (lowercase) and drush is wanting the uppercase directory. This has been reported in the past by mac users.
Comment #4
safetypinHere's the full debugging output:
Comment #5
jonhattanOP and comment #1 seems to me a temporary problem in cvs services. But there's still a problem with whitespaces in the path. From #4:
It was already fixed for bzr in http://drupal.org/cvs?commit=472080. Same fix for svn is attached. Also minor fixes in cvs package handler to catch bug in #1.
Comment #6
safetypinI attempted to apply the patch in #5, and I've looked through the modified files and can see the changes implemented in the patch, I'm still seeing the svn status -u warning: '/Users/Matthew/The' is not a working copy. I just changed the parent directory name to remove the space, and I continue to get the error about updating the module/theme from CVS.
However, after looking through the debug output again, it seems like the problem is that I started out with a non-cvs checkout of Drupal core, the fusion base theme, and a couple of other modules. I know I started this site out before configuring drush to use CVS, so I'm sure that's what did it. Whenever I just run the cvs checkout/update command, it tells me to "move away" all the files for that module.
So, I guess this means that the functionality to overwrite code that isn't CVS isn't completing properly for me. Could this be a permissions issue? I can handle this pretty easily for contributed modules, but I'm not sure how best to handle this for drupal core.
Comment #7
moshe weitzman CreditAttribution: moshe weitzman commented#5 looks ok to commit. did not review that thoroughly.
idlewilder - perhaps your best bet is to checkout a new drupal core from cvs and then copy your sites dir into it and then delete your existing web site and move the newly prepared one into it.
Comment #8
safetypinMy work around at the moment is to stop checking things out from CVS and use drush with wget. If drush can preserve my subversion information using wget, then I'm not sure what the advantage of checking out the data from CVS instead of downloading the files from wget.
The issue of drupal core was that I have the entire site under subversion control, so I'm not sure how to preserve file history of the core files. Switching drush's package handler to wget allowed me to successfully update drupal core and preserve the subversion information, so I'm happy with that. As long as I don't have a compelling to use CVS, I think I'll just leave it alone.
Comment #9
jonhattancommitted.