Satis fails to build if package is moved within SVN respository

[JostBaron]

I have some project in a SVN repository. The directory structure looks like this:

$svn-root/project/
      - trunk
          - composer.json
          - ...
      - branches (empty)
      - tags (empty)

Now I created the folder $svn-root/sub/, and moved $svn-root/project/ into sub/, using svn mv project/ sub/ and committing afterwards. Now, the revision is XXX. I updated my satis configuration file to contain the new path $svn-root/sub/project.

But now, I can't update my satis repository anymore (even after deleting the outputs and caches), because satis tries to download the composer.json at the revision when it was last changed, which was before the directory move, but from the new location.

If the composer.son was last changed in revision YYY, satis executes this command:

Executing command (CWD): svn cat --non-interactive  --username '...' --password '...'  '$svn-root/sub/project/trunk/composer.json@YYY'

This fails, since in revision YYY the file is still located at $svn-root/project/trunk/composer.json.

[alcohol]

I honestly forgot pretty much everything I knew about SVN. It has been over 6 years since I last used it. So not sure I can be of any help here.

The command you included though, is that from a satis build output? Or a composer install?

[JostBaron]

The command is from a satis build.