[Techtalk] Shared library dependencies - Debian
Lisa Kachold
lisakachold at obnosis.com
Fri Nov 9 18:28:51 UTC 2012
Terry,
On Fri, Nov 9, 2012 at 9:29 AM, Terry <tech at futurecourse.com> wrote:
> Hi Chris (and Lisa and Miriam),
>
> On 08/11/2012 13:44, Chris Wilson wrote:
>
>> Hi Terry,
>>
>
> How about downgrading back to the version of mysql supplied with the OS?
>>
>
> It's not causing any issues with respect to the services running.
> Everything runs just fine. It's the annoying cron job error messages that
> I keep getting. :) It's not a production server. It's a VPS I use for my
> own education in all things linux/debian. If I screw anything up, it just
> affects me.
>
>
> No, I'd say one line is the warning and one line is the actual library.
>> Nothing unusual there except the warning.
>>
>
> Ah, thank you. I couldn't find anything on google about it.
The link I sent from bugtracker is this issue. Did you read it?
>
>
> What exactly did you do? Install mariadb from the same repo and the
>> problem appeared?
>>
>
> On my VPS, I upgraded from MariaDB 5.3 to 5.5 using their repo. Started
> getting the errors. But I had done a little cleanup of my VPS and wondered
> if I hadn't inadvertently done something I shouldn't have. Googling wasn't
> much help although I had found the bug report Lisa mentioned but what had
> confused me was the two entries that ldd was spitting out. I thought it
> was seeing libmysqlclient18 twice, hence my wondering if I had done
> anything in my cleanup.
>
> In the meantime, I created a few pristine disk images of Debian Squeeze
> and Wheezy and installed mariadb and exim4-daemon-heavy and experienced the
> same problems. exim4 ran fine with the debian version of libmysqlclient18
> installed but when mariadb replaced it, errors occurred.
>
>
> Yes, I'd say it's a bug in the versions in the mariadb repo. Debian
>> packages are vere hard to get right (I hate them) and perhaps they got
>> them wrong, or they're not really compatible with your version of Debian.
>>
>
> I filed a bug report with mariadb and it's already being looked at. Yay!
Hopefully you cross referenced the code from Debian I sent?
>
>
>
>> I reckon you should go back to a supported combination of software. Use
>> the latest mariadb/mysql that comes with your OS and no other. Then at
>> least there's only one group to hold responsible for any problems, and
>> the Debian community are pretty good at fixing problems with Debian in
>> my experience.
>>
>> Cheers, Chris.
>>
>
> Thanks for everyone's comments. Looks like Miriam's comments were on the
> money about what happened. Hopefully, it's on the road to getting fixed in
> the next release of Mariadb.
>
> I really appreciate being able to ask questions here. I'm not very
> experienced and those mailing lists can be daunting sometimes.
>
> Again, thanks.
>
> --
> Terry
>
> ______________________________**_________________
> Techtalk mailing list
> Techtalk at linuxchix.org
> http://mailman.linuxchix.org/**mailman/listinfo/techtalk<http://mailman.linuxchix.org/mailman/listinfo/techtalk>
>
--
(503) 754-4452 Android
(623) 239-3392 Skype
(623) 688-3392 Google Voice
**
it-clowns.com
Chief Clown
More information about the Techtalk
mailing list