Re: [dev-context] [tex-live] Debian TeX -- new packages
We ask people using Debian to try these packages out, they survived all my tests and quite a lot of documents I tried out, but YMMV.
[What I describe below is not a Debian problem, but the proposed change would make the packages easier for Ubuntu users to use. I added dev-context to the CC: list since the pkg deps affect Ubuntu users -- e.g. me -- who use your excellent ConTeXt packages.] I'm using Ubuntu 6.10 (edgy) with all your tug.org stanzas. An "apt-get install texlive-base-bin" or "apt-get install context" fails when going from the TL2005 packages to the 2007 ones. The blocking package is texlive-base-bin: # apt-get install texlive-base-bin texlive-base-bin: Depends: libpng12-0 (>= 1.2.13-4) but 1.2.8rel-5.1ubuntu0.1 is to be installed Depends: libpoppler0c2 (>= 0.4.2) but it is not installable E: Broken packages I'll upgrade to the Ubuntu 7.04 beta, which will solve the libpng12-0 problem because Ubuntu 7.04 uses libpng 1.2.15. But libpoppler0c2 would still be missing. Here are the libpoppler pkgs in versions of Ubuntu: 5.04 (hoary) | libpoppler0-0.1.2 5.10 (breezy) | libpoppler0c2-0.4.2 6.04 (dapper) | libpoppler1-0.5.1 6.10 (edgy) | libpoppler1-0.5.4 7.04 (feisty) | libpoppler1-0.5.4 So, could you add libpoppler1 as an alternative libpoppler dependency? That should fix the installation. libpoppler1 is also in Debian (in experimental) so it should be a useful Debian change eventually. Then I can update to texlive 2007 and to the latest ConTeXt via apt-get. If that works, I'll update the ConTeXt wiki's installation instructions to say that Ubuntu users will have to upgrade to 7.04 to use your latest packages. Although, if it's possible to depend on an older libpng (on libpng12-0-1.2.8), then more Ubuntu users could upgrade. -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien)
Sanjoy Mahajan
I'll upgrade to the Ubuntu 7.04 beta, which will solve the libpng12-0 problem because Ubuntu 7.04 uses libpng 1.2.15. But libpoppler0c2 would still be missing. Here are the libpoppler pkgs in versions of Ubuntu:
5.04 (hoary) | libpoppler0-0.1.2 5.10 (breezy) | libpoppler0c2-0.4.2 6.04 (dapper) | libpoppler1-0.5.1 6.10 (edgy) | libpoppler1-0.5.4 7.04 (feisty) | libpoppler1-0.5.4
So, could you add libpoppler1 as an alternative libpoppler dependency? That should fix the installation. libpoppler1 is also in Debian (in experimental) so it should be a useful Debian change eventually.
No, we can't - these dependencies are autogenerated, and there's a reason why libpoppler1 is not allowed. Current TeXLive packages won't even compile with libpoppler1, let alone run, and after changing the patch to use libpoppler1, it won't compile with libpoppler0(c2). Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Current TeXLive packages won't even compile with libpoppler1, let alone run, and after changing the patch to use libpoppler1, it won't compile with libpoppler0(c2).
Right, as I found by trying to build it from source. Do you have a handy libpoppler1 patch? -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien)
[Using Ubuntu 6.10/i386] I couldn't apply (without rejected hunks) the Ubuntu poppler patch at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356079 to the Debian texlive-2007-1 source. So I just removed debian/patches/30_libpoppler from the patch series, returning to using the xpdf sources that ship with pdftex. Then the texlive-2007 src pkg compiled into the many .deb's and these binary pkgs installed fine. They use libpng-1.2.8 and libc6-2.4. I then could upgrade to your latest context pkg (2007.03.19) and test it. As its stress test, it processed my textbook fine. The only glitches I've noticed so far: * installing the pkgs removed dvipdfmx but I haven't figured out the reason. It may be Ubuntu-specific. * dvipos isn't included in any binary packages, although it gets built when creating them: $ pwd /var/tmp/tlrebuild/texlive-bin-2007 $ find -name dvipos ./build/source/texk/dvipos ./build/source/inst/bin/i686-pc-linux-gnu/dvipos ./build/source/Work/texk/dvipos ./build/source/Work/texk/dvipos/dvipos ./bin/i386-linux/dvipos I couldn't figure out where the package-splitting information lives, in order that dpkg-buildpackage knows dvipos belongs to a particular binary package. Maybe because there's no tpm file for it, and the tpm's are turned into magic Debian files, so dvipos gets left out? Multiple binary pkgs from one source pkg is one the the deeper mysteries of Debian packaging, well understood by maintainers of complex packages (like texlive or tetex) but not documented elsewhere. But I'm happy to learn how that works! -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien)
participants (2)
-
Frank Küster -
Sanjoy Mahajan