Python 3 database upgrade renders gramps unusable for languages other than English
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | gramps (Debian) |
Fix Released
|
Unknown
|
||
| | gramps (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
Version 4.1.1~dfsg-2 of Gramps is now using Python 3. Upgrading to Python 3 requires a database upgrade, and unfortunately there are several bugs caused by strings being converted in the ASCII format during the upgrade instead of the required Unicode.
After that, Gramps is unusable for users with special (non-English) characters in their database.
The bug has been fixed by the Gramps Project, and a patch applied in Debian. I will apply the same patch in Ubuntu and recommend that it is uploaded before the Vivid (15.04) release despite the current freeze.
Related branches
| Scott Kitterman (kitterman) wrote : | #1 |
| Ross Gammon (rosco2) wrote : | #2 |
Working on it now :-)
| Changed in gramps (Ubuntu): | |
| assignee: | nobody → Ross Gammon (retail-0) |
| Changed in gramps (Debian): | |
| status: | Unknown → Fix Released |
| Changed in gramps (Ubuntu): | |
| assignee: | Ross Gammon (retail-0) → nobody |
| Steve Langasek (vorlon) wrote : | #3 |
This bug was fixed in the package gramps - 4.1.1~dfsg-3
---------------
gramps (4.1.1~dfsg-3) unstable; urgency=medium
* Add patch to fix bugs when database upgraded to Python 3 (Closes: #779308)
-- Ross Gammon <email address hidden> Thu, 26 Feb 2015 21:57:31 +0100
| Changed in gramps (Ubuntu): | |
| status: | New → Fix Released |
The current freeze is only for new features, not bug fixes like this, so please don't think the freeze hinders fixing this.