yum problems

Jesse Keating jkeating at j2solutions.net
Thu Jul 28 05:27:40 UTC 2005


On Wed, 2005-07-27 at 23:23 -0400, Gene Heskett wrote:
> According to rpm, it wasn't, so I did an install with the --justdb 
> option, which fixed that right up.  Note that I don't frankly care if 
> the original kernel is available for booting or not, I've currently 
> about 25 choices setup in grub.conf.  I have been known to build 3 
> kernels a day just for fun & testing.

Which is why I say your rpm db is borked.  You cannot be running a clean
rpm db if you have no kernel entry.  The fact that you had to --justdb
it tells me that something has borked your rpm db, and in just about
every place I've ran into a borked rpm db for unknown reasons, it wasn't
worth the lengthy effort to try and figure out what went wrong and fix
it.  It was best to pave it, and restore critical data from backup.

[...]

> 
> Never say never my friend.  I've just come off a weeks worth of trying 
> to install FC4 on another machine & gave up after about 10 cycles.  
> Those cd's went out with the trash this morning.  3 of the many 
> installs worked long enough to type yum update, which promptly 
> destroyed them to the point of being unbootable. 

Whats so special about you that is different from the hundreds of
thousands of other users that are able to get FC4 installed w/out a
hitch?  It isn't terribly difficult, nor inherrently broken, unless you
have some wild system that just doesn't like their default kernels, or
you have hardware issues that are leading to corruption.

>  So if I do 
> something here thats not recoverable via amanda, and have to 
> re-install, the re-install with start with disk 1 of debian-3.1.  Or 
> maybe even gentoo, but at 70, I may not have enough time to get it to 
> run as clean as I have this one running now for day to day use.

More power to you.  Some Linux distributions are more... forgiving...
when you wander off the beaten path.  Some are less.  Fedora is
generally in the middle until all of a sudden the rpm DB is borked.  The
problem you see installing on one system is not indicative of a bad OS,
just a system that perhaps doesn't like the install for one reason or
another.

Do whatever you wish with your systems, however I can't take any credit
in any packaging bug you may find, as I know you don't have a pristine
or even semi-clean system.  Don't expect our stuff to work out of the
box on your system either.

-- 
Jesse Keating RHCE      (geek.j2solutions.net)
Fedora Legacy Team      (www.fedoralegacy.org)
GPG Public Key          (geek.j2solutions.net/jkeating.j2solutions.pub)
 
Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=jkeating




More information about the fedora-legacy-list mailing list