From: Benny M. <ben...@gm...> - 2009-03-09 10:38:14
|
2009/3/9 Doug <dou...@on...> > Doug Blank wrote: >> >> >> Doug, >> >> What third-party plugins are you waiting for? Have you contacted the >> authors? If they are around, they are encouraged to add their wares to: >> >> <http://www.gramps-project.org/wiki/index.php?title=Plugins> >> > <snip> > At the time of my last post they were Descendant B report, Family Sheet, > Family Tree, Place Completion Tool and Records, but I now see them > gradually finding their way on to the 3.1 plugin list. Records is now part of GRAMPS, so don't wait for it ;-) Benny |
From: Doug <dou...@on...> - 2009-03-09 16:51:00
|
Benny Malengier wrote: > > > 2009/3/9 Doug <dou...@on... > <mailto:dou...@on...>> > > Doug Blank wrote: > > > Doug, > > What third-party plugins are you waiting for? Have you > contacted the authors? If they are around, they are encouraged > to add their wares to: > > <http://www.gramps-project.org/wiki/index.php?title=Plugins> > > <snip> > At the time of my last post they were Descendant B report, Family > Sheet, Family Tree, Â Place Completion Tool and Records, but I now > see them gradually finding their way on to the 3.1 plugin list. > > > Records is now part of GRAMPS, so don't wait for it ;-) > > Benny > Thanks. I wondered about that! Doug |
From: Duncan L. <dun...@gm...> - 2009-03-12 05:36:42
|
2009/3/8 Jérôme <rom...@ya...>: > The safety way for database migration is to export to GRAMPS XML format > before updgrade and to import it into the new version. If this is the agreed preference then why don't we say this during the install of each major release? Duncan |
From: Stéphane C. <ste...@gm...> - 2009-03-12 07:18:22
|
> 2009/3/8 Jérôme <rom...@ya...>: >> The safety way for database migration is to export to GRAMPS XML format >> before updgrade and to import it into the new version. Personally, I disagree. Or rather, I don't contest whether or not it is a safer method. The part I disagree with is that we'd tell our users this is the method they should use on upgrades. We need to ensure data is upgraded correctly between releases. Especially for people who are not computer savy, telling them to export and re-import is a burden. And while we currently suffered through an upgrade problem in 3.1.0, who is to say that in 3.1.2 we wont accidentally introduce an XML import bug? Or that in 3.1.1 we don't already have an XML export bug? It doesn't necessarily make the XML a safer way to upgrade. Stéphane |
From: Jérôme <rom...@ya...> - 2009-03-12 08:04:36
|
Personally, I find XML a safer way too, because: * we make a backup and if to export XML doesn't work, then we don't make the migration (need to fix error) ! * XML format is human readable, can check data or a quick diff with .sh script and common commands, etc .. I agree binary format is faster and in the past some data were not properly managed by XML but maybe I rather trust myself than my PC ! Jérôme Stéphane Charette a écrit : >> 2009/3/8 Jérôme <rom...@ya...>: >>> The safety way for database migration is to export to GRAMPS XML format >>> before updgrade and to import it into the new version. > > Personally, I disagree. Or rather, I don't contest whether or not it > is a safer method. > > The part I disagree with is that we'd tell our users this is the > method they should use on upgrades. We need to ensure data is > upgraded correctly between releases. Especially for people who are > not computer savy, telling them to export and re-import is a burden. > > And while we currently suffered through an upgrade problem in 3.1.0, > who is to say that in 3.1.2 we wont accidentally introduce an XML > import bug? Or that in 3.1.1 we don't already have an XML export bug? > It doesn't necessarily make the XML a safer way to upgrade. > > Stéphane > |
From: Benny M. <ben...@gm...> - 2009-03-12 08:34:56
|
2009/3/12 Stéphane Charette <ste...@gm...> > > 2009/3/8 Jérôme <rom...@ya...>: > >> The safety way for database migration is to export to GRAMPS XML format > >> before updgrade and to import it into the new version. > > Personally, I disagree. Or rather, I don't contest whether or not it > is a safer method. > I believe the present way is the good way: you click a database, you get a notice it will be upgraded and if you agree. If this is your really important data, you will think at that moment: 'Do I have a backup somewhere?' That need not be an xml file. If the user presses continue, we upgrade the database, which happens on best practices. Note that the error who started this thread was due to an incomplete upgrade. This is easily fixed, as proven by Doug. In development code we don't bother to fix half-upgraded data, but as 3.1.0 was released, Doug did add the code to fix half-upgraded data and make it fully upgraded. So, this is actually better than an xml export/import that might have a bug you never know of. Hence, the way I do it is: 1/I take a backup as a .gramps xml file 2/I upgrade the family tree in GRAMPS, 3/I take immediately a new backup as .gramps xml 4/I continue working with the family tree. I suggest you do the same. Benny PS: I believe xml export/import works ok by the way :-) > The part I disagree with is that we'd tell our users this is the > method they should use on upgrades. We need to ensure data is > upgraded correctly between releases. Especially for people who are > not computer savy, telling them to export and re-import is a burden. > > And while we currently suffered through an upgrade problem in 3.1.0, > who is to say that in 3.1.2 we wont accidentally introduce an XML > import bug? Or that in 3.1.1 we don't already have an XML export bug? > It doesn't necessarily make the XML a safer way to upgrade. > > Stéphane > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Johan V. <jvr...@sq...> - 2009-03-12 11:13:50
|
Benny Malengier <ben...@gm...> writes: > Hence, the way I do it is: > 1/I take a backup as a .gramps xml file > 2/I upgrade the family tree in GRAMPS, > 3/I take immediately a new backup as .gramps xml > 4/I continue working with the family tree. I always archive a new revision before the upgrade, and again immedeately after the upgrade. I assume that equally safe? -- Johan |
From: Doug <dou...@on...> - 2009-03-12 10:38:46
|
Duncan Lithgow wrote: > 2009/3/12 Benny Malengier <ben...@gm...>: > >> Hence, the way I do it is: >> 1/I take a backup as a .gramps xml file >> 2/I upgrade the family tree in GRAMPS, >> 3/I take immediately a new backup as .gramps xml >> 4/I continue working with the family tree. >> > > But I'm getting errors with my XML export, which I read is because > it's from 3.0.4 not some other version. > http://www.gramps-project.org/bugs/view.php?id=2814 > > Duncan > When I first posted the error in 3.1.1 at the beginning of this thread, I had tried to export the (3.0.4-1) database and re-import it. I also got Duncan's XML error on export. I scrubbed 3.1.1, went back to 3.0.4-1, exported the database under 3.0.4-1; then went back again to 3.1.1. The database imported OK, but the Check and Repair Database was flawed, as originally posted. Doug |
From: Doug B. <dou...@gm...> - 2009-03-12 10:47:26
|
On Thu, Mar 12, 2009 at 6:34 AM, Doug <dou...@on...> wrote: > Duncan Lithgow wrote: > > 2009/3/12 Benny Malengier <ben...@gm...>: > > > >> Hence, the way I do it is: > >> 1/I take a backup as a .gramps xml file > >> 2/I upgrade the family tree in GRAMPS, > >> 3/I take immediately a new backup as .gramps xml > >> 4/I continue working with the family tree. > >> > > > > But I'm getting errors with my XML export, which I read is because > > it's from 3.0.4 not some other version. > > http://www.gramps-project.org/bugs/view.php?id=2814 > > > > Duncan > > > When I first posted the error in 3.1.1 at the beginning of this thread, > I had tried to export the (3.0.4-1) database and re-import it. > > I also got Duncan's XML error on export. > > I scrubbed 3.1.1, went back to 3.0.4-1, exported the database under > 3.0.4-1; then went back again to 3.1.1. The database imported OK, but > the Check and Repair Database was flawed, as originally posted. > The "XML error on export" is the Glade error (right?) and appears to either be caused by not uninstalling an older GRAMPS first, or a problem in older underlying libraries. Duncan or Doug: can you try uninstalling and then installing 3.1.1? -Doug S. > > Doug > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Duncan L. <dun...@gm...> - 2009-03-12 11:20:21
|
2009/3/12 Doug Blank <dou...@gm...>: > Duncan or Doug: can you try uninstalling and then installing 3.1.1? Sadly that made no difference: 154555: ERROR: _Tool.py: line 252: Failed to start tool. Traceback (most recent call last): File "/usr/share/gramps/PluginUtils/_Tool.py", line 248, in gui_tool tool_class(dbstate, uistate, options_class, name, callback) File "/home/duncan/.gramps/plugins/Check312.py", line 205, in __init__ Report(uistate, checker.text.getvalue(),cli) File "/home/duncan/.gramps/plugins/Check312.py", line 1612, in __init__ topDialog = glade.XML(glade_file,"summary","gramps") RuntimeError: could not create GladeXML object System Information: =================== Python version: 2.6.1+ (r261:67515, Mar 2 2009, 13:10:18) [GCC 4.3.3] BSDDB version: 4.7.3 Gramps version: 3.1.1-1 LANG: en_DK.UTF-8 OS: Linux Distribution: 2.6.28-9-generic |
From: Doug <dou...@on...> - 2009-03-12 14:17:30
|
Doug Blank wrote: > > > On Thu, Mar 12, 2009 at 6:34 AM, Doug <dou...@on... > <mailto:dou...@on...>> wrote: > > Duncan Lithgow wrote: > > 2009/3/12 Benny Malengier <ben...@gm... > <mailto:ben...@gm...>>: > > > >> Hence, the way I do it is: > >> 1/I take a backup as a .gramps xml file > >> 2/I upgrade the family tree in GRAMPS, > >> 3/I take immediately a new backup as .gramps xml > >> 4/I continue working with the family tree. > >> > > > > But I'm getting errors with my XML export, which I read is because > > it's from 3.0.4 not some other version. > > http://www.gramps-project.org/bugs/view.php?id=2814 > > > > Duncan > > > When I first posted the error in 3.1.1 at the beginning of this > thread, > I had tried to export the (3.0.4-1) database and re-import it. > > I also got Duncan's XML error on export. > > I scrubbed 3.1.1, went back to 3.0.4-1, exported the database under > 3.0.4-1; then went back again to 3.1.1. The database imported OK, but > the Check and Repair Database was flawed, as originally posted. > > > The "XML error on export" is the Glade error (right?) and appears to > either be caused by not uninstalling an older GRAMPS first, or a > problem in older underlying libraries. I can't remember for sure, but you're probably right this happened when I had put 3.1.1 on top of 3.1.0 . (The underlying libraries were definitely OK, as that's the first thing I check before upgrading anything). Everything's fine, now I'm entirely in 3.1.1. Doug > > Duncan or Doug: can you try uninstalling and then installing 3.1.1? > > -Doug S. > |