Bug 13584

Summary:	Please update GRAMPS to 4.1
Product:	Mageia	Reporter:	Marcus Zurhorst <marcuszurhorst>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	fiable, thierry.vignaud
Version:	4
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Marcus Zurhorst 2014-06-23 22:23:31 CEST

Please update GRAMPS to newly released version 4.1 [1] when this is still possible for the next release.

Gramps 4.1 has once more significant improvements and comes along with important fixes when interacting with other genealogy tools via GEDCOM file imports/exports.




[1]  https://gramps-project.org/2014/06/gramps-4-1-0-released/

Thierry Vignaud 2014-06-24 17:38:27 CEST

CC: (none) => thierry.vignaud
Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2014-06-24 19:21:41 CEST

Just uploaded

Status: NEW => RESOLVED
Hardware: i586 => All
Resolution: (none) => FIXED

Comment 2 Henri de Solages 2014-11-09 13:20:44 CET

For Mageia 4 too.

Status: RESOLVED => REOPENED
CC: (none) => fiable
Resolution: FIXED => (none)

Comment 3 Henri de Solages 2014-11-09 14:03:03 CET

Version 4.0.1 seems to have a bug breaking the update of some Gramps 3 databases. I just can't read my former genealogy. I get:

28841: ERROR: dbloader.py: line 107: global name 'UNITYPE' is not defined
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/gramps/gui/dbloader.py", line 322, in read_file
    force_python_upgrade)
  File "/usr/lib/python2.7/site-packages/gramps/gen/db/write.py", line 284, in try_
    return func(self, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/gramps/gen/db/write.py", line 730, in load
    self.gramps_upgrade(callback)
  File "/usr/lib/python2.7/site-packages/gramps/gen/db/write.py", line 2145, in gramps_upgrade
    upgrade.gramps_upgrade_16(self)
  File "/usr/lib/python2.7/site-packages/gramps/gen/db/upgrade.py", line 148, in gramps_upgrade_16
    if isinstance(handle, UNITYPE):
NameError: global name 'UNITYPE' is not defined 

It seems this bug has been corrected later: 
http://sourceforge.net/p/gramps/code/22739/

So I suggest to update Mageia 4.

Version: Cauldron => 4
Severity: normal => major

Manuel Hiebel 2014-11-10 23:22:40 CET

Component: New RPM package request => RPM Packages

Comment 4 Samuel Verschelde 2015-09-21 13:21:32 CEST

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Comment 5 Marja Van Waes 2015-10-27 06:58:31 CET

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too).

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: REOPENED => RESOLVED
Resolution: (none) => OLD