On Friday November 9 2007 11:59:21 am Frank Cox wrote: > > In the dim and distant past, I'd tried upgrades, and spent > > ages ironing out the bugs. Later, I did fresh installs, and > > spent a much lesser amount of time customising the new > > install. Apart from the time, this seemed to be the > > differences: One is just re-configuring, the other is > > sorting out all the problems that aren't handled by the > > update process. > > It looks like I'm going to have to bite the bullet and install > from scratch if I want to put F8 on this computer. > > I fired up the update process again last night just before > 2am. It's now almost 11am the following day and the screen > was still at the exact same place that it got to on "resolving > dependencies" when I left it last night. I was having the same problem. I decided to update my two machines on F7 using yum. Both went off without great complications overnight. They both have 'issues' this morning, but they seem fairly trivial, so far. Avahi was not replaced/upgraded and I know have both the fc7 and fc8 versions installed. Remove fails with a cryptic error: # rpm -qa avahi avahi-0.6.17-1.fc7 avahi-0.6.21-6.fc8 [root@vrproductions3 ~]# rpm -e avahi-0.6.17-1.fc7 error: %postun(avahi-0.6.17-1.fc7.i386) scriptlet failed, exit status 1 On my home machine, vmware-server wouldn't start and the configuration script wouldn't work - I tried the latest 114 any-any patch but it wouldn't run very far, either. I had to leave before gathering up the info and posting more details. Otherwise, so far, so good I'll be more sanguine after a couple of more days -- Claude Jones Brunswick, MD, USA
