Bug 136755 - selecting subversion should issue a warning regarding bdb based repositories.
Summary: selecting subversion should issue a warning regarding bdb based repositories.
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Olaf Hering
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-02 19:39 UTC by Marcus Rückert
Modified: 2005-12-06 12:50 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Rückert 2005-12-02 19:39:46 UTC 
in general it is possible to in place migrate a bdb based repository. but it doesnt have to work. it would be cool if we could issue a warning during installation about it. i saw people of other distros shooting their feets that way.
Comment 1 Olaf Hering 2005-12-05 10:44:21 UTC 
what exactly should happen, and where?
Comment 2 Marcus Rückert 2005-12-05 11:39:02 UTC 
what: "you had subversion installed on your old installation. if you had repositories locally which used bdb please dump them with "svnadmin dump" before proceeding with the installation"

when: during upgrade. when yast evaluates the old package selection.
Comment 3 Olaf Hering 2005-12-05 14:10:23 UTC 
I dont think yast can do that. And its already mentioned in some readme.
Comment 4 Olaf Hering 2005-12-06 12:50:55 UTC 
1. backup and restore your repository data

subversion repositories use either the Berkeley Database system libraries,
or the FSFS database format which comes with the subversion package.
Since the BDB system libraries often introduce a new incompatible format during
version upgrade, a backup/restore of all the subversion repositories must be
performed _BEFORE_ doing such a system upgrade.
'svnadmin dump' will write the repository to stdout in a 'dumpfile' format.
This dumpfile can be loader later with 'svnadmin load'.


This is mentioned in the readme.
And the repo is not lost, or corrupted after the upgrade.