Bug 16284

Summary: Can't open gramps database from version 4.1.1 with version 5 due to different bsddb version
Product: Mageia Reporter: Norbert Kieffer <nk0885>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal    
Version: 5   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: gramps CVE:
Status comment:
Attachments: Gramps warning

Description Norbert Kieffer 2015-07-03 16:03:44 CEST 
Description of problem:
After Mageia Upgrade to Version 5 it is Impossible to open my existing Gramps Data base (Gramps 4.1.1)
Message (picture herewith) is I should upgrade Bsddb to 5.3.28 (the existing is 5.3.21).
Where do I find the corresponding RPM for ugrading Python data base ?


Version-Release number of selected component (if applicable):


How reproducible:
At each Gramps opening

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Rémi Verschelde 2015-07-03 16:10:49 CEST 
Please put a meaningful summary next time, "Gramps" doesn't tell us anything about what the issue is.

The bug report page even gives you an example about what is a bad summary:

"Summary: A sentence that summarizes the problem. Please be descriptive and use lots of keywords.

Bad example: mail crashed
Good example: crash in Evolution while checking for new POP mail"

Summary: Gramps => Can't open gramps database from version 4.1.1 with version 5 due to outdated bsddb
Source RPM: Bsddb => gramps

Comment 2 Norbert Kieffer 2015-07-03 16:13:21 CEST 
Created attachment 6802 [details]
Gramps warning
Rémi Verschelde 2015-07-03 16:18:06 CEST

Summary: Can't open gramps database from version 4.1.1 with version 5 due to outdated bsddb => Can't open gramps database from version 4.1.1 with version 5 due to different bsddb version

Comment 3 Rémi Verschelde 2015-07-03 16:19:37 CEST 
According to the warning, the bsddb version in gramps 5 is 5.3.28. You don't need to update bsddb, you just need to allow gramps to upgrade your own database which was created with bsddb 5.3.21.

This does not look like a bug to me. Just make a backup of your database, and try what gramps proposes you.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 4 Norbert Kieffer 2015-07-03 22:23:06 CEST 
I've tried your solution.
It works fine.
You are right, it's not a Bug !
Thank you.
SOLVED