Re: [Gramps-users] upgrade problems 2.2.10 -> 3.1.1

[<kda...@tx...>]

I thought I had to go thru xml on upgrade :(.
When I try to import the grdb from 2.2.10 I get a pop up error "/tmp/tmp3Y68q- could not be opened" and a console error of 
Traceback (most recent call last):
  File "/usr/share/gramps/plugins/import/ImportGrdb.py", line 2446, in importData
    other_database.load(new_filename, callback)
  File "/usr/share/gramps/plugins/import/ImportGrdb.py", line 427, in load
    self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1)  # clean up unused logs
AttributeError: 'module' object has no attribute 'DB_LOG_AUTOREMOVE'
None

The /tmp file is there and non-zero.

I had 2 bookmarks in xml for persons which are existing.

Kyle

---- Benny Malengier <ben...@gm...> wrote: 
> 2009/3/31 <kda...@tx...>
> 
> > OK, I edited the xml and imported into another blank tree.  Bizarrely, 7
> > families still come up with the merge error.  Looking at these families,
> > only 1 had any duplicates, and that was an event id which I could fix. The
> > other families look ok.   I _still_ have 50 families with ID=None and seem
> > to be completely blank when I looked at them.  There are no such id's in the
> > imported xml file, of course.  It occurred to me I could have missing
> > families now, so I grep'd every hlink for a corresponding family and found
> > 15 missing families.  In gramps when I try to look at relationships for
> > these individuals it pops up an error message about a corrupted database.
> >
> > bummer.
> 
> 
> Don't forget to check your bookmarks at the bottom of the xml file. The
> bookmarks might refer to not existing families?
> Normally that is handled in the code, but there could be a bug there.
> 
> 
> > the individuals I checked seem to be most recently added ones (in 2.2.10).
> >
> > After removing all the "None" families, I can add a new family now, and it
> > successfully generates a family id, but no joy if I've lost 15 families...
> >
> > I will go back into 2.2.10 and do a check database and re-export, but IIRC
> > those have been successful and found no problems recently.
> >
> 
> If after that the problem is still there, send me the xml file privately,
> and I can check what is going wrong in the import.
> Does import of the grdb file also causes this issue? (keep backup of .gramps
> dir, and of your xml and grdb files before messing with versions of GRAMPS
> !)
> 
> Benny
> 
> 
> >
> > Kyle
> >
> >
> >
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > Gramps-users mailing list
> > Gra...@li...
> > https://lists.sourceforge.net/lists/listinfo/gramps-users
> >