From: James G. S. (jim) <jg...@sa...> - 2007-11-07 21:15:35
|
Benny Malengier wrote: > As this becomes a bug/devel issue, let's move this to gramps-devel. > > Tony, please subscribe to gramps-devel (temporarely), or check on > nabble.comhow this evolves. I'll try to add your name in the to field > so you get it > even if not subscribed. You can run the devel version that is improved > 2.2.9by getting branch22 from our svn, see the wiki (search on > subversion for > relevant pages). > > Jim, I do suppose the crash is related to what Tony asked? ;-) If by "the crash", you mean the symptom I mentioned in in bug 1353, then that symptom was in the command line interface. In the gui, creating a new db and importing the sample code proceeds without any apparent error. Attempting to export to gedcom pops up a dialog: """ Error detected in database GRAMPS has detected an error in the database. This can usually be resolved by running the "Check and Repair Database" tool. If this problem continues to exist after running this tool, please file a bug report at http://bugs.gramps-project.org 'NoneType' object has no attribute 'private' """ Running Check and repair produces the output I posted in a previous message, epeated here: """ 1 broken child/family link was fixed Wilson, Mary Ann was removed from the family of Unknown 1 broken spouse/family link was fixed Wilson, Mary Ann was restored to the family of Williams, Robert Eugene and Wilson, Mary Ann """ I haven't analyzed the export error or the repair operation. Export to gedcom works after the repair, but I haven't compared the imported sample to the exported gedcom yet. ==> If there is another "crash" under discussion, I must have missed it. Now I was reading Tony's earlier post as saying he wanted to run some sample data before committing his real genealogy data to Gramps, which is quite understandable. The sample data had one lettercase error and one structural level-error, but after fixing that, the import proceeded without any complaint from Gramps. I'd be willing to spend some more time understanding - the error detected while attempting an export, and - the details of the repair in check and repair, and finally - on the comparison of gedcom input to gedcom output but it might be another day or two until I get to it. Regards, ..jim |