gramps 3.1.2 in Karmic should allow python2.5 or python2.6

Bug #431059 reported by Jeff Stone
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gramps (Debian)
Fix Released
Unknown
gramps (Ubuntu)
Fix Released
Undecided
Unassigned
Declined for Lucid by Alessio Treglia

Bug Description

Binary package hint: gramps

Hi, the summary pretty much says it all, I've checked with Benny (<email address hidden>) from the GRAMPS mailing list (<email address hidden>) who said:

I believe gramps works fine with python 2.6, there is no reason for
python-2.5 only, >= 2.5 should be all needed (but 3.0 will not work
obviously).
You should notify the packager if there is an issue with the karmic package.

There's also this page http://gramps-project.org/wiki/index.php?title=Python2.6 which seems to confirm that GRAMPS is just fine with 2.6.

I think the package should require either python2.5 or python2.6 (but not 3.0). As it is currently, it requires python2.5 and python >= 2.5.

I don't know if this should go to the people at Debian, if so how should I proceed? I'm just a guy sitting in my living room so my apologies if I've done anything incorrectly.

I can help you verify the fix if something is implemented.

My eternal gratitude to everyone at Ubuntu,

Jeff

Revision history for this message
Alessio Treglia (quadrispro) wrote :

Forwarding to Debian maintainer

Changed in gramps (Ubuntu):
status: New → Triaged
Changed in gramps (Debian):
status: Unknown → New
Revision history for this message
Jeff Stone (stone1343) wrote :

I've been trying to be sure that everything will work with python2.6, so I figured out how to modify the package to require python2.6 instead on python2.5. Then I got this error:

jeff@ubuntu-karmic:~$ sudo dpkg -i gramps_3.1.2-1_all.deb
Selecting previously deselected package gramps.
(Reading database ... 110906 files and directories currently installed.)
Unpacking gramps (from gramps_3.1.2-1_all.deb) ...
Setting up gramps (3.1.2-1) ...
Traceback (most recent call last):
  File "/usr/bin/pycentral", line 2190, in <module>
    main()
  File "/usr/bin/pycentral", line 2184, in main
    rv = action.run(global_options)
  File "/usr/bin/pycentral", line 1496, in run
    self.options.exclude, byte_compile_default=True)
  File "/usr/bin/pycentral", line 1092, in install
    self.default_runtime.byte_compile(self.private_files, bc_option,
AttributeError: 'NoneType' object has no attribute 'byte_compile'
dpkg: error processing gramps (--install):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for shared-mime-info ...
Processing triggers for desktop-file-utils ...
Processing triggers for man-db ...
Processing triggers for gnome-icon-theme ...
Errors were encountered while processing:
 gramps

I'm learning all this as I go along, but I see postinst failed in pycentral, and I can see the offending code in pycentral:

        if byte_compile_default:
            if self.private_files:
                self.default_runtime.byte_compile(self.private_files, bc_option,
                                                  exclude_regex, ignore_errors)

That tells me that self.default_runtime is null, but I've changed PythonVersion in the control file to 2.6.

I found a file called /usr/share/pycentral-data/pyversions.py that says supported_versions includes only python2.4 and 2.5. So now, I don't know if this is a bug in pycentral (doubt it) or whether there is a replacement for pycentral with python2.6 (more likely) or whether this is related in some way to bug #353251

I don't know if pycentral is part of Python or what it is, so I can't proceed any further for now.

Changed in gramps (Debian):
status: New → Fix Released
Revision history for this message
Jeff Stone (stone1343) wrote :

Now that this has been fixed in Debian, is there anything I need to do to get it into Lucid? Thanks

Revision history for this message
Alessio Treglia (quadrispro) wrote :

Sync from debian unstable has been requested.

Revision history for this message
Alessio Treglia (quadrispro) wrote :

Please see bug #487126

Changed in gramps (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.