Dependencies

[daviddoria]

I've been having lots of crashes lately (particularly in KDevelop). I didn't know what else to do, so I said lets just update the whole system. So I turned on Fedora - Rawhide repo and did
sudo yum update

But I got zillions of dependency errors, even with
sudo yum --skip-broken update

Is this a case of "just wait till it gets fixed/better"?

Thanks,

Dave

[Nokia]

This is a case of reinstalling F10 and never turning on rawhide repo again.

[daviddoria]

why reinstall?
why never turn on rawhide?

[bee]

why never turn on rawhide?
Because rawhide is the source of yours "zillions of dependency errors" :D :p :p :rolleyes: :cool:

bye!!!!!!:):):)

[daviddoria]

but isn't that the idea? that you can start to use some of the new stuff before you install F11?

[bee]

but isn't that the idea? that you can start to use some of the new stuff before you install F11?
Well, yeah... if you know what you're doing :confused:... and if you are a Fedora developer (or a sort of...) :D :rolleyes:
why reinstall?
I'm not sure, so i don't know for sure :confused: :confused: :rolleyes:.... maybe it's possible to disable the rawhide repo, and reinstall the software you've updated (restoring old versions) in order to avoid a full reinstall. :D :D :cool: :rolleyes:
So, you have to disable rawhide, and check the logs files you have in:
ls -l /var/log/yum*
and look for the software you have updated from rawhide. :D Once you know what applications were updated... i think you need to remove them and reinstall them from the standard F10 update repo. :rolleyes: :D :cool: :)
btw, i cant guarantee you, that will work :p :D

bye!!!!!!!:):):)

[vallimar]

Rawhide is almost always in a broken state of one sort or another.
Unless you really know what you are doing, don't attempt to use it as your normal distro.
If you want to test the new stuff, install the Alpha.. preferably onto a testing partition apart
from your daily usage distro. If you want to run an unsupported, non-stable version of the
software, expect lots of bugs, brokeness and not so much help.

[bee]

ls -l /var/log/yum*
to easily get a list i think you have to write something like:
su -l
cd /var/log
ls -1 yum* | xargs cat | grep fc11
that is better if you run it only on the file of today.
or
rpm -qa | grep fc11
Hope that will help you a bit more to find what you have to reinstall. :rolleyes: :cool:

bye!!!!!!!!!!:):):)

[Jake]

Rawhide is almost always in a broken state of one sort or another.
Unless you really know what you are doing, don't attempt to use it as your normal distro.
If you want to test the new stuff, install the Alpha.. preferably onto a testing partition apart
from your daily usage distro. If you want to run an unsupported, non-stable version of the
software, expect lots of bugs, brokeness and not so much help.Alpha, is basically just a snapshot of Rawhide for that day, and updates via Rawhide, so the dependency issues may not be fixed, and lots may come along.

[vallimar]

I'm well aware of that, hence my posting of the brokeness and unsupported nature of things
and why it shouldn't be done unless you know what you are doing. But the alpha is not just a
random snapshot as you indicate, it's a planned snapshot during a time when Rawhide is thought
to mostly be all working as far as the features they want to promote. Which is also why it was
delayed this last time, because they found bugs and had to regenerate it a couple times and it
still had minor issues. Hence, if you are going to test, it's far safer to start from the alpha, which
is considered mostly working, than just grabbing straight from rawhide, which may be completely
broken at that time. Which part of that were you attempting to clarify or didn't understand?

[AdamW]

For a start, when upgrading to Rawhide, you should do:

yum upgrade

not:

yum update

that should solve a lot of the problems.

As the others have said, Rawhide is the development branch of Fedora. You can certainly use it to get a preview of the new stuff that's coming along, but it's not a good idea to use it as your day to day system unless you're very flexible, you have good backups, and you can live with stuff occasionally just stopping working. Generally you should install it on a test system, in a test partition, or in a virtual machine, and you should view it as a chance to check out some bleeding-edge stuff and testing, not as a stable, dependable system :)

'Upgrade to Rawhide!' is generally never a good answer to 'Hmm, I have a problem, what should I do?'

[bob]

I agree 100% with everyone on sticking to stable versions, maybe adding a partition if you want to test Rawhide, knowing that there will be problems and you'll delete it later on. One comment I did want to mention, for those times when you're stuck with dependency issues that 'skip-broken' misses:

First, try to resolve it with Yumex (yum install yumex) since you can pick and choose the updates very easily and sometimes have a visual clue of what the problem really is (multiple installs of a package, perhaps).

Second, Rahul had come up with a script years ago that I still find useful, although much slower. Copy this code and save it in your /home/username as "yum.sh"

#!/bin/sh
for i in `yum list updates |cut -f 1 -d " " |grep -A 500 -e Updated |\
grep -v -e Updated` ; do
echo "Updating $i"
yum -y update $i
done

Then, simply log into a terminal as 'su' and run 'sh yum.sh'

As I mentioned, this will examine every update individually, which takes much, much longer, but it does work. Rahul's also suggested reporting a Bugzilla on the times when 'skip-broken' fails, so that the team can correct any errors for the next version.