On Tue, May 22, 2001 at 13:57:48 -0500, Dave Sherohman wrote:
- and, if I did, would dpkg just put it back when the next revision of
gnumeric gets installed?
Indeed.
Any way to avoid that?
No; it's simply a part of the gnumeric package. Better file a bug report so
the next revision won't
On Mon, May 21, 2001 at 17:13:33 -0500, Dave Sherohman wrote:
unable to open module file: /usr/lib/gnumeric/plugins/0.47/libgnum_python.so:
undefined symbol: _Py_NoneStruct
Hmm... 0.47 is quite old; I'd recommend against using it for anything
serious.
This is on a not-quite-pure potato
On Tue, May 22, 2001 at 05:57:40PM +0200, J.H.M. Dassen (Ray) wrote:
On Mon, May 21, 2001 at 17:13:33 -0500, Dave Sherohman wrote:
unable to open module file:
/usr/lib/gnumeric/plugins/0.47/libgnum_python.so:
undefined symbol: _Py_NoneStruct
Hmm... 0.47 is quite old; I'd recommend
After installing gnumeric (with it's obscene list of dependencies, as
discussed here earlier), I'm getting the error
unable to open module file: /usr/lib/gnumeric/plugins/0.47/libgnum_python.so:
undefined symbol: _Py_NoneStruct
on startup. Installing python-base has not had any noticable
4 matches
Mail list logo
