-
Notifications
You must be signed in to change notification settings - Fork 86
londiste3 error with import pkgloader #42
Comments
What is the output of You might also consider building using setuptools instead. |
Forgot to update here, I fixed my issue by running londiste3 this way:
@cdown Thanks for your quick reply :) |
I have just faced the same error on Ubuntu 12.0.4, PostgreSQL 9.2 and Skytools3 3.2.6-3.pgdg12.4+1 when I was setting up a new server. root@xxx:~# service skytools3 start Please note that there were no such issues with the other 7 servers with Ubuntu 12.0.4, PostgreSQL 9.2 and Skytools3 3.1.5-1.pgdg12.4+1 that I setup several months ago. |
I've found out that earlier skytools was installed under /usr/lib/pymodules/python2.7/ root@yyy:~# ls -l /usr/lib/pymodules/python2.7/ root@xxx:~# python -c 'import sys; print(sys.version); print(sys.path)' and now it is installed under /usr/lib/python2.7/site-packages/ root@xxx:~# ls -l /usr/lib/python2.7/site-packages/ root@yyy:~# python -c 'import sys; print(sys.version); print(sys.path)' that is not in the python path. |
So my workaround is root@yyy: |
I had a similar error though for completely different reasons. It looks like Skytools installed everything under /usr/local/local/.. (i.e. an extra local) which broke all the paths stuff. This is running on:
Am going to try and find out why it installed to a bad path. |
modifying |
My server is running Debian 7.8, with Postgresql-9.3 (9.3.6-1.pgdg70+1)
I want to use Londiste replication. I have installed the following Skytools package via apt-get install:
python-skytools3 3.2.6-3.pgdg70+1
skytools-modules-9.3 2.1.13-4.pgdg70+2
skytools3 3.2.6-3.pgdg70+1
After installation, upon running
londiste
command, or evenservice skytools3 start
, I run into this error:Traceback (most recent call last):
File "/usr/bin/scriptmgr3", line 48, in
import pkgloader
ImportError: No module named pkgloader
Trying
locate pkgloader.py
give me this:/usr/lib/python2.7/site-packages/pkgloader.py
Any pointers here will be greatly appreciated, thanks!
The text was updated successfully, but these errors were encountered: