You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by jonatan <jo...@wineasy.se> on 2002/12/28 12:25:26 UTC
Issues from a new user
I recently installed Subversion to handle all PHP code on a web server.
I have a few questions/issues from the perspective of a newbie to
Subversion and SCM software in general.
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?
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?
3) I get intermittent crashes from the BDB when running "svn export".
It has happened about three times, and I'm only at revision 11.
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
/home/arksvn/db:
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).
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)".
Thanks for all the work. Subversion will be (is) great!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by Branko Čibej <br...@xbc.nu>.
jonatan wrote:
> I recently installed Subversion to handle all PHP code on a web
> server. I have a few questions/issues from the perspective of a newbie
> to Subversion and SCM software in general.
>
> 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?
Yes, you're missing something. :-)
You can /never/ delete history. Your file b is still there, it's just
not visible in the HEAD revision. To paraphrase your question:
$ svn add a b
$ svn commit
This creates your revision 1, with files a and b.
$ svn rm b
$ svn commit
You're now at revision 2; that revision doesn't contain b any more.
However, b still exists in revision 1. You can get it back by updating
to revision 1 again:
$ svn up -r 1
If course, that won't bring back b in HEAD. But you can also resurrect a
delted file:
$ svn cp -r1 <repos-url>/b b
$ svn commit
This will copy b as it existed in revision 1 to your working copy, and
commit it, creating revision 3.
> 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?
That would require distributed repositories; you'd need a local
repository copy that could somehow be synchronized with the master after
several commits. Subversion doesn't support that (yet). and won't 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 11.
>
> 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
> /home/arksvn/db:
> 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 shouldn't happen through normal use. Can you reproduce this
consistently? If yes, can you tell us exactly how?
> 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)".
You can't, really. All you know is that your binaries weren't built from
a release tarball, but from a working copy. There's no guarantee in
general that all the files in the working copy were at the same version.
Only the person who built the binaries can be sure.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
jonatan <jo...@wineasy.se> writes:
> I see. Good to know the file can be reinstated. The reason I assumed
> it was lost forever was that "svn cat -r1 b" and svn log b" return
> error messages. Is that intended? I was expecting "svn cat -r1 b" to
> return revision 1 of b, and "svn log b" to return all log messages
> associated with b.
>
> svn cat -r1 b
> subversion/clients/cmdline/cat-cmd.c:69: (apr_err=150004)
> svn: Entry has no url
> svn: 'b' has no URL
This ought to work, imho, but it's a strange case. A `b' once existed
in this directory, but no longer does. If you did
$ svn cat -r1 http://url.to.repository/blah/blah/b
that would definitely work.
Still, folks: wouldn't it be nice if we computed the url and tried it?
(Sigh, so many, many edge cases.)
> svn log b
> subversion/libsvn_ra_dav/util.c:358: (apr_err=160013)
> svn: Filesystem has no item
> svn: REPORT request failed on /path/to/repos
> subversion/libsvn_ra_dav/util.c:152: (apr_err=160013)
> svn:
> file not found: revision `18', path `b'
Similar situation to above, but even more edgy, yeah.
> I've skimmed through the book, enough to get by with using it. I
> started off with your CVS book, but realized that Subversion was the
> way to go :-)
Good :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by Nick Glencross <ni...@glencros.demon.co.uk>.
I'm a newbie too, but this looks like a backtrace that I saw the other
night when I was running cvs2svn.py to import my depot, and ran out of
disk in a partition (I didn't realise that I'd get hundreds of megs of
database log files!) It was certainly in the cleanup handlers like this
that I saw the problem.
Cheers,
Nick
jonatan wrote:
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 1024 (runnable)]
> 0x2ad010e1 in __kill () at __kill:-1
> -1 __kill: No such file or directory.
> in __kill
> (gdb) bt
> #0 0x2ad010e1 in __kill () at __kill:-1
> #1 0x2acd651a in raise (sig=6) at signals.c:65
> #2 0x2ad02570 in abort () at ../sysdeps/generic/abort.c:88
> #3 0x2ab9ccb8 in default_warning_func (pool=0x8099a20, baton=0x0,
> fmt=0x2aba9047 "%s") at subversion/libsvn_fs/fs.c:107
> #4 0x2ab9cf2e in cleanup_fs_apr (data=0x8099a58)
> at subversion/libsvn_fs/fs.c:237
> #5 0x2ac2a623 in run_cleanups (c=0x8099b88) at apr_pools.c:1961
> ...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by jonatan <jo...@wineasy.se>.
>> I just ran "svn co file:///path/to/repos" and got:
>>
>> A repos/trunk
>> ...
>> Checked out revision 18.
>> Abort
>>
>> The "Abort" seems to mean that the client crashed, right? After this
>> I get the same error message as before when trying to access the
>> repos.
>
> yeah, that shouldn't be happening... any chance you can run that
> command inside gdb and get us a backtrace?
/usr/local/gdb-5.3/bin/gdb
GNU gdb 5.3
...
This GDB was configured as "i686-pc-linux-gnu".
(gdb) file svn
Reading symbols from svn...done.
(gdb) run co file:///home/arksvn
Starting program: /usr/local/subversion-r3987/bin/svn co
file:///home/arksvn
[New Thread 1024 (runnable)]
A arksvn/trunk
...
A arksvn/trunk/map/index.php
Checked out revision 19.
Program received signal SIGABRT, Aborted.
[Switching to Thread 1024 (runnable)]
0x2ad010e1 in __kill () at __kill:-1
-1 __kill: No such file or directory.
in __kill
(gdb) bt
#0 0x2ad010e1 in __kill () at __kill:-1
#1 0x2acd651a in raise (sig=6) at signals.c:65
#2 0x2ad02570 in abort () at ../sysdeps/generic/abort.c:88
#3 0x2ab9ccb8 in default_warning_func (pool=0x8099a20, baton=0x0,
fmt=0x2aba9047 "%s") at subversion/libsvn_fs/fs.c:107
#4 0x2ab9cf2e in cleanup_fs_apr (data=0x8099a58)
at subversion/libsvn_fs/fs.c:237
#5 0x2ac2a623 in run_cleanups (c=0x8099b88) at apr_pools.c:1961
#6 0x2ac299bc in apr_pool_destroy (pool=0x8099a20) at apr_pools.c:746
#7 0x2ac2982c in apr_pool_clear (pool=0x80838a0) at apr_pools.c:706
#8 0x2abd31ad in svn_pool_clear (pool=0x80838a0)
at subversion/libsvn_subr/pool.c:143
#9 0x0804af14 in svn_cl__checkout (os=0x805e258, baton=0x7ffffba4,
pool=0x805e138) at subversion/clients/cmdline/checkout-cmd.c:140
#10 0x0804d666 in main (argc=3, argv=0x7ffffc84)
at subversion/clients/cmdline/main.c:856
#11 0x2acfacae in __libc_start_main (main=0x804cf00 <main>, argc=3,
argv=0x7ffffc84, init=0x804a100 <_init>, fini=0x8050680 <_fini>,
rtld_fini=0x2aab56d0 <_dl_fini>, stack_end=0x7ffffc7c)
at ../sysdeps/generic/libc-start.c:92
(gdb)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
> I just ran "svn co file:///path/to/repos" and got:
>
> A repos/trunk
> ...
> Checked out revision 18.
> Abort
>
> The "Abort" seems to mean that the client crashed, right? After this I
> get the same error message as before when trying to access the repos.
yeah, that shouldn't be happening... any chance you can run that
command inside gdb and get us a backtrace?
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by jonatan <jo...@wineasy.se>.
> On Saturday, December 28, 2002, at 04:49 PM, jonatan wrote:
>
>> Thanks for all of the responses. I will respond to just one to spare
>> some bandwidth.
>>
>>>> 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.
>>
>> I see. Good to know the file can be reinstated. The reason I assumed
>> it was lost forever was that "svn cat -r1 b" and svn log b" return
>> error messages. Is that intended? I was expecting "svn cat -r1 b" to
>> return revision 1 of b, and "svn log b" to return all log messages
>> associated with b.
>>
>> svn cat -r1 b
>> subversion/clients/cmdline/cat-cmd.c:69: (apr_err=150004)
>> svn: Entry has no url
>> svn: 'b' has no URL
>>
>> svn log b
>> subversion/libsvn_ra_dav/util.c:358: (apr_err=160013)
>> svn: Filesystem has no item
>> svn: REPORT request failed on /path/to/repos
>> subversion/libsvn_ra_dav/util.c:152: (apr_err=160013)
>> svn:
>> file not found: revision `18', path `b'
>
> for both of these, the problem (i think) is that svn is trying to look
> in your working copy for the file, and it's been deleted, so it can't
> find it. if you give a url as the target instead of a path, it should
> work. (i.e. svn log -r 1 file:///path/to/repos/b). the log command
> really should be easier to use with deleted files, since you basically
> have to know the reivsions it existed in to get any useful log info
> about it. this is annoying when you're trying to figure out when
> something was deleted for example...
>
>> svn: Berkeley DB error
>> svn: Berkeley DB error while checkpointing after Berkeley DB
>> transaction for filesystem /home/arksvn/db:
>> DB_RUNRECOVERY: Fatal error, run database recovery
>
> out of curiosity, what file system are you running this on? we've had
> weird berkeley db errors in the past that turned out to be file system
> bugs.
Ext2 on a SCSI. Trustix 1.5 Linux 2.2.20 on a i686.
>> From Garrett Rooney:
>>> well, your repository is getting screwed up somehow. are you
>>> accessing it via ra_local (file:// url's) and hitting control-c to
>>> kill the process or something? or did svn crash for some reason?
>>> if svn exits unexpectedly while talking directly to the repository
>>> it can leave the berkeley db database in an inconsistent state.
>>
>> I do access the repos with ra_local, but am not killing the process
>> (that I know of). How do I see if svn crashes?
>
> well, either your apache logs would have something about a crash, or
> you'd see your client crash (if you were accessing it via ra_local).
I just ran "svn co file:///path/to/repos" and got:
A repos/trunk
...
Checked out revision 18.
Abort
The "Abort" seems to mean that the client crashed, right? After this I
get the same error message as before when trying to access the repos.
>> I should mention that I'm modifying the group owner and privileges of
>> the files in the db/ subdirectory of the repository to get them
>> readable and writable by a group called "svn". Perhaps this is
>> causing problems.
>
> that shouldn't cause that kind of problem (as far as i know).
>
> -garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Saturday, December 28, 2002, at 04:49 PM, jonatan wrote:
> Thanks for all of the responses. I will respond to just one to spare
> some bandwidth.
>
>>> 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.
>
> I see. Good to know the file can be reinstated. The reason I assumed
> it was lost forever was that "svn cat -r1 b" and svn log b" return
> error messages. Is that intended? I was expecting "svn cat -r1 b" to
> return revision 1 of b, and "svn log b" to return all log messages
> associated with b.
>
> svn cat -r1 b
> subversion/clients/cmdline/cat-cmd.c:69: (apr_err=150004)
> svn: Entry has no url
> svn: 'b' has no URL
>
> svn log b
> subversion/libsvn_ra_dav/util.c:358: (apr_err=160013)
> svn: Filesystem has no item
> svn: REPORT request failed on /path/to/repos
> subversion/libsvn_ra_dav/util.c:152: (apr_err=160013)
> svn:
> file not found: revision `18', path `b'
for both of these, the problem (i think) is that svn is trying to look
in your working copy for the file, and it's been deleted, so it can't
find it. if you give a url as the target instead of a path, it should
work. (i.e. svn log -r 1 file:///path/to/repos/b). the log command
really should be easier to use with deleted files, since you basically
have to know the reivsions it existed in to get any useful log info
about it. this is annoying when you're trying to figure out when
something was deleted for example...
> svn: Berkeley DB error
> svn: Berkeley DB error while checkpointing after Berkeley DB
> transaction for filesystem /home/arksvn/db:
> DB_RUNRECOVERY: Fatal error, run database recovery
out of curiosity, what file system are you running this on? we've had
weird berkeley db errors in the past that turned out to be file system
bugs.
> From Garrett Rooney:
>> well, your repository is getting screwed up somehow. are you
>> accessing it via ra_local (file:// url's) and hitting control-c to
>> kill the process or something? or did svn crash for some reason? if
>> svn exits unexpectedly while talking directly to the repository it
>> can leave the berkeley db database in an inconsistent state.
>
> I do access the repos with ra_local, but am not killing the process
> (that I know of). How do I see if svn crashes?
well, either your apache logs would have something about a crash, or
you'd see your client crash (if you were accessing it via ra_local).
> I should mention that I'm modifying the group owner and privileges of
> the files in the db/ subdirectory of the repository to get them
> readable and writable by a group called "svn". Perhaps this is causing
> problems.
that shouldn't cause that kind of problem (as far as i know).
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by jonatan <jo...@wineasy.se>.
Thanks for all of the responses. I will respond to just one to spare
some bandwidth.
>> 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.
I see. Good to know the file can be reinstated. The reason I assumed it
was lost forever was that "svn cat -r1 b" and svn log b" return error
messages. Is that intended? I was expecting "svn cat -r1 b" to return
revision 1 of b, and "svn log b" to return all log messages associated
with b.
svn cat -r1 b
subversion/clients/cmdline/cat-cmd.c:69: (apr_err=150004)
svn: Entry has no url
svn: 'b' has no URL
svn log b
subversion/libsvn_ra_dav/util.c:358: (apr_err=160013)
svn: Filesystem has no item
svn: REPORT request failed on /path/to/repos
subversion/libsvn_ra_dav/util.c:152: (apr_err=160013)
svn:
file not found: revision `18', path `b'
> (Have you read the online Subversion book or other documentation yet?)
I've skimmed through the book, enough to get by with using it. I
started off with your CVS book, but realized that Subversion was the
way to go :-)
>> 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).
I see. Good to know that it is planned.
>> 3) I get intermittent crashes from the BDB when running "svn
>> export". It has happened about three times, and I'm only at revision
>> 11.
>>
>> 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
>> /home/arksvn/db:
>> 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).
For the record, I'm getting this on a i686 running Linux.
> Does it still happen if you upgrade your server?
I will try. (I've been putting it off since initial installation was
pretty hairy...)
> Soon Subversion will use BDB 4.1.24, and then we'll see if this
> problem persists. Sorry for the inconvenience.
No problem. I don't expect it to be perfect, yet.
From Branko Čibej:
> This shouldn't happen through normal use. Can you reproduce this
> consistently? If yes, can you tell us exactly how?
No, but it's not consistently reproducible, but it happens "often".
I've had it happen five times so far, out of perhaps 30-40 tries. It
just happened again, this time with a slightly different message:
svn: Berkeley DB error
svn: Berkeley DB error while checkpointing after Berkeley DB
transaction for filesystem /home/arksvn/db:
DB_RUNRECOVERY: Fatal error, run database recovery
From Garrett Rooney:
> well, your repository is getting screwed up somehow. are you
> accessing it via ra_local (file:// url's) and hitting control-c to
> kill the process or something? or did svn crash for some reason? if
> svn exits unexpectedly while talking directly to the repository it can
> leave the berkeley db database in an inconsistent state.
I do access the repos with ra_local, but am not killing the process
(that I know of). How do I see if svn crashes?
I should mention that I'm modifying the group owner and privileges of
the files in the db/ subdirectory of the repository to get them
readable and writable by a group called "svn". Perhaps this is causing
problems.
>> 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.
I did (issue number 1053) but for some reason it wasn't possible to set
the milestone.
>> Thanks for all the work. Subversion will be (is) great!
>
> Hope so! :-)
>
> -Karl
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
jonatan <jo...@wineasy.se> 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
> 11.
>
> 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
> /home/arksvn/db:
> 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! :-)
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Issues from a new user
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Saturday, December 28, 2002, at 07:25 AM, jonatan wrote:
> I recently installed Subversion to handle all PHP code on a web
> server. I have a few questions/issues from the perspective of a newbie
> to Subversion and SCM software in general.
>
> 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?
svn delete already does exactly what you want. to get back to the
previous version, you can either 'svn up -r
version_before_i_deleted_it' or you can (assuming you deleted it in
revision 5) do a 'svn merge -r 4:5 .' and the file will be back in your
working copy. then you can commit to have it back in the repository.
> 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?
you want distributed repositories, where you've got your own little
repos on your machine, and you merge changes to and from it into your
main repository. lots of other people want this too, but it's a lot of
work.
> 3) I get intermittent crashes from the BDB when running "svn export".
> It has happened about three times, and I'm only at revision 11.
>
> 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
> /home/arksvn/db:
> 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).
well, your repository is getting screwed up somehow. are you accessing
it via ra_local (file:// url's) and hitting control-c to kill the
process or something? or did svn crash for some reason? if svn exits
unexpectedly while talking directly to the repository it can leave the
berkeley db database in an inconsistent state.
> 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)".
at the moment, you remember what revision you built it from ;-)
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org