I just reinstalled my system, but for whatever reason can’t get rid of some package dependency problems. Can someone help me sort them out? Which repositories contain the necessary packages, and can I somehow install kde4-Amarok, -Gwenvieww, and -Digikam without downgrading other packages?
AMAROK:
#### YaST2 conflicts list - generated 2009-07-13 22:13:00 ####
kde4-amarok-2.0.1.1-2.1.1.i586 requires kdebase4-runtime < 4.1.60, but this requirement cannot be provided
uninstallable providers: kdebase4-runtime-4.1.3-4.1.i586[repo-oss]
kdebase4-runtime-4.1.3-4.2.9.i586[repo-update]
] Following actions will be done:
downgrade of kdebase4-runtime-4.2.4-2.13.i586 to kdebase4-runtime-4.1.3-4.2.9.i586
install kdebase4-runtime-4.1.3-4.2.9.i586 (with vendor change)
openSUSE Build Service
-->
openSUSE
(and about 80 other downgrades ... )
] do not install kde4-amarok-2.0.1.1-2.1.1.i586
] Ignore some dependencies of kde4-amarok
#### YaST2 conflicts list END ###
GWENVIEW:
#### YaST2 conflicts list - generated 2009-07-13 22:11:51 ####
gwenview-4.2.4-1.12.i586 requires kdebase4-runtime >= 4.2.4, but this requirement cannot be provided
] Ignore some dependencies of gwenview
] do not install kde4-gwenview-4.1.3-4.7.i586
] Following actions will be done:
downgrade of gwenview-4.2.4-1.12.i586 to gwenview-1.4.2-116.49.i586
install gwenview-1.4.2-116.49.i586 (with vendor change)
openSUSE Build Service
-->
openSUSE
downgrade of kdebase4-runtime-4.2.4-2.13.i586 to kdebase4-runtime-4.1.3-4.2.9.i586
install kdebase4-runtime-4.1.3-4.2.9.i586 (with vendor change)
openSUSE Build Service
-->
openSUSE
(... and tons of other downgrades ... )
#### YaST2 conflicts list END ###
DIGIKAM:
#### YaST2 conflicts list - generated 2009-07-13 22:12:33 ####
kde4-digikam-0.10.0-60.4.i586 requires kdebase4-runtime < 4.1.60, but this requirement cannot be provided
uninstallable providers: kdebase4-runtime-4.1.3-4.1.i586[repo-oss]
kdebase4-runtime-4.1.3-4.2.9.i586[repo-update]
] do not install kde4-digikam-0.10.0-60.4.i586
] Ignore some dependencies of kde4-digikam
] Following actions will be done:
downgrade of kdebase4-runtime-4.2.4-2.13.i586 to kdebase4-runtime-4.1.3-4.2.9.i586
install kdebase4-runtime-4.1.3-4.2.9.i586 (with vendor change)
openSUSE Build Service
-->
openSUSE
downgrade of kdebase4-workspace-4.2.4-3.11.i586 to kdebase4-workspace-4.1.3-10.3.7.i586
install kdebase4-workspace-4.1.3-10.3.7.i586 (with vendor change)
openSUSE Build Service
-->
openSUSE
( ... and tons of other downgrades ... )
#### YaST2 conflicts list END ###
My system environment:
OS: Linux 2.6.27.23-0.1-pae i686
System: openSUSE 11.1 (i586)
KDE: 4.2.4 (KDE 4.2.4) “release 2”
(Funnily enough, when I used One-Click-Installation to upgrade from KDE 4.1 to 4.2, it said ‘if you have problems with dependencies, go into “Advanced” and activate the main repository for your system’. I did just that, but in fact of a solution I got even more error messages … :sarcastic:
You need to be aware that there were some changes in naming so for example kde4-digikam is digikam, kde4-amarok is amarok. Try like that. Most of them will still have kde4-**** but many changed their names.
Hi. There is an issue with repository priorities when you upgrade to KDE 4.2.x or 4.3. Just give your update repository the same priority as your KDE 4.2 repository and you should be fine. If that does not help, please tell us which repositories you have activated. Good luck!
Guys, thanks for your help!
BenderBendingRodriguez: Thanks for the tip! I was actually able to install Gwenview for kde4 by choosing the package without the kde4- extension.
supertimorplusfort: I followed your advice and made the priorities for KDE:42 and Update even. I think this helped me with installing Gwenview (see above), but I’m still having problems with Amarok & Digikam.
(1) I’ve currently installed Amarok 1.4.10-26.2.1-i586 (came with the openSUSE 11.1 installation CD, I think). When I try to update to Amarok 2 (that is, the kde 4 version), I get an error message that “libamarok.so.0” can’t be found.
(2) As for Digikam, I got version 9.4-51.18-i586 installed right now (from repo-oss). Trying to update to 0.10.0 gives me an error message that “libdigikam.so.0” can’t be found.
What I don’t understand: If libamarok.so.0 are libdigikam.so.0 are not included in the updated packages, they shouldn’t be necessary, so why is Yast2 looking for them?
If they are necessary, why are they not included?
I have to admit that I have to plead complete ignorance when it comes to package management … :shame:
Make all your repos to autorefresh but disable the home repos. Refresh all and try to install amarok and digikam again, it is important that it refreshes.
Installing Digikam worked this time, thanks a bunch! 
With Amarok, I now get the following error message:
nothing provides libloudmouth-1.so.0 needed by amarok-2.1.1-2.9.i586
] do not install amarok-2.1.1-2.9.i586
By the way, would you recommend that I leave the OSS/Non-OSS repos switched off and focus on Update?
… I suppose I should stop messing around with the repos, but rather be a good boy and wait until KDE 4.3 …
search for:
libloudmouth-1.so.0 with rpm provides checked in software management
I have it and amarok
You can leave NON-OSS repo swithced off but i’d leave OSS on since Update contains ONLY packages that changed and lots of stuff didn’t change at all.
… I suppose I should stop messing around with the repos, but rather be a good boy and wait until KDE 4.3 …
Well, obviously you played a lot with your priorities. Just set all of them to 99 and you should be fine. And enable oss and non-oss again. They are vital! libloudmouth-1.so.0 is in oss for example. You don’t need autorefresh for oss and non-oss cause they never change.
Sorry to disappoint you, but situation regarding the priority issue won’t improve with KDE 4.3. If you want just try KDE 4.3. I run RC2 and it feels stable. Should you prefer any KDE 3 application over the KDE 4 ones, e.g. amarok, you can add the new KDE 3 repository. Things are called kde3-something there.
Guys, thanks for the pointers. It’s worked and I got Amarok II running now.
Apparently setting all repos to priority 99 is indeed a good idea … I wonder why there are 99 other priority options out there, though … ::X
