Closed (fixed)
Project:
Drush
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
23 Jun 2009 at 07:22 UTC
Updated:
3 Jan 2014 at 00:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
hanoiiGot to this issue as well, patch works, although the same change was missing in the
version_control_post_install()function.Attached is the same patch with this other slight modification. Tried it and it works OK.
+1 for this to have it working ASAP.
Patch's against CVS
Comment #2
boinkster commentedI'm having the same problem even with the patch across several servers. With verbose on, I see that svn.inc gets included but no svn commands are executed. Maybe it's my setup: I have d6.13 under CVS and the sites dir under SVN. Does the entire install need to be under SVN for this to work?
Comment #3
hanoii@boinkster, have you tried the latest patch in this issue?
Comment #4
boinkster commentedYes, to no avail. Also tried on a test install that fully under SVN (not just files). Same thing, I can see that svn.inc is included but no SVN commands happen - no errors either:
If I call --version-control=svn AND --svnsync it throws these errors:
These were on my local windows box but I get the same behavior on remote 'nix server. Not sure where to troubleshoot. Am I using the correct syntax?
Comment #5
hanoiiYou are getting the same error on the linux machine? even the Fatal error: Call to undefined function version_control_post_install()?. I'd troubleshoot 'nix definitely, as windows i not 100% supported by drush.
Comment #6
boinkster commentedOkay, not the fatal error, but --svnsync doesn't run:
It is the same without the version-control call.
How would I track this down?
Comment #7
hanoiiI think I know what might be happening. I only tried this patch using dl or even updatecode command using a module that was already present in the SVN repository, and then, the code properly finds the .svn directory inside it. If you, which might be the case, execute a dl command with a new module being downloaded, I am almost possitive the function that validate if the source is being versioned by SVN will failed. I believe the check of .svn has to be made with the parent directory rather than the project one. I'll take a look at this patch and maybe improve it
Comment #8
boinkster commentedI confirmed this on a third server (CentOS). With the patch applied to HEAD, --svnsync works with updatecode but not with dl. I'll review the other servers on Monday to confirm.
Comment #9
zach harkey commentedI have tried everything and I can't get --svnsync or --svncommit to work with dl or updatecode to save my life.
I've tried the All-Versions-HEAD on both CentOS and MAMP stack: no dice.
Comment #10
hanoiiI had this issue in mind for a while. After noticing that dl was not working with the patch but updatecode was I looked at the patch and realized we thought things wrong. The version_control_is_versioned() should be checked against the path, and not against the actual project. Path would be the parent, which would be versioned for both new and updated code.
The part of the patch that prepends the path to the svn commands, I think it's still right.
Attached is a patch which I think fixes most issues.
Comment #11
lyricnz commentedI had this problem too, and the patch in #10 fixed it for me.
Comment #12
moshe weitzman commentedlooks reasonable. committed.