-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 05 December 2003 06:40 pm, Mike Watson wrote: > On Friday 05 December 2003 06:31 pm, William Hooper wrote: > > Mike Watson said: > > > In addition, I can't use RPM to instead the rpm directly. I get > > > a message about the file requiring an Athlon architecture and RPM > > > quits. > > > > > > How can I change the architecture? Why does RPM now refuse to > > > install. I can't use --force either. > > > > RPM is the one complaining, not up2date. > > > > You can see the values by doing: > > > > rpm --showrc | head > > > > I don't think directly editing the rpmrc file is the "correct" > > (since MaximumRPM says "don't touch"), so you might want to ask on > > the RPM-List. > > rpm --showrc | head says I have a build architecture of i386 and > compatible architecture is i586 i486 i386. > > How can I correct this? > > Mike W Since my original question was that up2date showed the wrong CPU on the kernel upgrade, is this an up2date issue or RPM? I have found that $HOSTTYPE is still shown as i386 instead of i686 like my other Athlon. Running kudzu changes nothing. Is one of the sysint scripts failing too? Mike Watson - -- Registered Linux - 256979 (http://counter.il.org for more information) NRA Life ARS: W0TMW -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/0h6X5fq6h2uDDlQRAsJRAJ41smyJ2P//dF8cQF7vQVa+79dcPgCfUh6i CG4eU29NFWaGPFNmBa7lFeM= =goz2 -----END PGP SIGNATURE----- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
