On Jun 4, 2007, at 14:04, Rich Shepard wrote:
> 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
> 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
> 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
> creating a new project in the repository with the current versions
> of the
> files, what can I do?
Show us the exact commands you enter and the exact results you
receive; it's hard to speculate what's going on otherwise.
One possible reason changes you make to a file aren't seen by
Subversion and not transmitted to the repository is if whatever tool
you use to edit the file does not bump the file's modification date.
If this is the case, instruct the tool you use to edit the files not
to fudge the modification date like that. If you can't, then remember
to "touch" the file before trying to commit.
Telling Subversion to add a file that's already added shouldn't cause
anything to blow up; it should just print a message that the file is
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jun 4 22:28:12 2007