On Tue, Sep 13, 2005 at 07:38:56AM -0600, Barak Pearlmutter wrote: > This isn't djview's fault, is it?
Nope, you can blame this one on me. The dependency was forced in order to get the GNOME 2.10 package into testing so that we can get unstable unwedged. djview's uninstallability is an unfortunate side-effect of this; FWIW, getting libqt3 into testing is the next order of business, but is likely to take a few weeks yet on account of the large number of packages that need to be recompiled. On Tue, Sep 13, 2005 at 08:29:29AM -0600, Barak Pearlmutter wrote: > Yes, it probably has to do with that. > Will look into a transitional package. But although it might solve > the multiple libdjvulibre1 vs multiple libdjvulibre15 problem, it > probably won't solve this libqt* issue. The only way to address this would be by building against libqt3c102-mt using g++-3.3 as the compiler and uploading to t-p-u. It looks like this should be safe, FWIW, since libdjvulibre15 exports only a C interface via its headers in spite of being implemented in C++. I'd be happy to approve such an upload to t-p-u if you were so inclined. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
