Robin Laing wrote:
Temlakos wrote:
Nat Gross wrote:
Finally yum worked today. I wish it did not!
It dl'd 36 packages, including mysql 3.x although this server is
actively running mysql 4.1x.
Everything with yum seemed perfect, when I happened to glance at the
screen as yum listed "deleted mysql" on the console. I said to
myself, "nah, can't be". BUT, it did! NO TRACE of mysql is on the
system! In the yum cache the 3.x rpm sits, the client programs are
there, but NO SERVER. No related files or service. (#'service mysql
start' reports "mysql: unrecognized service".
I do have my data, thank god.
Running FC3 latest kernel (yum updated it today) on a 1.6ghz Dell
4500s with 1 gig ram.
1. WHY did yum do this?! 1B. Especially that mysql service was ACTIVE
at the time! What about my users!???
2. HOW do I prevent this from happening again?
3. Should I DUMP yum?
Your input is appreciated.
-nat
I use smart, myself. And in smart, I can "lock" a package and make
sure that it doesn't go anyplace. I can even see in advance what
"smart" is going to upgrade or downgrade or remove /before/ it happens.
No, don't /dump/ yum. But neither should you use it as your primary
package updater. I keep it around for certain situations such as
"repository reported unexpected size" that I've been seeing lately
from some of the jpp repos.
Temlakos
I use Yumex and read through the list of updates. Yumex is in extras.
Yumex is, of course, a GUI front-end for yum. I use it, too, when smart
gives me any kind of trouble. I would never try to manage updates with
only one package manager.
Temlakos
