Jppy: comments to the current jppy
Ludovic Rousseau
ludovic.rousseau at free.fr
Tue May 23 22:52:51 BST 2006
Le Monday 22 May 2006 à 12:45:34, Nicholas Piper a écrit:
> > Only one strange thing, but probably a bug in the packaging: The
> > pisock.py (and friends) are installed on Debian into /usr/lib/python/
> > where there are *not* found by jppy. I linked them into
> > /usr/lib/python2.3/site-packages/ and of you go.
>
> This is a change to previous packaging yes. Maybe it's a bug, please
> email Ludovic Rousseau <rousseau at debian.org> and let him know.
I found the bug and uploaded a new version in experimental.
I am not a Python user so I did not noticed it earlier.
> Is that all you mean, or are there further changes you're suggesting?
> Do you think I should Conflict with all current versions of jpilot in
> debian? I'm not sure how to do that; I don't know the version number
> they'll use when they switch to libpisock9. I will ask Ludovic
> Rousseau by CCing him on this mail.
>
> Ludovic: My package 'jppy-jpilot-plugins" will only work if jpilot is
> linked with libpisock9. Currently that means people have to recompile
> their own jpilot (not a real problem at this point I think,
> considering the technical level of jppy.) It would be nice if apt
> could warn them about this somehow?
I don't know an easy way to do that.
I will recompile jpilot using libpisock9 when pilot-link 0.12.0 is
stable. But I don't know when that will happen.
Bye,
--
Dr. Ludovic Rousseau Ludovic.Rousseau at free.fr
-- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
More information about the Jppy
mailing list