Bug#112211:

[Thomas Hood <jdthood@yahoo.co.uk>]

Hi, and thanks for the additional info.

dpkg is actually behaving correctly here.

In order to install xlibmesag3 dpkg has to remove
mesag3 first.  However, removing mesag3 would break
the dependency on libgl1.  So, dpkg cannot proceed.

Changing from one provider of libgl1 to another is
different from upgrading a provider of libgl1.
In the latter case, the package remains in the
installed state throughout the procedure.

Do we want to modify dpkg so that it will go ahead
anyway in circumstances like these?  I'm not sure.

--
Thomas


On Wed, 2002-10-16 at 04:26, Michael Fair wrote:
> This happened a long time ago so I do not recall
> the specifics but it was much more than just
> a spruious warning.  I eventually had to force
> the install to happen.
> 
> There was a package installed that required libgl1.
> This was originally provided by mesag3.
> xlibmesag3 also provided libgl1.
> 
> If I tried to install xlibmesag3 it would error
> out complaining that doing so would break the
> package that relied on libgl1.
> 
> So the error was something about the provides line
> of packages to be installed not being recognized
> when checking if removing a package would break
> dependencies.