# Versions
OS: OS X 10.5.8
Drush: Latest head as of 2009/10/15

# Details

I was upgrading emfield and exploring the svn commit feature and noticed my commits were broken after the update. After some poking around I realized that this particular update of emfield had renamed changelog.txt -> CHANGELOG.txt which was interpreted as adding a new file called CHANGELOG.txt and removing a file called changelog.txt. I am running on OS X using a case sensitive filesystem. Drush adds the new file as it should but then runs a svn remove on the old file which doesn't seem to be a case sensitive operation (maybe an issue with svn in os x) which then removes the newly added file leaving SVN in a state where it wants to add a file but it is missing.

# Example

drush updatecode emfield --version-control=svn --svnsync -v

...

Project emfield was updated successfully. Installed version is now 6.x-1.11.
Backup skipped because .svn directory was detected. Use Subversion to revert if needed.
Executing: svn status /.../sites/all/modules/emfield

...

? /.../sites/all/modules/emfield/contrib/emthumb/CHANGELOG.txt
! /.../sites/all/modules/emfield/contrib/emthumb/changelog.txt

...

Executing: svn add /.../sites/all/modules/emfield/contrib/emthumb/CHANGELOG.txt
A /.../sites/all/modules/emfield/contrib/emthumb/CHANGELOG.txt
Executing: svn remove /.../sites/all/modules/emfield/contrib/emthumb/changelog.txt
D /.../sites/all/modules/emfield/contrib/emthumb/changelog.txt

....

svn status

D /.../site/all/modules/emfield/contrib/emthumb/changelog.txt
! /.../site/all/modules/emfield/contrib/emthumb/CHANGELOG.txt

At this point CHANGELOG.txt or changelog.txt no longer exist.

Comments

ducdebreme’s picture

subscribing

greg.1.anderson’s picture

Version: » 8.x-6.x-dev
Component: Code » Base system (internal API)
Status: Active » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If desired, you may copy this bug to our Github project and then post a link here to the new issue. Please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.