Update from 10 year old gramps files

Currently, gramps 5.2.2, Linux, Fedora 40.
I created a small tree some 8-10 years ago. What is the best way to import that into 5.2.2 please?

How can I tell from the files what the older files version of gramps is?

A quick guess is that you were using 3.4.x at that time, which can probably be converted by 5.2.2.

What do these files look like?

x.gramps (dated 2007 - 2014)

One (html file) shows

GRAMPS, 2.2.8-0.SVN created 2007-12-21

ps: I also have a file I marked (xmlsave.2015) which is xml format (no metadata though unless

Indicates a version 1.6?

regards

You can try follow this steps…

upgrade fron an old gramps database

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 your operating system does not support Gramps-2 any more as some dependencies has been removed since Gramps-2 (GCONF, gnome-doc-utils, yelp, python-reportlab, libglade, etc...) or updated like python libs and related, then you could have a look at Linux Genealogy Live CD archives.

    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.

    related to bug 6129 : I downloaded the gramps 2.2.10 on my ubuntu 11.10 and did the following :

Thanks Avma.
I did wonder about a virtual machine to do this?
I’ve seen ‘incompatible’ packages previously.
Is it reasonable to install an ‘older’ linux for this purpose, working in a virtual environment?

Well if you get lucky and your machine takes Gramps 2.x then it is quite straightforward; import your file, export to xml (and gedcom) install gramps 3.x import and so on.
I wouldn’t go and install an old Linux just for that, but if you read on on that link, you could try and submit your file in as describe there, hopefully they might kept an older running versions of Gramps to help you out.

1 Like

If you found that 1.6 in the XML, you can import that right away, and for the other .gramps file, you can also just give it a try. A .gramps file is normally compressed XML, and if it is, you can rename it to .gz, and then extract its contents with gunzip.

If it’s too old, you may need to run an old Linux in a VM, because current Linuxes often don’t have the packages that older .deb or .rpm files depend on. There are other threads here on that subject, and it can be quite difficult to find an old live CD that can be run in VirtualBox, and access a shared folder. And that’s why I suggest those old threads, where I wrote about my own tests with those.

1 Like

Addendum: The last time I tried working with live CDs is reflected in this thread:

1 Like

Coincidentally, the naming is reminiscent of the RCS Archiving currently being discussed in another thread.

Thanks. I’ll chase the link, though the XML import sounds hopeful

2 Likes

Please let us know how things go.

2 Likes

@ennoborg - yes, X.gramps, imports (minor msg about media path)…

Is there an ‘export to latest version / standard’ command please? o/p format Grams xml package?

regards

The easiest export is a backup. without media. It does the same as an export without filters in compressed Gramps XML, but the latter would create an anonymous file named data.gramps, and you probably don’t want that.

Backups are always named after your tree, and also include the date in the file name. Automated backups even add a time stamp to that name.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.