Thank you for your help. My husband and I have looked at all of these
options in the documentation but were unsure whether any of these methods
would be successful. It is reassuring to learn this from someone who knows.
I had not thought to bring up our backup files, though. Thanks for the
I look forward to the new release. I was concerned that my .gramps files
could not be saved. What a relief! Again, thanks for you kind offer to help.
I may contact you if we have trouble.
On Mon, Nov 30, 2009 at 2:50 AM, Benny Malengier
> 2009/11/29 . . <lrlaskey@...>:
> > Duncan,
> > I appreciate your help with this matter and will be as specific and
> > with my terms as possible. I have many older files saved as .gramps and
> > .grdb that are both surname databases and backup ,.bak, copies, too.
> > I'll start with those files that I cannot import first. This is the error
> > message I get when I attempt to import a .grdb database into a new empty
> > family tree. This is probably of of those databases that I moved from
> > original directory.
> > /tmp/tmpni6tlW could not be opened
> First, version 3.1.3 will be released 6 december. It reintroduces
> support for XML import of old GRAMPS versions, which due to lack of
> testing, did not work anymore in earlier versions.
> So keep your .gramps files around, and when 3.1.3 arrives, try again
> with that, all .gramps files created with version 1.0.0 or later
> should be supported I believe.
> Second, the error you now give, is due to import of a grdb file of
> which the database logs cannot be recovered. This is explained in
> So, the only way to recover from this is:
> Or: obtain a backup of your old .gramps directory, and move the files
> in the .gramps/grampsdb directory to their original position
> (carefull, don't remove the data of your already created family trees
> which is also in .gramps/grampsdb). Once this is done, you should be
> able to import the grdb files.
> Or: use the xml files to import your data. You can use GEDCOM, but
> GEDCOM does _not_ store all data you can save in Gramps, so do it for
> one Gedcom file first, and see if the loss is acceptable to you before
> continuing with Gedcom import. Xml import is safe, but you need to
> wait for version 3.1.3. to be available for your system if 3.1.2 has
> problems with the old xml.
> Or: use the database dump and load tool to create a new grdb file that
> can be opened without the log files being present in
> ./gramps/grampsdb. This is explained in
> It really is not difficult to do that, I did it for several people who
> did not succeed to do this, all without problems. So if you fail at
> home to do it, mail it to me, or to one of the other core developers,
> and they will convert to xml for you.
> PS: your email name is set to .., I find that a bit annoying in my
> list of mails, would you mind assigning a real name in your mail
> client? It is now: . . <lrlaskey@...>. If everybody starts to
> use that technique, it would become really, really annoying.
> > On Sun, Nov 29, 2009 at 5:27 AM, Duncan Lithgow <
> > wrote:
> >> 2009/11/29 . . <lrlaskey@...>:
> >> > Surname files are my name for GRAMPS ".grdb" and ".gramps files.
> >> Okay, now I'm with you. I can understand that you call them 'files',
> >> they look like files. Actually they are databases, I think it's to
> >> avoid this technical confusion that they are now just called 'Family
> >> Trees' in Gramps.
> >> > I have many
> >> > of them because I have not been working on my genealogy for some time
> >> > and I
> >> > let several versions pass by without updating them.
> >> Do you mean that your genealogy is composed of different parts of the
> >> family stored in different 'Family Trees'? Or do you just mean that
> >> you have many old backup copies?
> >> > and GRAMPS cannot import them.
> >> Don't worry, you can import them, it's just a matter of how
> >> complicated it might get. As far as I know no-one has been forced to
> >> lose data because of a format change.
> >> > I was house cleaning. The consequences are that now I am getting error
> >> > messages when I try to open or import older files.
> >> I suggest you choose one example of your problem and ask for help with
> >> that. Then while we solve one problem you will probably see how to
> >> solve the others. The .gramps files you mentioned should import
> >> without any problem. Make sure you import into a new _empty_ family
> >> tree. The .grdb files are a bit trickier, but there are people on this
> >> list who are happy to help (I've never had to recover a .grdb file
> >> myself). Also you mentioned merging, for that I suggest you wait for a
> >> later release of Gramps. There are no tools to help manage merging
> >> databases - but the devs are working on fixing that.
> >> > Is there a way to create gedcoms from the command line without opening
> >> > GRAMPS? A gedcom could be opened in the new format.
> >> I recommend you don't do that. Gramps can't promise that GEDCOM files
> >> will have all the information inside that the original .gramps files
> >> had.
> >> > I have learned a hard lesson. Whenever a program upgrades, save files
> >> > the
> >> > new format. I should have done that several versions ago.
> >> And this problem is in no way unique to Gramps - but at least the
> >> gramps devs have made sure there is always a way to recover your data.
> >> Regards, Duncan
> >> PS. Ask a very specific question and you'll get more useful, and
> >> shorter, answers :-)
> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> > trial. Simplify your report design, integration and deployment - and
> > on
> > what you do best, core application coding. Discover what's new with
> > Crystal Reports now. http://p.sf.net/sfu/bobj-july
> > _______________________________________________
> > Gramps-users mailing list
> > Gramps-users@...
> > https://lists.sourceforge.net/lists/listinfo/gramps-users