severity 347366 important retitle 347366 kismet: pulls in spurious deps from Magick-config severity 347395 important retitle 347395 drip: pulls in spurious deps from Magick-config severity 347398 important retitle 347398 imview: pulls in spurious deps from Magick-config severity 347399 important retitle 347399 k3d: pulls in spurious deps from Magick++-config severity 347400 important retitle 347400 kword: pulls in spurious deps from Magick++-config severity 347401 important retitle 347401 librmagick-ruby1.8: pulls in spurious deps from Magick-config severity 347402 important retitle 347402 nip2: pulls in spurious deps from Magick-config severity 347404 important retitle 347404 rss-glx: pulls in spurious deps from Magick-config severity 347405 important retitle 347405 tclmagick: pulls in spurious deps from Magick-config severity 347407 important retitle 347407 python-libavg: pulls in spurious deps from Magick++-config severity 347408 important retitle 347408 prestimel: pulls in spurious deps from Magick++-config severity 347409 important retitle 347409 php4-imagick: pulls in spurious deps from Magick-config severity 347410 important retitle 347410 labplot: pulls in spurious deps from Magick++-config severity 347411 important retitle 347411 kxstitch: pulls in spurious deps from Magick++-config severity 347413 important retitle 347413 drawtiming: pulls in spurious deps from Magick++-config thanks Laurent, it would really be much more efficient if you would just ask the release team for rebuilds instead of filing separate RC bugs against each package needing a rebuild... In any case, these bugs are still relevant, since none of the packages in question had a build-dependency on libdps-dev -- which means either they were missing build-dependencies (unlikely, but the autobuilders will soon tell us if this is true), or they picked up spurious dependencies via imagemagick. The latter case makes these fifteen lovely bugs an example of the problem discussed in <http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html>; and while this *particular* spurious dependency will go away with a simple rebuild of the application (already queued on the autobuilders for each of these packages BTW), the underlying problem is that these packages don't have very good library handling and are certainly picking up dependencies on *other* libraries they don't use -- causing unnecessary archive churn, dependency fragility, more work for the release team/autobuilders, etc. So maintainers, please take the advice given in that mail and fix your packages to a) not use the output of Magick-config --libs when linking, and b) use the Debian version of libtool (if applicable). (One alternative to using Magick-config --libs seems to be to use pkg-config -- not because ImageMagick gets its pkg-config support right, but because it happens to get it right in a way that benefits us. ;) Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature