Difference between revisions of "Gramps Old database"
m (→Introduction) |
m (→Solutions) |
||
Line 8: | Line 8: | ||
==Solutions== | ==Solutions== | ||
− | * The safety way is to import it into [http://sourceforge.net/project/showfiles.php?group_id=25770&package_id=109309 Gramps-2] and to export this updated database. This will generate a new Gramps XML more compatible for an import into Gramps-3. | + | * The safety way is to import it into '''[http://sourceforge.net/project/showfiles.php?group_id=25770&package_id=109309 Gramps-2]''' and to export this updated database. This will generate a new Gramps XML more compatible for an import into '''Gramps-3'''. |
− | **If you operating system do not support Gramps-2 any more as some dependancies has been removed since Gramps-2 (GCONF, gnome-doc-utils, yelp, python-reportlab, etc...) or updated like python libs and related, then you could have a look at [[Linux_Genealogy_CD|Linux Genealogy Live CD]]. | + | **If you operating system do not support '''Gramps-2''' any more as some dependancies has been removed since '''Gramps-2''' (''GCONF, gnome-doc-utils, yelp, python-reportlab, etc...'') or updated like python libs and related, then you could have a look at [[Linux_Genealogy_CD|Linux Genealogy Live CD]]. |
− | * Also, you may [[Using_the_bug_tracker|submit your old database on bug-tracker]], mark this report as private (will be hidden for non-developers) and a developer will try to help you for updating your database. | + | * Also, you may [[Using_the_bug_tracker|submit your old database on bug-tracker]], mark this report as '''private''' (''will be hidden for non-developers'') and a developer will try to help you for updating your database. |
Revision as of 12:39, 18 May 2009
Introduction
If you have an old Gramps XML database generated 4 years ago, then you may have some difficulties to import them into last stable release (3.1.x). Gramps-1 did not store event as primary object and did not use bsddb references. There was some limitations (size, informations, encoding), new Gramps versions tried to fix them.
Solutions
- The safety way is to import it into Gramps-2 and to export this updated database. This will generate a new Gramps XML more compatible for an import into Gramps-3.
- If you operating system do not support Gramps-2 any more as some dependancies has been removed since Gramps-2 (GCONF, gnome-doc-utils, yelp, python-reportlab, etc...) or updated like python libs and related, then you could have a look at Linux Genealogy Live CD.
- Also, you may submit your old database on bug-tracker, mark this report as private (will be hidden for non-developers) and a developer will try to help you for updating your database.