From: "Francesco R." <vivo@gentoo.org>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] mysql-4.1
Date: Fri, 21 Oct 2005 12:07:25 +0200 [thread overview]
Message-ID: <200510211207.26060.vivo@gentoo.org> (raw)
In-Reply-To: <43588B41.6040009@munat.com>
Alle 08:31, venerdì 21 ottobre 2005, Ben Munat ha scritto:
> Francesco, any thoughts on this? I seem to remember my last disaster
> with mysql/vpopmail was due to libmysqlclient.so.12 disappearing.
> This makes me very nervous. Shouldn't revdep-rebuild take care of
> this? Anyone else have vopopmail installed but have successfully done
> this upgrade?
>
revdep-rebuild *should*, having problem me too with it not rebuilding
*all* what I need.
A rather awful workaround is to rebuild every package that has the mysql
useflag. to generate a list try this oneliner:
emerge -epv --columns mysql \
| grep mysql | grep -v 'dev-db/mysql '\
| cut -c 17- \
| awk 'emerge --oneshot {print $1}' \
| awk '{print "emerge --oneshot --nodeps", $1}'
then adjust the list for your needs.
> Dave Strydom wrote:
> > Well i have only had failure, due to programs not being able to
> > find the libmysqlclient.so.12
> > even after updating with ldconfig or env-update
> >
> > my MailScanner and exim broke because of this (well i only got that
> > far into it because i rolled back to the old version)
> >
> > So, do any of you folks reporting success or failure happen to
> > be using vpopmail? The last
> > big MySQL debacle took down vpopmail and therefore all the
> > mail... that sucked.
[snip]
Sorry for the problems, I can setup a test environment on a public ip
address (x86 running stable), following your instruction (I don't use
vpopmail).
Then we can test everything there.
Best regards,
Francesco R.
--
gentoo-server@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-21 10:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 4:42 [gentoo-server] mysql-4.1 Ben Munat
2005-10-20 4:49 ` Bertrand CHERRIER
2005-10-20 5:34 ` W.Kenworthy
2005-10-20 7:03 ` Dave Strydom
2005-10-20 6:51 ` W.Kenworthy
2005-10-20 13:16 ` Francesco R.
2005-10-20 13:42 ` Wolf Giesen
2005-10-20 13:55 ` Dark
2005-10-20 15:41 ` [gentoo-server] mysql-4.1, revdep-rebuild Wolf Giesen
2005-10-21 12:00 ` [gentoo-server] mysql-4.1 William Kenworthy
2005-10-21 13:15 ` Francesco R.
2005-10-20 13:03 ` Francesco R.
2005-10-21 3:18 ` Ben Munat
2005-10-21 4:55 ` Dave Strydom
2005-10-21 6:31 ` Ben Munat
2005-10-21 10:07 ` Francesco R. [this message]
2005-10-21 13:17 ` Francesco R.
2005-10-21 13:22 ` Lance Albertson
2005-10-22 12:11 ` Dave Strydom
2005-10-22 12:16 ` Dave Strydom
2005-10-22 13:26 ` Barry Marler
2005-10-22 13:31 ` Dave Strydom
2005-10-22 13:50 ` Lance Albertson
2005-10-22 13:55 ` Dave Strydom
2005-10-22 14:01 ` Craig Webster
2005-10-22 14:32 ` Luca Longinotti
2005-10-22 14:51 ` Craig Webster
2005-10-22 19:43 ` Francesco R.
2005-10-22 19:46 ` Craig Webster
2005-10-22 20:57 ` Francesco R.
2005-10-22 22:13 ` Luca Longinotti
2005-10-22 22:53 ` Petteri Räty
2005-10-22 17:00 ` Barry Marler
2005-10-23 20:37 ` [gentoo-server] routing bittorent radu herinean
2005-10-24 8:19 ` Wolf Giesen
2005-10-24 14:13 ` Marton Gabor
2005-10-22 19:46 ` [gentoo-server] mysql-4.1 Francesco R.
-- strict thread matches above, loose matches on Subject: below --
2005-10-20 13:40 Covington, Chris
2005-10-20 13:50 ` Dark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510211207.26060.vivo@gentoo.org \
--to=vivo@gentoo.org \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox