That little libpng affair

["Marcelo E. Magallon" <mmagallo@debian.org>]

Hi people,

 [ please Cc: me ]

 so woody is out and there's a mess to clean up.

 We have:

$ grep-available -s Package -F Depends libpng-dev | wc -l
      5
$ grep-available -s Package -F Depends libpng2-dev | wc -l
     17

 In case it isn't self evident, you can't have libpng-dev and
 libpng2-dev installed at the same time.  libpng-dev is the *newer one*
 (and the one that should be used according to libpng-dev's description)

 The first group is:

libcamlimages-ocaml-dev
libqt3-dev
libqt3-emb-dev
libquicktime4linux-dev
libsdl-image1.2-dev

 The second one:

clanlib-dev
gdk-imlib-dev
imlib-dev
kdelibs-dev
libfnlib-dev
libgd-dev
libgd-noxpm-dev
libglpng-dev
libgtk2.0-dev
libguppi-dev
libimlib2-dev
libmagick5-dev
libqt-dev
libqt-emb-dev
libwmf-dev
libwraster2-dev
libwxgtk2.2-dev

 That looks well contained.  The libsdl-image1.2-dev package is
 infortunate because:

$ grep-available -s Package,Depends -F Depends libpng2 | grep-dctrl -n -s Package -F Depends libsdl-image1.2        
libparagui1.0
libsdl-ocaml
burgerspace
libsdl-perl
criticalmass

 For example:

$ criticalmass
[...]
libpng warning: Application was compiled with png.h from libpng-1.2.1
libpng warning: Application  is running with png.c from libpng-1.0.12
libpng error: Incompatible libpng version in application and library
Segmentation fault (core dumped)

 In fact, looking at the Build-Depends the situation is: 

$ grep-dctrl -n -s Package -F Build-Depends libpng2-dev Sources | wc -l
    153
$ grep-dctrl -n -s Package -F Build-Depends libpng-dev Sources | wc -l
     37

 Let's take a closer look:

$ for png3 in `grep-available -s Package -F Depends libpng-dev` ; do grep-dctrl -s Package,Build-Depends -F Build-Depends libpng2-dev Sources | grep-dctrl -s Package -F Build-Depends $png3 ; done
Package: black-box
Package: bumprace
Package: sdlperl
 
 (sorry about the piss-poor performance of that, I didn't want to use a
 temp)

 The other way arround:

$ for png2 in `grep-available -s Package -F Depends libpng2-dev` ; do grep-dctrl -s Package,Build-Depends -F Build-Depends libpng-dev Sources | grep-dctrl -s Package -F Build-Depends $png2 ; done
Package: licq
Package: fsviewer
Package: kdeadmin
Package: licq

 Even more annyoing is the fact that you can't have a GTK+ 2 and Qt 3
 development environment installed at the same time (that means for
 example you won't be able to have kdevelop and anjuta installed at the
 same time).  Second generation dependencies:

$ for p in `grep-available -n -s Package -F Depends libpng2-dev` ; do grep-available -s Package -F Depends $p ; done | sort -u | wc -l
     47
$ for p in `grep-available -n -s Package -F Depends libpng-dev` ; do grep-available -s Package -F Depends $p ; done | sort -u | wc -l
      3

 The first group is a bunch of GNOME, GTK+, GNOME 2 and GTK+ 2 stuff.
 The second group is, uhm, boring ;-)  It will expand once KDE3 makes
 its way into sid (I guess it hasn't already since I would expect
 something in there to depend on libqt3-dev).

 Look at 147420 for even more fun regarding this issue.  (In short:
 apparently someone managed to convince the release manager that having
 libgtk2.0-dev depending on libpng2-dev in woody was a good idea).

 Looking at Suggests and Recomends is left as an excercise for the reader.

 Thanks,

-- 
Marcelo             | This signature was automatically generated with
mmagallo@debian.org | Signify v1.07.  For this and other cool products,
                    | check out http://www.debian.org/


-- 
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org