"Christopher L. Everett" <[EMAIL PROTECTED]> writes:
> Maurits van Rees wrote:
>
>>
>>
>>So if I would remove libmysqlclient12 then these packages would be
>>removed as well. Not all packages that you mention are in this list.
>>But there are packages that also depend on packages in this list, s
Maurits van Rees wrote:
So if I would remove libmysqlclient12 then these packages would be
removed as well. Not all packages that you mention are in this list.
But there are packages that also depend on packages in this list, so
they would be removed too. So let's look one step further:
$ a
On Mon, Oct 03, 2005 at 04:13:01PM -0500, Christopher L. Everett wrote:
> [EMAIL PROTECTED]:# apt-get remove libmysqlclient12
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following packages will be REMOVED:
> libdbd-mysql-perl libmysqlclient12 mysql-client-4.1 mysql-ser
lict. Rather the problem happens
when both libmysqlclient12 and libmysqlclient14 are being loaded in the
same executable space.
You'd need to rebuild the conflicting stuff using libmysqlclient12 to
use libmysqlclient14 to really fix the problem.
--
Captain Logic is not steering this tugboat.
--
To
For various reasons (I believe a version conflict is causing selects
to return no rows when it clearly has data to return), I want just
libmysqlclient14 on my server, but Debian own't let me uninstall
libmysqlclient12 without removing mysql wholesale:
[EMAIL PROTECTED]:# apt-get remove libmysqlcl
5 matches
Mail list logo