Bug#574741: jppy: FTBFS on ia64: segmentation fault (unaligned
tags 574741 + pending thanks This was caused by an incorrect assumption about some types, see http://git.debian.org/?p=jppy/jppy.git;a=commitdiff;h=24a281fed9b52427a061f7187d26ed32507e9b49 I hope that a new package will be uploaded to Debian soon, as 0.0.56-1. (I could not reproduce the later example which fails at testSaving (basicTests.todoBasicTest), so maybe that is a separate problem?) Thank you for the report, I'm sorry it took a long while to bring my attention to it. Nick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558670: jppy: FTBFS: scons: *** Path for option pisock_library does not exist: /usr/lib64
tags 558670 + pending thanks On Thu, 18 Feb 2010, Jakub Wilk wrote: I believe that the attached patch fixes this bug. Thanks Jakub. I'm going to commit a different fix (bbfbf5f13) in a moment, which causes debian/rules to specify the path rather than use the default (which is wrong, in this case.) Nick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516304: jppy: generates incorrect package with python-support from experimental
Hi Sandro, On Wed, 14 Oct 2009, Sandro Tosi wrote: I saw you tagged 516304 as pending on July 15: do you plan an upload soon? It would be helpful to have the bug fixed asap. We have a new release almost ready ( http://git.debian.org/?p=jppy/jppy.git;a=shortlog;h=refs/heads/debian ) but it's failing to build in cowbuilder (possibly only on amd64) so we're not uploading it quite yet. It's being looked at currently. Nick -- Nick Piper GPG: 1024D/3ED8B27F Open Source advocate, System Architect, Network Engineer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537244: jppy: does not start but quits with a segmentation fault
This is because we are currently NOT compatible with libpisock9 0.12.4. You must have libpisock9 0.12.3 installed instead. The conflicts data was not updated in libpisock9 to reflect this due to an oversight. See http://lists.pilot-link.org/pipermail/pilot-link-devel/2009-July/001777.html A new jppy package (with source changes) needs to be created and uploaded with a matter of urgency, but this has not happened yet. The porting work was started, but not finished: http://git.debian.org/?p=jppy/jppy.git;a=shortlog;h=refs/heads/pilot-link-0.12.4-compat-devel I'm sorry for this trouble. Nick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516304: generates incorrect package with python-support from experimental
tags + pending thanks See http://git.debian.org/?p=jppy/jppy.git;a=commitdiff;h=4f24395a98322242ecb355ca9748b8f21366a49d;hp=b3a3c0f988974ea211ed819de0b739aff6dff4d7 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515171: jppy: homepage from long description does not exist
tags 515171 + pending -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#493082: won't start without 'sms' section in config
martin, On Thu, 31 Jul 2008, martin f krafft wrote: File /usr/lib/python2.5/ConfigParser.py, line 511, in get raise NoSectionError(section) ConfigParser.NoSectionError: No section: 'sms' Thanks - fixed in http://jppy.zanu.org.uk/trac/changeset/333 Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491848: undeclared (and wrong) dependency on python2.5-dev
martin, On Wed, 30 Jul 2008, martin f krafft wrote: also sprach Nicholas Piper [EMAIL PROTECTED] [2008.07.30.0038 +0200]: I neglected to check that it was in diff that 'svn diff' made. It's attached; but if you're happy with this approach then I'll commit to subversion - basically it's just copying find-python-library-name.sh from an old revision back to the head; and getting SCons to call it rather than debian/rules. At least it works now, so let's put it in subversion and release 0.0.46. Thank you! That's done, http://jppy.zanu.org.uk/trac/changeset/329 Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491848: undeclared (and wrong) dependency on python2.5-dev
martin, On Tue, 29 Jul 2008, martin f krafft wrote: Anyway, ./find-python-library-name.sh is now being used, where do I get that from? Is it the same as used to be in ./debian? I neglected to check that it was in diff that 'svn diff' made. It's attached; but if you're happy with this approach then I'll commit to subversion - basically it's just copying find-python-library-name.sh from an old revision back to the head; and getting SCons to call it rather than debian/rules. Nick find-python-library-name.sh Description: Bourne shell script
Bug#491848: undeclared (and wrong) dependency on python2.5-dev
martin,
On Wed, 23 Jul 2008, martin f krafft wrote:
also sprach Nicholas Piper [EMAIL PROTECTED] [2008.07.23.0045 +0200]:
* jpilot to use RTLD_GLOBAL when loading the plugins
Unfortunately, I think RTLD_GLOBAL is disabled on Debian.
22 14:13 pusling and it opens with RTLD_GLOBAL - that's patched
out of debian libltdl packages.
22 14:14 pusling does jppy ships own copy of libltdl ?
I don't know why.
I don't understand this - I use Debian (my /etc/debian_version says
lenny/sid) and the patch which makes jpilot load the plugins with
RTLD_GLOBAL appeared to work.
* our python module to -lpython (disliked by Debian)
Reference for that dislike? And why? Sorry, I am in a dozen
different projects right now and kinda lost overview.
#445379 , but I mis-thought and actually this doesn't help (I tried
it.)
This is what
http://jppy.zanu.org.uk/trac/browser/debian/trunk/find-python-library-name.sh?rev=322
used to do.
Hm, I suppose this seems like the way we need to head.
Ok, new patch attached for your consideration that dlopen()'s the
right shared python library - but note we still must use RTLD_GLOBAL
to have success... otherwise python modules that jppy uses don't have
the libpython symbols:
calling plugin_startup for [jppy 0.46pre]
jppy: Starting...
jppy: Opened python library
jppy: Initialized python
jppy: Imported os, sys
ImportError: could not import gobject (error was:
'/var/lib/python-support/python2.5/gtk-2.0/gobject/_gobject.so:
undefined symbol: _Py_ZeroStruct')
NickIndex: ChangeLog
===
--- ChangeLog (revision 328)
+++ ChangeLog (working copy)
@@ -1,3 +1,12 @@
+2008-07-25 Nicholas Piper [EMAIL PROTECTED]
+
+ * jpilot_plugins/jppy.c (plugin_startup): Remove deprecated
+ init_pygobject() call
+
+ * SConstruct: Set PYTHON_SHARED_LIB to a better filename for
+ libpython - see Debian bug
+ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491848
+
2008-06-28 Nicholas Piper [EMAIL PROTECTED]
* SConstruct: Add python_bin_module_prefix option to SCons, to
Index: jpilot_plugins/jppy.c
===
--- jpilot_plugins/jppy.c (revision 328)
+++ jpilot_plugins/jppy.c (working copy)
@@ -207,11 +207,10 @@
jp_init();
jp_logf(JP_LOG_INFO, jppy: Starting...\n);
- // 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]
+ // This is because python modules don't -lpython, combined with
+ // jpilot not loading the plugins with RTLD_GLOBAL, so the plugin's
+ // -lpython isn't then available to the python modules that it
+ // uses... See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491848
if (!dlopen (PYTHON_SHARED_LIB, RTLD_NOW | RTLD_GLOBAL)) {
jp_logf(JP_LOG_FATAL, \n%s\n, dlerror());
python_is_working = 0;
@@ -231,7 +230,12 @@
jp_logf(JP_LOG_DEBUG, jppy: Imported os, sys\n);
- init_pygobject();
+ PyObject *gobject = pygobject_init(2,4,0);
+ if (gobject == NULL) {
+PyErr_Print();
+return 0;
+ }
+
jp_logf(JP_LOG_DEBUG, jppy: Initialized pygobject\n);
PyRun_SimpleString(sys.path.insert(0,'%s/.jpilot/python' % (os.getenv('JPILOT_HOME') or os.getenv('HOME';
Index: SConstruct
===
--- SConstruct (revision 328)
+++ SConstruct (working copy)
@@ -10,6 +10,7 @@
from helpers import *
import dbhash
import SCons
+import commands
print Please remember that SCons does NOT automatically use your shell
environment variables. This script uses PKG_CONFIG_PATH explicitly.
@@ -190,15 +191,17 @@
pluginEnv.Append(CPPDEFINES=['JPILOT_PLUGIN_PREFIX=\\$jpilot_plugin_prefix\\'])
+
jppyPluginEnv = pluginEnv.Clone()
-jppyPluginEnv.Append(CPPDEFINES=['PYTHON_SHARED_LIB=\\libpython${python_version}.so\\'])
+jppyPluginEnv.Append(LINKFLAGS=distutils.sysconfig.get_config_var('LINKFORSHARED'))
jppyPluginConfig = jppyPluginEnv.Configure()
if not jppyPluginConfig.CheckLibWithHeader(libpython%s % env['python_version'],
'Python.h','C','PyErr_Clear();'):
print You need libpython%s.so to compile this program % env['python_version']
Exit(1)
jppyPluginConfig.Finish()
-jppyPluginEnv.Append(LINKFLAGS=distutils.sysconfig.get_config_var('LINKFORSHARED'))
+python_library_filename = commands.getoutput(./find-python-library-name.sh libpython%s.so % env['python_version'])
+jppyPluginEnv.Append(CPPDEFINES=['PYTHON_SHARED_LIB=\\%s\\' % python_library_filename])
jpilot_plugins = []
Bug#491848: undeclared (and wrong) dependency on python2.5-dev
tags 491848 patch
thanks
martin,
On Tue, 22 Jul 2008, martin f krafft wrote:
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;·
}·
I never understood yet why this seemed to be required (until
today). It's been there forever -
http://jppy.zanu.org.uk/trac/browser/trunk/jpilot_plugin/jppy.c?rev=2#L209
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!
If you run jpilot with -d, you'll see that it 'bombs out' in the
init_pygobject() here:
jp_logf(JP_LOG_DEBUG, jppy: Imported os, sys\n);
init_pygobject();
jp_logf(JP_LOG_DEBUG, jppy: Initialized pygobject\n);
I've improved the logging, now we see:
ImportError: could not import gobject (error was:
'/var/lib/python-support/python2.5/gtk-2.0/gobject/_gobject.so: undefined
symbol: _Py_ZeroStruct')
and that leads me to...
http://mail.gnome.org/archives/desktop-devel-list/2006-February/msg00192.html
which helps me understand what is actually wrong.
So it seems that we need one of these:
* jpilot to use RTLD_GLOBAL when loading the plugins
* our plugin to dlopen() python (this bug...)
* our python module to -lpython (disliked by Debian)
--- jpilot-1.6.0/plugins.c 2008-05-01 16:33:26.0 +0100
+++ jpilot-1.6.0.mine/plugins.c 2008-07-22 23:33:54.0 +0100
@@ -270,7 +270,7 @@
p-plugin_unpack_cai_from_ai = NULL;
p-plugin_pack_cai_into_ai = NULL;
- h = dlopen(path, RTLD_LAZY);
+ h = dlopen(path, RTLD_LAZY | RTLD_GLOBAL);
if (!h) {
jp_logf(JP_LOG_WARN, _(Open failed on plugin [%s]\n error
[%s]\n), path,
dlerror());
And this works :-) along with the attached patch for jppy.
but I could get it to say anything about PyExc_ImportError, even
with jpilot's -d flag.
I assume you mean 'could not'.
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).
This is what
http://jppy.zanu.org.uk/trac/browser/debian/trunk/find-python-library-name.sh?rev=322
used to do.
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().
This one looks like a build error, as the @@python_module_prefix@@
wasn't expanded.
Summary is that we need jpilot to change how they load plugins.
NickIndex: ChangeLog
===
--- ChangeLog (revision 328)
+++ ChangeLog (working copy)
@@ -1,3 +1,10 @@
+2008-07-22 Nicholas Piper [EMAIL PROTECTED]
+
+ * jpilot_plugins/jppy.c (plugin_startup): Avoid dlopen() of python
+ ourselves, and switch away from the old API for initialising
+ gobject so we can get an error condition from it properly. This
+ depends on a jpilot patch to cause it to dlopen() plugins with
+
2008-06-28 Nicholas Piper [EMAIL PROTECTED]
* SConstruct: Add python_bin_module_prefix option to SCons, to
Index: jpilot_plugins/jppy.c
===
--- jpilot_plugins/jppy.c (revision 328)
+++ jpilot_plugins/jppy.c (working copy)
@@ -207,18 +207,6 @@
jp_init();
jp_logf(JP_LOG_INFO, jppy: Starting...\n);
- // 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
Bug#485312: Jppy: Bug#485312: Useless dependency on python-gnome2-extras
Josselin, On Sun, 08 Jun 2008, Josselin Mouette wrote: currently, this package has a dependency on python-gnome2-extras. However, it does not seem to use any of the modules in it. The dependency should probably be dropped. It uses gtkspell, which is part of python-gnome2-extras unless that changed and I don't see it? http://packages.debian.org/search?searchon=contentskeywords=gtkspell.somode=exactfilenamesuite=testingarch=any http://jppy.zanu.org.uk/trac/browser/jppy/trunk/jppy/gui/contacts.py#L404 Regards, Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445379: python-jppy: module is linked to libpython
tags 445379 - patch thanks I believe http://jppy.zanu.org.uk/trac/changeset/313 helps resolve this. Note that it changes the build arguments, so http://jppy.zanu.org.uk/trac/changeset/314 is needed too (and/or remove any SCustomize cache file.) Please could someone test? [EMAIL PROTECTED]:~$ ldd /usr/lib/python2.5/site-packages/jppy/__jpilotmodule.so | grep python [EMAIL PROTECTED]:~$ Removing patch tag, as that patch was included as http://jppy.zanu.org.uk/trac/changeset/301 previously, and will go into 0.0.44-1. Josselin Mouette wrote: Furthermore, despite being able to build several versions, the package uses XS-Python-Version: current for no reason. Please switch to XS-Python-Version: all instead or specify a range of supported versions. At the moment, I'm not confident that building for several versions at once is working. Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479499: jppy: maintainer address rejects mail
Lucas, On Mon, 05 May 2008, Lucas Nussbaum wrote: On 01/05/08 at 10:51 +0100, [EMAIL PROTECTED] wrote: You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at [EMAIL PROTECTED] Please at least moderate those mails. I've changed to moderate non-member posts. Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422120: InternetRadio browser doesn't work anymore in quodlibet
I found adding libgnomevfs2-extra helped make the Internet Radio browser work again for me, at least! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
