Identifying conflicts with package folders during a Salesforce DX migration.
After changing my preferences in Versions, I thought everything was good to go. That is, until I started receiving the following error after every successful commit:
This error message was rather cryptic, and gave me absolutely no help (nor did searching the internet). I tried many different things, including manually going into the checked out SVN repository to try to run clean up, but nothing resolved it. However, when I tried to clean up the repository, it gave me an error about my SQLite library being too old. I proceeded to update that with homebrew, but then got another error:
Error code 155037: Error bumping revision post-commit
Interestingly (or, as you may infer from the error message), the commits did succeed, but there was an issue locally incrementing the revision number. Unfortunately, this seemingly innocent message also meant that the .svn folder somehow got corrupted, as Versions could not even display the folder hierarchy anymore. My only real course of action was to delete the repository and re-check it out each time (saving my Force.com/Eclipse project settings), which took me doing twice before I wanted to punch something. I had to stop doing actual work and figure out how to resolve this nightmare.
After doing a bit of research and poking around, I finally came across someone else who experienced the same problem in the post Problems in SVN in Eclipse on Mac OS X Mountain Lion (10.8). In a nutshell, it appears that after I first upgraded SQLite to work with the newer version of SVN, the location that SVN was expecting to find the SQLite library did not exist. What I needed to do was the last two steps of the linked post, which was to locate any references to this particular file, and then create a symbolic link from an actual library to the expected location.