I can’t uninstall firefox and xulrunner because yast gives me a lot of error of dependencies. (or downgrade KDE 4.3 to 4.1). Is it possible to uninstall and then reinstall in command line forgetting the dependencies? is it too risky?
I’m gonna try that growbag says, it’s simple and nice. i like this solution. hope it works
i didn’t realize that repo errors. I’ve playing with latest kde and i think i made a mistake. And then another one (and another one, …). I think that my system has some parts broken. As I can see that’s not a normal problem. Maybe reinstalling can be a plausible solution.
I must go out, so i cannot try the different solutions that i’m pending to do. Later i’m gonna post, I hope that it’ll work
First of all, thanks a lot to everone who has answered.
Firefox now starts, and that’s what I’ve done to solve it (thanks FeatherMonkey):
1.- Change firefox binary from mozilla repo to updates repo.
2.- xulrunner190 from 586 to X86_64 (my system is 64 bits)
3.- put packman repo on and videolan off just like BenderBendingRodriguez told me a few lines above…
I did the three points at the same time, so i don’t know if it’s only one of them who solves my problem or two, etc…
Another question, BenderBendingRodriguez & caf4926 told me to update unconditionally, how can I do this? If I translate directly from spanish yast2 says “update if new package available” it says nothing from unconditionally. As you can imagine my system language is spanish.
FeatherMonkey you told me: “At the moment you have xulrunner from update and mozilla from mozilla”. I think that you want to said xulrunner from update and firefox from mozilla, but how knew you that? It’s amazing! thanks a lot!
Finally I’m really really sorry about my bad english.
As for how I knew by the radio button and looking at the mozilla repo.
This is one of the reasons why I’m not a big fan of update unconditionally(To do this there is an option to select all in list(Think click after select system as repo), then I think you should have update if newer))
This is why prefer zypper dup as this will/should solve these type of problems, if you have an update on update and the repos = the same priority, then it isn’t wrong it is updating to the latest. As to why the 2 repos can’t exist together I don’t know why I always thought rpm didn’t really mind this. But with zypper dup then if this happens then it will not update to the newer as for the exact choice I don’t know but it would keep the repos the same, so it wouldn’t mix the repo’s.
Edit Oh well after reading the zypper page update shouldn’t of done this, something else seems to of mixed them. Maybe an ignored dependency when going to 3.5.