View Full Version : Alpha pain...
16th March 2009, 05:05 AM
Is anyone else seeing this???
I installed from the Alpha DVD so I could keep ext4. After install, running yum-update tols me I had 1200+ updates to install. I let a simple yum-update run overnight and when I came back, I could not get into the system. Every cursor movement or keystroke flashed the solar flares background and then black. Rebooting was also a no-go.
I dropped back and re-installed from the DVD then set my runlevel to 3. I finally got an ethernet connection configured and when I tried to run the yum-complete-transaction, it turned out all my packages failed checksum and this generated a mess.
I don't know where to go with this...
Does Fedora post daily-build DVD images like Ubuntu does?
16th March 2009, 05:18 AM
not daily no, i think they do make weekly ones, check the iso image mirrors
16th March 2009, 10:06 AM
After installation of Alpha, update RPM first ( yum update rpm)
After that update the rest
16th March 2009, 02:41 PM
I'll give it one more shot, but I think I hit a snag there as well. Invalid checksums, I think...
17th March 2009, 03:03 AM
I tried that approach. After updating rpm, I ran a yum update and it ended up giving me an unfinished transaction and an unusable Gnome environment. I rebooted and ran yum-complete-transaction and when it was done, I was in the same place, no login was possible.
There must be a list and an approach to take to these updates, but due to the proximity of Beta, it might be best to wait. I'm sure if I was getting updates from day 1, it would be relatively OK, but I'm not in that boat and without daily builds, it's tough to get current.
If anyone has any other advice, I might try it again, but right now that drive is a paper-weight. I can boot the DVD in to rescue mode, but I fear that something didn't update properly that left me in this hosed condition...
17th March 2009, 04:09 AM
Hrrm, I ran into something similar, but in my case, there was a reason it didn't complete transaction--I don't remember what it was, but basically, after that, there was no /etc/passwd, only a passwd.rpmnew and a passwd- (with a dash--not a tilde) after it.
In general, step one is to install. You've probably figured that one out. :) Step two is, as mentioned, yum update rpm
(That fixes the md5 issues).
Then, after that, aside from that one time I had the trouble, I run yum update and reboot and everything is fine. I should add that I do a minimal install, no desktop environment and also unchecking all apps, games, etc. to cut down on the number of updates after installation.
17th March 2009, 04:19 AM
For that amount of updates you could try "yum upgrade" after following previous instructions.
21st March 2009, 06:52 AM
So, I ran yum update rpm and then yum upgrade. Python-slip was updated and Gnome locked up solid. I killed gnome-session and started yum-complete-transaction from a tty. It's running now. Let's see what happens...
22nd March 2009, 12:52 AM
I saw a bunch of files being replaced in /etc. Things like group, shadow and passwd. I cp'd the saved files back to the originals while booted in rescue mode and it didn't matter, I could not log in. I guess I have no choice but to wait for the beta release...
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.