Yeah, I've packaged something new for that. Eventually my sponsor will upload it (I've already asked him to, he asked me about the test suite, I added it back in, it barfed without it installed, so I dumped "export LD_LIBRARY_PATH" into the Makefile, etc...) Hopefully it should be up in the next 48 hours. The new package is already on the VCS; it's tagged as debian/2.0-2, and I've tested it as building.
BTW, as far as I was aware, 0.0.0 was normal, since it is the first SO release of the package (JBIG-KIT, as written by the author, has no SO in the Makefile - I fiddled with the Makefile until it worked. That has been submitted upstream, but upstream would seem to be a Cambridge fellow with other far more interesting things to amuse him, or perhaps the students are just getting to him :) In any case, upstream is unresponsive. ). Is that not the normal practice for versioning? Let me know if there's something else - I'd be happy to add you onto the VCS. The tree is at github.com/mvanderkolff/jbigkit-packaging (I have not got access to alioth collab-maint - that's why it's not hosted there). Warmest regards, Michael On Sun, Apr 8, 2012 at 11:53 PM, Jay Berkenbilt <q...@debian.org> wrote: > Michael van der Kolff <mvanderko...@gmail.com> wrote: > >>> If so, I will definitely support it in libtiff. There's a >>> security update going in now. After that transitions, I'll upload with >>> JBIG support. >> >> When do you expect that to be? My use case for this is actually fax, >> which means that I need one final piece from HylaFAX before I can go >> ahead and use it. HylaFAX only builds with JBIG support if both >> libtiff with JBIG exists, and the JBIG headers also exist. > > If all goes well, it should only be a couple of days. > > Actually, I just tried building tiff with libjbig-dev installed, and I > get the following: > > ... > checking for jbg_dec_init in -ljbig... no > checking jbig.h usability... yes > checking jbig.h presence... yes > checking for jbig.h... yes > ... > Support for external codecs: > ... > ISO JBIG support: no > ... > > If I look at the libraries: > > % cd /usr/lib/x86_64-linux-gnu > % ls -l *jbig* > lrwxrwxrwx 1 root root 14 Apr 6 08:08 libjbig.so -> libjbig.so.0.0 > lrwxrwxrwx 1 root root 16 Apr 6 08:08 libjbig.so.0 -> libjbig.so.0.0.0 > -rw-r--r-- 1 root root 58912 Apr 6 08:08 libjbig.so.0.0.0 > > it seems that libjbig.so is wrong. The .0.0.0 is suspicious anyway. Is > there no proper shared library versioning here? > > Updating the link of libjbig.so to point to libjbig.so.0.0.0 corrects > the problem. I'll delay any uploads until I hear back that this problem > is fixed. If you need a sponsor for your upload and your regular > sponsor is slow to respond or unavailable, let me know, and I can > sponsor. > > -- > Jay Berkenbilt <q...@debian.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
