libkpathsea3 incompatibility problem
There's a major problem with the new tetex-* packages, and in
particular with the new libkpathsea3 package. Because upstream broke
binary compatibility with previous versions (and as they have stated,
they are not yet supporting the building of libkpathsea as a shared
library), there are now several packages which are broken because of
this (all of which have been Bcc'd on this email):
$ grep-available -F Depends libkpathsea3 -s Package,Version,Depends
Package: lilypond
Version: 1.6.6-2
Depends: libc6 (>= 2.3.1-1), libguile9 (>= 1:1.4-24), libkpathsea3 (>= 1.0.7+20011202-8), libstdc++2.10-glibc2.2 (>= 1:2.95.4-15), tetex-bin (>= 1.0.5-1), tetex-extra (>= 1.0-1), python, guile
Package: spawx11
Version: 1.2.4-3
Depends: dvilib2, libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20011202-8), libttf2, t1lib1, vflib3, xlibs (>> 4.1.0)
Package: vflib3
Version: 3.6.13-1
Depends: libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20011202-8), libttf2, t1lib1, defoma
Package: ultrapoint
Version: 0.4-9
Depends: libc6 (>= 2.2.4-4), libggi2 (>= 1:2.0.1-2), libgii0 (>= 1:0.8.1-1), libglib1.2 (>= 1.2.0), libkpathsea3 (>= 1.0.7+20011202-2), libttf2, libunicode0 (>= 0.4.0-2), libxml1 (>= 1:1.8.14-3), t1lib1, vflib3, zlib1g (>= 1:1.1.3), libggi-target
Package: libkpathsea-perl
Version: 3.3.1.10-1
Depends: libc6 (>= 2.2.4-4), libkpathsea3 (>= 1.0.7+20011202-7), perlapi-5.8.0, perl (>= 5.8.0-3), tetex-bin (>> 1.0)
Package: dvi2ps
Version: 3.2j-1
Depends: libc6 (>= 2.3.1-1), libkpathsea3 (>= 2.0-1), libttf2, vflib2 (>= 2.25.1-1), tetex-base (>= 1.0.2), debconf
Package: dvilx
Version: 1:01.03-5.1
Depends: libc6 (>= 2.2.4-4), libkpathsea3 (>= 1.0.7+20011202-3), xlibs (>> 4.1.0), tetex-bin
Package: ctie
Version: 1.0-1
Depends: libc6 (>= 2.2.4-4), libkpathsea3 (>= 1.0.7+20011202-3)
Package: jtex-bin
Version: 1.8-5.1
Depends: jtex-base, tetex-bin, libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20021025-3)
Package: spawg
Version: 1.2.4-3
Depends: dvilib2, libc6 (>= 2.3.1-1), libglib1.2 (>= 1.2.0), libgtk1.2 (>= 1.2.10-4), libkpathsea3 (>= 1.0.7+20011202-8), libttf2, t1lib1, vflib3, xlibs (>> 4.1.0)
Package: dvipdfm
Version: 0.13.2c-9
Depends: tetex-base, libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20021025-5), libpaper1, libpng12-0, zlib1g (>= 1:1.1.4)
Package: ptex-bin
Version: 3.0.5+0.04-2
Depends: ptex-base (>= 1:2.0-3), tetex-bin (>= 1.0.7+20011202-5.1), tetex-extra, libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20021025-6)
Package: dvipdfm-cjk
Version: 1:20020916cvs-1
Depends: tetex-bin, tetex-base, dvipdfm-cjk-cmap, libc6 (>= 2.2.5-13), libkpathsea3 (>= 1.0.7+20011202-8), libpng3, libssl0.9.6, zlib1g (>= 1:1.1.4)
Package: libkpathsea-dev
Version: 2.0-1
Depends: libkpathsea3 (= 2.0-1)
Package: tetex-bin
Version: 2.0-1
Depends: libc6 (>= 2.3.1-1), libgcc1 (>= 1:3.2.2-1), libkpathsea3 (>= 1.0.7+20021025-1), libpng12-0, libstdc++5 (>= 1:3.2.2-1), libwww0 (>= 5.4.0) | libwww-ssl0 (>= 5.4.0), libxaw7 (>> 4.1.0), t1lib1, xlibs (>> 4.1.0), zlib1g (>= 1:1.1.4), perl, tetex-base (>= 2.0), ed, debianutils (>= 1.13.1), debconf
Package: dvi2dvi
Version: 2.0alpha-2
Depends: libc6 (>= 2.2.4-4), libkpathsea3 (>= 1.0.7+20011202-3.1)
Package: vflib3-bin
Version: 3.6.13-1
Depends: libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20011202-8), libttf2, t1lib1, vflib3, xlibs (>> 4.1.0)
Package: xgdvi
Version: 1.2.4-3
Depends: dvilib2, libc6 (>= 2.3.1-1), libglib1.2 (>= 1.2.0), libgtk1.2 (>= 1.2.10-4), libkpathsea3 (>= 1.0.7+20011202-8), libttf2, t1lib1, vflib3, xlibs (>> 4.1.0)
Package: tex-guy
Version: 1.2.4-3
Depends: dvilib2, libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20011202-8), libttf2, t1lib1, vflib3
Package: tex4ht
Version: 20021008-1
Depends: tetex-bin, libc6 (>= 2.2.4-4), libkpathsea3 (>= 1.0.7+20011202-7)
Package: jbibtex-bin
Version: 3.0.5+0.04-2
Depends: jbibtex-base, libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20021025-6)
Package: jmpost
Version: 3.0.5+0.04-2
Depends: libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20021025-6), tetex-bin (>= 1.0.7+20011202-5.1)
Package: dvipdfmx
Version: 20021230-7
Depends: tetex-bin, tetex-base, dvipdfm, debconf, libc6 (>= 2.3.1-1), libkpathsea3 (>= 2.0-1), libpaper1, libpng12-0, libssl0.9.7, zlib1g (>= 1:1.1.4)
Package: multex-bin
Version: 0.7-5.1
Depends: multex-base, tetex-bin, libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20021025-3)
Package: cweb
Version: 3.64-3
Depends: libc6 (>= 2.2.4-4), libkpathsea3 (>= 1.0.7+20011202-5.1)
Package: dvisvga
Version: 1:01.03-5.1
Depends: libc6 (>= 2.2.4-4), libkpathsea3 (>= 1.0.7+20011202-3), svgalibg1, tetex-bin
Package: dvipsk-ja
Version: 5.90a+jp1.5g-3
Depends: libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20021025-6), tetex-bin (>= 1.0.7+20011202-5.1), tetex-base
Package: dvifb
Version: 1:01.03-5.1
Depends: libc6 (>= 2.2.4-4), libkpathsea3 (>= 1.0.7+20011202-3), gpm, tetex-bin
Package: dvilib2
Version: 1.2.4-3
Depends: libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20011202-8), libttf2, t1lib1, vflib3, tetex-extra
Package: tkdvi
Version: 0.3.1-1.1
Depends: libc6 (>= 2.2.3-1), libkpathsea3 (>= 1.0.7+20001218-3), tk8.3 | wish
Package: catdvi
Version: 0.14-2
Depends: libc6 (>= 2.3.1-1), libkpathsea3 (>= 1.0.7+20021025-8)
Package: freetype1-tools
Version: 1.4pre.20011029-1
Depends: libc6 (>= 2.2.4-4), libkpathsea3 (>= 1.0.7+20001218-6), libttf2, xlibs (>> 4.1.0)
Package: xdvik-ja
Version: 22.15-j1.04-4
Depends: tetex-base, tetex-bin, libc6 (>= 2.2.3-7), libkpathsea3 (>= 1.0.7+20001218-5), libxaw7 (>> 4.1.0), vflib2 (>= 2.25.1-1), xlibs (>> 4.1.0)
So now what do we do? Presumably, all of these packages will break
once the new libkpathsea3 is installed, so here are the obvious
options:
(1) File RC bugs against all of these packages, requiring them to
recompile against the newer libkpathsea3, and have versioned
Conflicts: with the old versions of these dozen or so packages.
(2) Change the so version number of the libkpathsea library to 4, even
though this matches nothing in the upstream, and provide an old
libkpathsea3 package in oldlibs for compatibility (this would be a
source package entirely separate from tetex-bin derived from the
old teTeX sources).
(3) Like (2), but change the so version number to 0 to indicate
unstable interface.
I prefer (2) or (3). Other comments?
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, website: http://www.polya.uklinux.net/
Debian GNU/Linux Developer, see: http://people.debian.org/~jdg/
Visit http://www.thehungersite.com/ to help feed the hungry
Reply to: