Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What is this “dump/load cycle” people sometimes talk about when upgrading a Subversion server?

0
10 Posted

What is this “dump/load cycle” people sometimes talk about when upgrading a Subversion server?

0

Subversion’s repository database schema changes occasionally during development. We try to keep such changes to a minimum, but Subversion is pre-1.0 software, and we want to ship 1.0 with the best schema we can. If a schema change happens between Subversion releases X and Y, then repository administrators upgrading to Y must do the following: • Shut down svnserve, Apache, and anything else that might be accessing the repository. • svnadmin dump /path/to/repository > dumpfile.txt , using version X of svnadmin. • mv /path/to/repository /path/to/saved-old-repository • Now upgrade to Subversion Y (i.e., build and install Y, replacing X). • svnadmin create /path/to/repository, using version Y of svnadmin. • svnadmin load /path/to/repository <> , again using version Y of svnadmin. • Copy over hook scripts, etc, from the old repository to the new one. • Restart svnserve, Apache, etc. See http://svnbook.red-bean.com/html-chunk/ch05s03.html#svn-ch-5-sect-3.4 for more details on dumping and load

0

Subversion’s repository database schema has changed occasionally during development. Old repositories, created with a pre-1.0 development version of Subversion, may require the following operation when upgrading. If a schema change happens between Subversion releases X and Y, then repository administrators upgrading to Y must do the following: • Shut down svnserve, Apache, and anything else that might be accessing the repository. • svnadmin dump /path/to/repository > dumpfile.txt , using version X of svnadmin. • mv /path/to/repository /path/to/saved-old-repository • Now upgrade to Subversion Y (i.e., build and install Y, replacing X). • svnadmin create /path/to/repository, using version Y of svnadmin. • svnadmin load /path/to/repository < dumpfile.txt , again using version Y of svnadmin. • Copy over hook scripts, etc, from the old repository to the new one. • Restart svnserve, Apache, etc. See this section of the Subversion book for more details on dumping and loading. Note: Most upgra

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123