FC9 nvidia yum update conflict
 

I am trying to keep the system current just using the standard updater, and when I go to run my updates, this time I get the following:

Normally, I'd give it a shot to uninstall both those packages and re-install them, but since they are the nvidia packages, I'm a little hesitant (getting the nvidia card to work cleanly with everything wasn't a trivial task ... and I actually got Warcraft running better in linux than on the windows side of this box ... I'm close to never switching back to windows).

So ... any suggestions as to how to resolve this conflict?

This is one of those situations that it is best to just wait it out. USUALLY there is just a lag between one package getting into the repo and the other (updated version) missing the boat. Sometimes the packager (the guy) makes an error on when making the package. Either way, a couple day wait will usually clear things up. Video drivers are rarely a security threat so waiting a couple of days should not be a problem.

try do disable the livna repository by default and enable it only when necessary.
To do that, edit the file "/etc/yum.repos.d/livna.repo" and change all lines in this file from "enabled=1" to "enabled=0".

Using yum (the command line updater/installer), it is easy enable it. Just add "--enablerepo=livna" to the command, I mean, "yum install whatever --enablerepo=livna" to install something from the livna repo.

@lazlow: I've waited about two weeks now, which is why I posted. I don't mind waiting a bit longer and checking again, though, so I'll probably do that.

@marozsas: I went ahead and did this as well ... that let me accomplish at least the bug fix updates.

Thanks all!

if i get this correctly, the problem is that two packages have one and the same file (nvidia-xconfig)
try to uninstall nvidia-xconfig (which creates an /etc/X11/xorg.conf that you should already have) and if you might need the config program (maybe to create an up-to-date configuration), see if the program is still there.
any luck with this?

Sorry, been away a bit, but started a new thread that has some resemblance to this issue. Not sure how to link a thread correctly, so here's the full address

http://www.linuxquestions.org/questi...lities-662408/

Long story short, I did somewhat as advised here. I removed the kmod *everything* and tried to put akmod in its place (one of the major problems was simply that livna had not yet made stable kmod-nvidia drivers for the newest builds ... auto kmod is supposed to help fix that).

Now I'm close to resolving that (it works semi-beautifully), but haven't figured out how to get WINE to use the "new" drivers yet.

IE: OpenGL works great in linux now using the nvidia card (games, compiz, etc). WINE works well with most programs. WINE does /not/ however work with any D3D or OpenGL applications right now for me, complaining about GL errors.

I'll be banging my head against that later tonight some more. I'm almost to the point of trying to remove WINE and reinstall, which would be a pain because of the number of tweaks I've done (registry hacks, etc), but if it works, it works.

Just wanted to list what the downside of this was (at least, I believe this is what caused it since I don't want to blame my own inattentiveness ;) ).

When livna was disabled, the next update to fedora decided it could come through just fine, and as part of it, it removed all my xorg-nvidia and kmod-nvidia rpms. Ouch. I'm honestly not sure /why/ it removed those things and I certainly don't recall seeing that in the list of things it planned to do, but my suspicision is that it didn't see them in the repo anymore and then wiped them out.

I've been reworking it with akmod, but I'm not sure disabling livna is the best idea if you're dependent on nvidia drivers from them. I certainly could see disabling the "testing" repositories as well as the "source" ones, but the main, base livna.repo has a few things in it that I apparently use pretty heavily ;).