make svn based dependencies work flawless if project itself is svn managed

[Flyingmana]

Had just a case in irc composer-dev, where a install/update of a package did fail with an

Package could not be downloaded, svn: E155000: Revision 4782 doesn't match existing revision 3152 in ....

problem occurred, because the project itself is managed via svn and the dependency got fetched via svn, too.
I assume some conflict with how svn manages external svn repositories inside of an project.

full paste of composer install -vvv:
http://pastebin.com/6LggFrMc

[thekabal]

This was inside an install of the SVN version of Blacknova Traders (available at sourceforge). After much struggling, I followed Flyingmana's advice, and made a "clean" directory for composer outside of the project, and grabbed the latest versions that way. It worked! I then copied over the vendor directory from the "clean" composer directory, and after a few struggles with SVN, I was able to update the project to the latest versions.

Hope this helps someone else determine a cause and maybe a solution!

[oliver-graetz]

I suppose that your problem came from trying to use a package of the "svn" type inside another repository. Composer will then checkout another repo inside your repo which leads to "obstructing working copy" and other strange problems.

The clean solution: You should set svn:ignore for your vendors directory and not try to commit its contents to the outer SVN repo. Instead, you use composer install not only on your development machine but also on the deployment server.

But this doesn't help if you don't have command line access on the deployment machine and cannot run composer install there. This is why some people including me have demanded an SvnExportDownloader (#1716) to be provided. You could vote for that issue.

[Seldaek]

See https://packagist.org/packages/linearsoft/composer-svn-export which hopefully fixes it.