Comment 6 for bug 23786

Message-ID: <email address hidden>
Date: Tue, 11 Oct 2005 23:50:44 -0700
From: Thomas Bushnell BSG <email address hidden>
To: Ron <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#333479: gdk-imlib1: gdk-imblib1 should not explicitly conflict with libpng2

Ron <email address hidden> writes:

> Package: gdk-imlib1
> Version: 1.9.14-22
> Severity: critical
> Justification: breaks unrelated software
>
> Unless there is something big I am missing, gdk-imlib should
> certainly not take it upon itself to force the removal of
> libpng2 and all its dependencies...

There is something big you are missing.

libpng2 is being removed from Debian. libpng12-0 is a suitable
replacement, source and binary compatible.

Old versions of gdk-imlib1 were linked against libpng2 (or libpng10-0,
which amount to the same thing). The new version of gdk-imlib1 is a
masquerade; it's really gdk-imlib11. Packages expecting gdk-imlib1
will work fine getting gdk-imlib11 instead, except for those that
independently link against libpng10-0 (or libpng2). Those will
encounter disasters, because both png's cannot be loaded into one
program simultaneously without problems.

So it was either recompile everything that uses gdk-imlib1, or
recompile everything that uses libpng2/libpng10-0. But the latter is
*already necessary*, because libpng2 is being removed from Debian.

Unstable is... unstable!

Packages that use libpng2 or libpng10-0 should be recompiled.

Thomas