setup.py doesn't seem to install all files under F14

Bug #674931 reported by Andrea Musuruane
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Genesis Sync
Incomplete
Undecided
Unassigned

Bug Description

Using Fedora 14, setup.py doesn't seem to install all required files to run genesis-sync. For example, desktop files and translation ("mo") files are not installed.

BTW, Fedora 14 has python 2.7, if this can help.

Revision history for this message
Andrea Musuruane (musuruan) wrote :
Revision history for this message
Frederik Elwert (frederik-elwert) wrote :

Thank you for the bug report, and please excuse the late reply.

Unfortunately, I am neither using Fedora nor setup.py (directly), I am normally rather building deb packages from source. The implicit setup.py calls during the package creation process seem to work, so I’d need a bit more information from you.

* Which version of Genesis do you use?
* Which version of python-distutils-extra do you have installed?
* How did you call setup.py (which commands, any options)?
* Are there any error messages (maybe you could attach the output of setup.py)?

Thanks!

Changed in genesis-sync:
status: New → Incomplete
Revision history for this message
Andrea Musuruane (musuruan) wrote :

$ python -V
Python 2.7

* Which version of Genesis do you use?
0.6.2

* Which version of python-distutils-extra do you have installed?
python-distutils-extra-2.19-2

* How did you call setup.py (which commands, any options)?
python setup.py build
python setup.py install --skip-build

* Are there any error messages (maybe you could attach the output of setup.py)?
Attached.

A similar problem has been reported for Mandriva:
https://qa.mandriva.com/show_bug.cgi?id=60905
("the setup.py script didn't run to completion on Mandriva")

Anyway, since you used Ubuntu specific things like application indicators I am unable to continue to use genesis on Fedora and I will no longer maintain this package in Fedora.

Revision history for this message
Frederik Elwert (frederik-elwert) wrote :

Thanks for the information!

I am trying to keep Genesis distribution agnostic, and do not intend to turn it into an Ubuntu only application. But since I only use Ubuntu, I am not always able to test it properly. So any feedback from other distributions is welcome, and active help even more so.

Genesis does not (or at least should not) depend on Ubuntu specific features like AppIndicators. Genesis has two separate modules for status indication, one based on AppIndicator, and one based on StatusIcon (which is standard GTK). The latter is not tested as thoroughly, but should work as well. So I would encourage you to use Genesis on Fedora and inform me about issues you run into.

As regarding to setup.py, I compared you log to the one of dpkg-buildpackage, which calls setup.py to create the debian package. It looks like under Fedora, build_i18n isn’t called during build. That creates the .mo files from the .po files, and the .desktop file from the .desktop.in file, and puts them directly into the build directory. Since that is not done, these files are missing from you install.

I have no idea why this isn’t done, and I must confess that I am not too familiar with distutils and all its details. But maybe you could try calling “python setup.py build_i18n” manually after the regular build and see if that works.

Revision history for this message
Andrea Musuruane (musuruan) wrote :

I just pasted you the output of "python setup.py install --skip-build". mo files are created correctly during "python setup.py build" but they are not installed. The other thing that is not installed is the desktop file.

Anyway, you seems to use at least one component that is Ubuntu specific: apport.

Moreover, if I manually install the missing bits and I run genesis I get the following error:
$ genesis-sync
Traceback (most recent call last):
  File "/usr/bin/genesis-sync", line 388, in <module>
    GenesisSync()
  File "/usr/bin/genesis-sync", line 71, in __init__
    self._syncevo_server = get_server_interface()
  File "/usr/lib/python2.7/site-packages/genesis_sync/helpers.py", line 62, in get_server_interface
    'org.syncevolution.Server')
  File "/usr/lib/python2.7/site-packages/genesis_sync/helpers.py", line 53, in get_dbus_interface
    obj = _session_bus.get_object(name, path)
  File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/libexec/syncevo-dbus-server exited with status 127

It might be I miss some python modules.

Revision history for this message
Frederik Elwert (frederik-elwert) wrote :

Sorry, I might be blind, but I cannot find the build output, where did you paste it?

Strange that the translation specific files are not installed even if they are built. But as I said, I am not that familiar with distutils.

Right, apport support is automatically added by quickly. It should be save to leave it out, it is nowhere used except for the file being present. I guess it is save to exclude it for Fedora packaging.

Regarding the error message: That looks rather like a SyncEvolution error than a Genesis error. syncevo-dbus-server simply dies when Genesis tries to access it. You could try running /usr/libexec/syncevo-dbus-server in a terminal and see if there is a more verbose error message in it when you start Genesis. But I guess this should be solved in the syncevolution package before trying to make Genesis run.

Revision history for this message
Andrea Musuruane (musuruan) wrote :

I didn't attach the build output. I'm doing it right now.

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.