So it really isn't an Xastir bug, it's a Debian *Magick packaging bug..the
maintainers of those two ecosystems need to update their packages to remove the
Jasper dependency.
And since Debian has been absorbed by the Borg Collective that is systemd,
another option would be to wait until
This is a good table of the impact of it's removal:
https://release.debian.org/transitions/html/jasper-rm.html
--David
On 03/14/2016 03:30 PM, David Ranch wrote:
The Xastir source code has dependencies that link to it.. specifically
GraphicsMagick / ImageMagick
$ ldd /usr/bin/xastir
The Xastir source code has dependencies that link to it.. specifically
GraphicsMagick / ImageMagick
$ ldd /usr/bin/xastir | grep jasper
libjasper.so.1 => /usr/lib64/libjasper.so.1 (0x003fbd80
$ rpm -qRi GraphicsMagick | grep jasper
libjasper.so.1()(64bit)
--David
KI6ZHD
Hope the debian package maintainer is listening. the xastir developers
don't support distro packages, just the source code.
-Jason
kg4wsv
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir
