On Thu, 02 May 2002 21:12:04 -0700 Harry Putnam <[EMAIL PROTECTED]> quietly intimated:
> ABrady <[EMAIL PROTECTED]> writes: > > > What I did to fix it was I went to a mirror and downloaded a new > > up2date(that was part of the problem too, I think) and all of the > > other RPMs and manually updated them. After that everything worked > > OK. > > > > I remember (but not in detail) that a lot of others had a similar > > problem at the time. Someone figured out exactly what packages > > needed to be upgraded to fix the problem. In my usual brute > > force-manner, I just did the whole kit'n'kaboodle and got it over > > with. > > Heavy enough it turns out.. Taking a clue from you I grabbed all rpm > related packages on the list (including popt). Also included the > up2date updates as you noted. Then ran: > > rpm -UvhF --nodeps *.rpm > > After that I ran `up2date -u' to get the rest... All went smoothly > after force installing the rpm*rpm packages. > > I have a hunch that proceedure could have gotten me into a big mess > but this time I got lucky. Well, this machine is a toy. I have another that I can fall back on if I really screw something up. So I take a lot of chances that others wouldn't/shouldn't. I always try to keep an escape plan handy for this machine as well. The errors I was getting didn't make any sense, as you found out, because it pointed to things I didn't have and complained I needed to keep things that weren't there. So I took that to mean something was bad somewhere in the build process. Once I reached that conclusion it was just a matter of getting everything that was added since the last time up2date was successful and cramming it in all at once. It turned out I was right. Dumb luck or whatever, but it all turned out OK in the end. At least it all worked out in the end. -- Microsoft: "You've got questions. We've got dancing paperclips" _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
