Execution of Genesis fails on Karmic.

[Charlie Powell]

When installing version 0.4.2.1 on Ubuntu Karmic and Python 2.6.4, execution of the binary fails on error:

Traceback (most recent call last):
  File "bin/genesis", line 22, in <module>
    from Genesis import config
ImportError: No module named Genesis

Upon further investigation, the required packages were installed into /usr/lib/python2.6/site-packages, but python was only looking in /usr/lib/python2.6/dist-packages. I'm not sure if this is a bug with python or genesis-sync but...

The way I got around the issue was by running this:

sudo ln -s /usr/lib/python2.6/site-packages/Genesis/ /usr/lib/python2.6/dist-packages/
sudo ln -s /usr/lib/python2.6/site-packages/genesis-0.4.2.1-py2.6.egg-info /usr/lib/python2.6/dist-packages/

[davidcaste (davidcaste)]

Hi!!

This is very very strange. How have you installed Genesis Sync?, have you used the DEB package, or the setup.py install method instead? Please describe a little more your system, so we can reproduce your problem (and fix it!).

Cheers

[Charlie Powell (powellc)]

I downloaded the source tarball and ran the python setup script:

sudo python setup.py install --prefix /usr

As for more info about the system...
2.6.31-14-generic kernel,
Ubuntu 9.10 Karmic 64-bit
Python 2.6.4 (2.6.4-0ubuntu1)

[Frederik Elwert (frederik-elwert)]

This is unfortunately a known problem, see bug #362570.

First, on Debian/Ubuntu I’d always recommend using the deb package from the PPA. Distutils installations are hell to get rid of, so using the package management is almost always the better way to go.

Second, up to recently, we had problems with installing Genesis to /usr/local. This is why the --prefix thing was recommended. Unfortunately I didn’t think of that Ubuntu bug, so this breaks on current Ubuntu versions. Once /usr/local is fixed as a possible installation path for Genesis (which should be in the next release, thanks to David’s work), you should be able to simply omit the --prefix.

I’m afraid there’s not much we can do about this, so I’d recommend just using the deb package for now or wait for the next release.

[davidcaste (davidcaste)]

Right now it's too late to try to reproduce it, but tomorrow I'll try.

The setup.py install method is known to not work in versions 0.4.2 and 0.4.2.1. Some works has been done to fix it, you definitely should take a look to branch lp:~genesis-devs/genesis-sync/0.4.2-fixes, and try to install again using it. It has been tested in Fedora 12 and Ubuntu Karmic, but it would be great if you could tested it too.

ON the other hand, it is recommended to install Genesis Sync using the DEB packages provided by Frederik Elwert in his PPA archive [1]; they are far more tested the setup.py install method, and they're easier to install, update and uninstall.

Although the bug seems to be a duplicate of bug # 433434, I won't mark it as duplicated until I have time to test it enough. So please, if you have enough interest I would like you to test the setup.py install method from lp:~genesis-devs/genesis-sync/0.4.2-fixes branch, or otherwise please install Genesis Sync using the DEB package.

Thank you very much for your attention :-)

[1] https://launchpad.net/~frederik-elwert/+archive/ppa/+packages

[davidcaste (davidcaste)]

Ups, Frederik has reason, it isn't a duplicate of bug #433434, I agree too that is a duplicate of bug #362570.

I don't know if branch lp:~genesis-devs/genesis-sync/0.4.2-fixes will work in this scenario, but it would be very interesting to test it.

Thank you both Frederik and Charlie :-)

[Charlie Powell (powellc)]

Just tried the 0.4.2-fixes branch... wonderful! All the issues I was having have been fixed.

Although I do have one note about the readme..... shouldn't the preferred method for installation be at the top of the Installation section? I, being one to jump right into some project without reading everything in full, neglected to even see that last line in there.

[Frederik Elwert (frederik-elwert)]

Your’re right, I’ll work on the README before the next release.

I’m glad to hear that David’s work fixed the issues for you.