From comand at blastwave.org  Thu Jun  2 03:22:23 2005
From: comand at blastwave.org (Cory Omand)
Date: Wed, 01 Jun 2005 18:22:23 -0700
Subject: [csw-announce] Subversion 1.2.0 Packages Available
Message-ID: <1117675343.6222.24.camel@haywire>

New packages for subversion 1.2.0 (including pm_subversion, pysvn,
javasvn, and ap2_subversion) are now available.

Please note that the ap2_subversion package now has an explicit
dependency on the Apache 2.0 prefork MPM (ap2_prefork).  The
prefork MPM is currently the default for the apache2 distribution.
Due to issues with locale character set detection, mod_dav_svn is
unable to access repositories when the worker MPM is loaded.

This upgrade requires no further action if deployed for client use
only.  For server use, any repositories created with subversion
linked against Berkeley DB 4.0.x (bdb4) will require a dump/load,
as outlined in the following procedure.  If you are unsure which
version of BDB was used to create your repository, see [3] below
for details.

$ mv /path/to/repo /path/to/repo.bak
$ su - <svn user>
$ svnadmin dump /path/to/repo.bak > /tmp/svn.dump

# Upgrade subversion

$ su - <svn user>
$ svnadmin create /path/to/repo
$ svnadmin load /path/to/repo < /tmp/svn.dump
$ svnadmin verify /path/to/repo
# ... verify that you are able to access the new repo
$ rm -r /path/to/repo.bak

This will re-create your subversion repository.  Note that the
create/dump/load must be done as the user which manages the
repository, or permission issues may prevent access to the rebuilt
repository.  For additional information, please see:

[1]
http://svnbook.red-bean.com/en/1.1/ch05s03.html#svn-ch-5-sect-3.5

[2]
http://subversion.tigris.org/faq.html#bdb43-upgrade

[3]
http://subversion.tigris.org/faq.html#divining-bdb-version


-- 
Cory Omand <comand at blastwave.org>
Blastwave


From comand at blastwave.org  Thu Jun  2 03:22:23 2005
From: comand at blastwave.org (Cory Omand)
Date: Wed, 01 Jun 2005 18:22:23 -0700
Subject: [csw-announce] Subversion 1.2.0 Packages Available
Message-ID: <1117675343.6222.24.camel@haywire>

New packages for subversion 1.2.0 (including pm_subversion, pysvn,
javasvn, and ap2_subversion) are now available.

Please note that the ap2_subversion package now has an explicit
dependency on the Apache 2.0 prefork MPM (ap2_prefork).  The
prefork MPM is currently the default for the apache2 distribution.
Due to issues with locale character set detection, mod_dav_svn is
unable to access repositories when the worker MPM is loaded.

This upgrade requires no further action if deployed for client use
only.  For server use, any repositories created with subversion
linked against Berkeley DB 4.0.x (bdb4) will require a dump/load,
as outlined in the following procedure.  If you are unsure which
version of BDB was used to create your repository, see [3] below
for details.

$ mv /path/to/repo /path/to/repo.bak
$ su - <svn user>
$ svnadmin dump /path/to/repo.bak > /tmp/svn.dump

# Upgrade subversion

$ su - <svn user>
$ svnadmin create /path/to/repo
$ svnadmin load /path/to/repo < /tmp/svn.dump
$ svnadmin verify /path/to/repo
# ... verify that you are able to access the new repo
$ rm -r /path/to/repo.bak

This will re-create your subversion repository.  Note that the
create/dump/load must be done as the user which manages the
repository, or permission issues may prevent access to the rebuilt
repository.  For additional information, please see:

[1]
http://svnbook.red-bean.com/en/1.1/ch05s03.html#svn-ch-5-sect-3.5

[2]
http://subversion.tigris.org/faq.html#bdb43-upgrade

[3]
http://subversion.tigris.org/faq.html#divining-bdb-version


-- 
Cory Omand <comand at blastwave.org>
Blastwave