Hi,
I'm wondering if any of these "Subversion
Inconveniences" has been addressed in 1.4.3 or will be
addressed 1.4.4. Particularly interested in
Repository Deadlocks.
Also, has anyone looked into using Postgres instead of
Berekely DB for a more reliable solution?
Best,
Ted
Interrupted checkouts.
If you interrupt a checkout in progress, you'll need
to toss the working copy and start over.
See Issue #730 for more details.
Charset conversion not yet supported on Win32
Charset encoding (i18n) conversion is not yet
supported on Win32, due to problems with our
portability libraries, apr and apr-util. There is no
issue associated with this, but it is being actively
worked on and should be fixed soon. Meanwhile, stick
with 7-bit ascii on Windows.
Charset conversion failure mode too extreme
If Subversion cannot convert log data to your local
charset encoding, it will (currently) just show
"[unconvertible data]" for the entire unconverted log
message. This is lossier than necessary. There are
even some revisions in the Subversion repository
itself that exhibit this behavior when the client
locale is ISO-8859-1 (Latin-1).
See Issue #807 for more details.
Repository deadlocks
If an svn client is directly accessing a repository
via a file:/// url and is interrupted, or crashes, (or
if httpd crashes), the repository is likely to be left
in a 'wedged' state. You'll need to run Berkeley DB's
'db_recover -ve -h repos/db' to unwedge the
repository. Make sure you shut down httpd before doing
this.
See Issue #739 for more details.
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 12 22:55:01 2002