Package: jppy-jpilot-plugins Version: 0.0.45-1 Severity: serious Tags: upstream
Unless python2.5-dev is installed, jpilot can't spawn the jppy
plugin but instead writes on startup:
jppy: Starting...
libpython2.5.so: cannot open shared object file: No such file or
directory
piper:~|master|% ls -l /usr/lib/libpython2.5.so /usr/lib/libpython2.5.so.1;
dpkg -S /usr/lib/libpython2.5.so /usr/lib/libpython2.5.so.1.0
lrwxrwxrwx 1 root root 17 2008-07-22 14:10 /usr/lib/libpython2.5.so ->
libpython2.5.so.1
lrwxrwxrwx 1 root root 19 2008-07-13 21:51 /usr/lib/libpython2.5.so.1 ->
libpython2.5.so.1.0
python2.5-dev: /usr/lib/libpython2.5.so
python2.5: /usr/lib/libpython2.5.so.1.0
Yet, the plugin seems to be linked properly:
piper:~|master|% ldd /usr/lib/jpilot/plugins/libjppy.so | grep pyth
libpython2.5.so.1.0 => /usr/lib/libpython2.5.so.1.0 (0x00007febb2f26000)
This seems to be due to
jpilot_plugins/jppy.c:210:
// we seem to have to do this, as well as just linking this plugin
// to the python library, otherwise init_pygobject() causes the
// plugin to stop-and-exit. If we only do this and don't link,
// then we get··
// error [/usr/lib/jpilot/plugins/libjppy.so: undefined symbol:
PyExc_ImportError]
if (!dlopen (PYTHON_SHARED_LIB, RTLD_NOW | RTLD_GLOBAL)) {·
jp_logf(JP_LOG_FATAL, "\n%s\n", dlerror());·
python_is_working = 0;·
return 0;·
}·
and SConstruct:194:
jppyPluginEnv.Append(CPPDEFINES=['PYTHON_SHARED_LIB=\\"libpython${python_version}.so\\"'])
If we remove all this code, the plugin fails to load and jpilot just
says:
Python is not running, unable to generate GUI!
but I could get it to say anything about PyExc_ImportError, even
with jpilot's -d flag.
I'd say this is quite a horrible hack and we should try to get rid
of it, but if that fails, then PYTHON_SHARED_LIB needs to be defined
to point to the same .so.* file with which the plugin is linked,
which I suppose has to be determined with
readlink -f /usr/lib/libpython2.5.so
(which would work during build on Debian at least).
With PYTHON_SHARED_LIB set to libpython2.5.so.1.0, stuff still
doesn't work, however:
jppy: Ready.
(-v:22246): libglade-WARNING **: could not find glade file
'@@python_module_prefix@@/gui/contacts.glade'
Traceback (most recent call last):
File "/usr/lib/jpilot/plugins/jpilot_site.py", line 6, in plugin_gui
combined.notebook(hbox, control_mainloop=0)
File "jppy/gui/combined.py", line 22, in __init__
self.panes.append(contacts.pane(glade_path))
File "jppy/gui/contacts.py", line 47, in __init__
wTree = gtk.glade.XML(gladefile,"vpanedContacts")
RuntimeError: could not create GladeXML object
Warning! Failed during python version of plugin_gui().
Is the only solution to depend on python2.5-dev???
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages jppy-jpilot-plugins depends on:
ii jppy 0.0.45-1 Personal Information Manager using
ii libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii libc6 2.7-12 GNU C Library: Shared libraries
ii libcairo2 1.6.4-6 The Cairo 2D vector graphics libra
ii libglib2.0-0 2.16.4-2 The GLib library of C routines
ii libgtk2.0-0 2.12.11-2 The GTK+ graphical user interface
ii libpango1.0-0 1.20.5-1 Layout and rendering of internatio
ii python2.5 2.5.2-8 An interactive high-level object-o
Versions of packages jppy-jpilot-plugins recommends:
ii jpilot 1.6.0-1 graphical app. to modify the conte
jppy-jpilot-plugins suggests no packages.
-- no debconf information
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
