So I've just finished setting up FC6 how I wanted it on my Macbook. Anyone who's got Linux running on a Macbook will know it takes a few tweaks.

So firstly, is it worth upgrading to F7? I'm already running the latest stable kernel since I had to compile in various extra things.

So I guess it comes down to package sets. How out of date are the FC6 repos compared to F7?

As far as upgrading, should I install from Anaconda? Or can I change to the Fedora 7 repositories and upgrade from there?

Thanks in advance,
-deus-

If you're unfamiliar with basic system administration it is probably not a good idea to upgrade.

Fedora 7 has a new kernel which uses libata for PATA disks, so what used to be hd[a-d] is now sd[a-d] and would require you to modify your fstab and possibly recreate your initramfs afterwards with mkinitrd.

If this isn't an issue, package sets are not a big concern.
You can upgrade using Yum or with the DVD or boot.iso over HTTP.

__________________
[autopsy@localhost ~]$ cat you >>/dev/null && rm -rf you

Awesome, thanks. What do I do about Livna and such? Switch to their FC7 repo and update?

Also, since I'm using a vanilla kernel, what will happen when I upgrade? Will the new F7 kernel be added to my menu.lst or will it remove all my current kernels and just leave the new one? I need to keep using my current kernel, and it's the latest stable anyway.

-deus-

When you upgrade the machine, it will already use the new Livna repository unless you have values hardcoded in /etc/yum.repos.d/livna.repo
Nothing should happen that I can think of.
The scenario I described earlier is for upgrading from FC6 to a F7 kernel. As long as you decide not to format your boot or root partitoins, all the data should be upgraded and your kernel would stay the same, it will probably change the default value in grub.conf, but that is easy to change back to your custom kernel.

__________________
[autopsy@localhost ~]$ cat you >>/dev/null && rm -rf you

Uh, snap, it fucked up.

Everything was going fine until yum got about halfway with updating pages, then it just stopped.

I ran yum again to find it complaining about yum, dbus, and rpm Python modules not being installed, so I downloaded and installed them manually from the F7 repo.

That seemed to enable me to start yum without it barfing, but now...

And it just hangs there.

Same thing happens with yum update

Help?

-deus-

That's odd for it to just stop, how long do you think you waited when it was stopped before you did anything else?

That seems very strange, in the course of yum doing a release upgrade to another release, while packages are being upgraded Yum doesn't reload anything, definitely something to look into and report if we determine it is a bug in a package or some other problem that only occurs when updating specific packages.
After making sure yum-updatesd service is off or simply not installed and that no Yum processes are running, try this:
If you find it is still hanging, try:
Do not interrupt that process.

What can happen is the RPM database lock files may be left by a killed process or some other reason.. such as a RPM %post script which happen to wind up in a deadlock or possibly was killed for whatever reason. It isn't common now but it can still happen, it used to be more common in earlier versions of Fedora since RPM has been going through heavy development.

Regardless if it fixes it or not, could you also post your /var/log/yum.log file here?

__________________
[autopsy@localhost ~]$ cat you >>/dev/null && rm -rf you

It went back to the root prompt.

I tried this. It got interesting.

http://rafb.net/p/M4ypiY92.html

I killed it when it was getting nowhere.

Sure.

http://rafb.net/p/hRF6d998.html

Any ideas?

Thanks a lot,
-deus-

Okay, now I just have dependency issues:

http://rafb.net/p/Hw0tnX90.html

It seems to be still looking for some FC6 packages.

Any ideas?

-deus-

Those are all missing dependency issues, while they should be satisfied, they probably are. Run:
Then try the upgrade again.

__________________
[autopsy@localhost ~]$ cat you >>/dev/null && rm -rf you

I've tried that. It still throws the same dependency errors.



-deus-