jonatan <email@example.com> writes:
> 1) "svn delete". This seems to delete the file permanently. Suppose I
> have files a and b in revision 1, but in revision 2 I do away with
> file b. Since the file is deleted permanently, there is no way to
> revert to revision 1, since b is deleted. Am I missing something, or
> is there some other way of deleting a file from future revisions
> without deleting it from past revisions?
You're thinking of CVS. Subversion doesn't delete it in past
revisions, only in future ones. If you 'svn update -rOLDREV', the
file will reappear. If you 'svn checkout -rOLDREV URL', the checked
out tree will have b in it.
(Have you read the online Subversion book or other documentation yet?)
> 2) Stacked commits. I am sometimes offline for periods of time. It
> would be great if I could somehow stack up commits to be performed
> when I get online again. Otherwise I'll have to make one huge commit
> with all changes, which would make the changes less easily
> distinguishable. I realize there may be problems (conflicts) when
> multiple users are committing changes, but since I am the only user
> accessing the repository, I don't see why this wouldn't be
> possible. Any thoughts?
Subversion doesn't support this yet, and probably won't anytime soon
(at least not before 1.0).
> 3) I get intermittent crashes from the BDB when running "svn
> export". It has happened about three times, and I'm only at revision
> svn: Couldn't open a repository.
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository file:///home/arksvn/trunk
> svn: Berkeley DB error
> svn: Berkeley DB error while opening environment for filesystem
> DB_RUNRECOVERY: Fatal error, run database recovery
> Running "svnadmin recover" fixes it though. Is this normal? (My server
> is running SVN r3987 and BDB 4.0.14).
This isn't normal, although we've seen it on at least one other
machine (an old Sparc20 running Debian GNU/Linux).
Does it still happen if you upgrade your server?
Soon Subversion will use BDB 4.1.24, and then we'll see if this
problem persists. Sorry for the inconvenience.
> 4) How do I find out which revision of Subversion I'm running, when I
> am running a dev build? "svn --version" just shows "svn, version
> 0.16.0 (dev build)".
This is something we need to fix, it's been discussed quite a bit
here. Most Subversions are built from a single revision tree, so we
could put that revision number where "(dev build)" is, thus making
everyone's lives easier.
We don't seem to have an issue for it, though; possibly because we
(uh, I) got temporarily caught up in the complexities of how to handle
the edge case of a mixed-revision build.
Want to file an issue for this? Put it in milestone 'parallel' for
now, please, since it doesn't really block anything.
> Thanks for all the work. Subversion will be (is) great!
Hope so! :-)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Dec 28 19:29:09 2002