From: Douglas S. B. <db...@cs...> - 2008-08-07 13:46:49
|
> Doug, did you not change compound dates? I don't think I have have changed anything that would cause the issue below. I haven't touched the XML yet, but I don't think that should be an issue. It looks like a mixed-up set of files from one version with files from another. -Doug > The problems you mention with .grdb files are all gone in version 3.0.1. > It would be nice if somebody updates any hanging wiki pages which > misrepresent the issue. > > About your new error. Are you using trunk by any chance? I know some > date things changed there. The XML of v2 should import in branch 30 > and in trunk however, not doing so is a serious bug. Can you submit a > bug ticket please and attach the full error message. > > > Benny > > > 2008/8/4, lis...@le... > <lis...@le...>: >> Hi, >> >> thanks for your reply. I believe this is the wiki page you mean: >> http://gramps-project.org/wiki/index.php?title=Recover_corrupted_grdb >> >> I tried the dump/load with my db tools but the resuting file gave me an >> "unsupported hash version" error in gramps. I used lower version db >> tools >> (4.5) and I've managed to rescue the database. >> >> I was actually aware that gramps used additional files for the database, >> but I didn't think you'd still need them if you used the export >> function. >> What's the point of an export function if the resulting file is useless >> without the original files? >> It doesn't really help that the relevant page in the documentation makes >> no mention of this requirement, and makes it look like the grdb export >> is >> the preferred format by listing it first. The description of the XML >> format >> you mention suggests that its purpose is for backwards compatibility: >> http://gramps-project.org/gramps-manual/2.2/en/ch03s05.html >> >> I tried to upgrade back to gramps 3, but exporting the database to XML >> in >> v2 and then importing in in v3 gives this error: >> >> 28917: ERROR: DbLoader.py: line 306: Failed to import database. >> Traceback (most recent call last): >> File "/usr/share/gramps/DbLoader.py", line 296, in do_import >> self.uistate.pulse_progressbar) >> File "/usr/share/gramps/GrampsDbUtils/_ReadXML.py", line 112, in >> importData >> info = parser.parse(xml_file, use_trans, line_cnt, person_cnt) >> File "/usr/share/gramps/GrampsDbUtils/_ReadXML.py", line 745, in >> parse >> self.p.ParseFile(ifile) >> File "/usr/share/gramps/GrampsDbUtils/_ReadXML.py", line 2284, in >> startElement >> f(attrs) >> File "/usr/share/gramps/GrampsDbUtils/_ReadXML.py", line 1663, in >> start_datespan >> self.start_compound_date(attrs, gen.lib.Date.MOD_SPAN) >> File "/usr/share/gramps/GrampsDbUtils/_ReadXML.py", line 1713, in >> start_compound_date >> cal = gen.lib.Date.calendar.index(attrs['calendar']) >> AttributeError: class Date has no attribute 'calendar' >> >> I tried searching the list archives, but like most things sourceforge, >> the >> mail archive servers suck ass. Any idea how I can fix this? I'm working >> on >> 2.2.10 for now. >> >> >> Anyway, thanks for your help, >> >> Guser >> >> On Mon, 4 Aug 2008, Benny Malengier wrote: >>> The grdb format is a database, and consists of a file and an >>> environment (located under linux in the hidden /.gramps directory). >>> The many problems with this setup leaded to version 3.0.1, where the >>> entire database is in the environment location, and no file is shown >>> to the user anymore with the problems this enshews. >>> This forces the user to to do an export to eg the .gramps xml format >>> when moving between computers, which is needed. >>> >>> So you have some options: >>> 1/your distant relatives can fire up their windows computer, start >>> gramps, open the grdb file, and export it to xml, which you can use >>> without problems. Just mailing it is ok. >>> 2/you use the dump tools to get data out of the grdb file without the >>> environment being present. See our wiki (search on the word >>> 'corruption' should give you the relevant wiki page, I'm on dial-up >>> and the wiki is to slow to search for it now). This should give you >>> your data with almost everything present. If you use Gentoo, you >>> should be able to do this ;-) >>> >>> The lesson to be learned is that grdb format is no good for moving >>> between pc's and storing data, an issue that hopefully will be fully >>> resolved in the new 3.0.x releases. >>> >>> Benny >>> >>> 2008/8/4, lis...@le... >>> <lis...@le...>: >>>> Hi, >>>> >>>> last year I was abroad with some relatives I rarely see, and I decided >>>> to >>>> make >>>> use of the opportunity to start a geneology database. I settled on >>>> gramps >>>> and >>>> since they had a Windows PC, I downloaded one of the packages, I'm not >>>> sure >>>> which version (2something). When I left I remember reading the gramps >>>> site >>>> to >>>> decide how to transfer the DB to my usb stick, and I remember >>>> exporting >>>> it, >>>> I'm >>>> not sure to what format. file(1) says: >>>> >>>> export.gramps: Berkeley DB (Btree, version 9, native byte-order) >>>> >>>> This year I'm with some other relatives and I want to add to it. I >>>> have >>>> my >>>> gentoo laptop with me and I'm trying to get to the old database with >>>> no >>>> success. I've switched back from version 3 to gramps 2.2.10 since I've >>>> read >>>> that the DB format was changed. >>>> >>>> If I do file-open with filetype on autodetect I get "Error opening >>>> <file> >>>> The >>>> file is probably either corrupt or not a valid GRAMPS database". >>>> If I create a new database with file-new and then do file-import with >>>> filetype >>>> on autodetect I get the same error. >>>> If I try to import with filetype set to "GRAMPS package" I get the >>>> error >>>> "Error >>>> extracting into <dir>/export.gramps.media". >>>> I've tried all the other filetypes both for import and for file-open >>>> with >>>> similar errors. >>>> >>>> If I run "gramps -i export.gramps" I get "GRAMPS has experienced an >>>> unexpected >>>> error" with error detail: >>>> 1956: ERROR: gramps.py: line 179: Gramps terminated with the following >>>> message: >>>> 'Error importing export.gramps'. >>>> Traceback (most recent call last): >>>> File "/usr/share/gramps/gramps.py", line 172, in run >>>> gramps_main.Gramps(args) >>>> File "/usr/share/gramps/gramps_main.py", line 232, in __init__ >>>> ah.handle_args() >>>> File "/usr/share/gramps/ArgHandler.py", line 407, in handle_args >>>> self.cl_import(imp[0],imp[1]) >>>> File "/usr/share/gramps/ArgHandler.py", line 473, in cl_import >>>> sys.exit(msg) >>>> SystemExit: Error importing export.gramps >>>> >>>> What am I doing wrong? >>>> >>>> >>>> Thanks, >>>> >>>> Guser >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge >>>> Build the coolest Linux based applications with Moblin SDK & win great >>>> prizes >>>> Grand prize is a trip for two to an Open Source event anywhere in the >>>> world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> _______________________________________________ >>>> Gramps-users mailing list >>>> Gra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>>> >>> >> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |