Cleaning Up A Mess

   I've been running svn-1.4.0 and upgraded today to -1.4.3 to gain access to
the new svnadmin commands.

   For a number of months I've had one project in the repository, and decided
to add a new project about a month ago. I followed the instructions in Mike
Mason's book, "Pragmatic Version Control Using Subversion," and it seemed to
go well. Except that committed versions continued the numbering of the
original project rather than starting at build 1 for the new project.

   However, one file (schema.sql) is not transmitted to the repository when I
make changes to it. Thinking the file was not added, I tried adding it. Bad
move; it was already there. When I tried deleting the copy, only the working
copy in the local directory was wiped out (but I was able to re-save it from
the open emacs buffer.)

   While I understand the value of having a permanent repository for files
and their deltas, this entire project's repository is FUBAR. I can use 'svn
ls' and see all the files, but I cannot delete unnecessary ones (as I
could/can with the original project in the repository), and when I commit
changes, this one file is just not updated.

   I've read the 1.4 version of the book, looked at the 'svnadmin help dump'
page, and tried to figure out how to fix this mess on my own. Other than
creating a new project in the repository with the current versions of the
files, what can I do?

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |    The Environmental Permitting
Applied Ecosystem Services, Inc.        |          Accelerator(TM)
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org