> Eric Sisolak wrote: > > On Mon, Nov 23, 2009 at 7:24 PM, Chris Adams <[email protected]> wrote: > >> I updated a couple of servers from mostly-up-to-date RHEL 5.3 to the > >> current RHEL 5.4+updates via "yum update", and I got a bunch of bogus > >> dependencies added in. > >> > >> On a 32 bit server, yum wanted to add amanda (backup software). �On a 64 > >> bit server, yum wanted to add KDE, GTK, Ruby, and a whole bunch more (on > >> a server without X installed). > >> > > [snip] > >> -- > >> Chris Adams <[email protected]> > >> Systems and Network Administrator - HiWAAY Internet Services > >> I don't speak for anybody but myself - that's enough trouble. > >> > > > > I had something similar happen to me several months ago. I could not > > figure out why "yum update" was bringing X as a dependency for an > > update. Like many mysterious yum issues, I was able to clear it up by > > running "yum clean all" and then running the update again. > > > I've started wondering why yum has started to offer to install 32-bit > stuff on my pure 64-bit Tikanga clone. It happened yesterday when I > wanted to install expect, but not today when I tried to reproduce it > with emacs. It's quite possible it's something I've done. It's also > quite possible it's not something I've done. > > If others report similar experiences, I can stop wondering.
I don't think this will help with the OP's problem, but it does help keep 64bit systems clean of 32bit unless you specifically as for it: in /etc/yum.conf add: multilib_policy=best I'd be curious to know if you already have it and it still did the 32bit offer. -greg _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
