Hello! Am Dienstag, 28. März 2006 11:10 schrieb Stephan Binner:

Only at day of release, latter is regularly updated (eg to 3.5.2 today :-).

YaST just shows me 3.5.1 as version number and I get some conflicts. The files are dated 28th March though. Is there maybe a mistake with the version-numbers? Or is my mirror not updated properly yet? Sven #### YaST2 conflicts list - generated 2006-03-28 18:54:44 #### kdelibs3 nicht verfgbar Ben�igt von: kdebase3 ben�igt kdelibs3 >= 3.5.2- Konfliktl�ung: ( ) Alle 12 entsprechenden Pakete l�chen kdeartwork3 l�chen schafkopf l�chen kdebase3-nsplugin l�chen kdeaddons3-kate l�chen amarok-xine l�chen kdebase3-SuSE l�chen amarok-libvisual l�chen kdebase3-extra l�chen Weitere 4... ( ) Diesen Konflikt ignorieren und ein inkonsistentes System riskieren Konflikt mit kdebase3 3.5.1-45 Nicht erfllte Abh�gigkeiten: kdebase3 ben�igt kdelibs3 >= 3.5.2- Konfliktl�ung: ( ) kdebase3 nicht aktualisieren ( ) Diesen Konflikt ignorieren und ein inkonsistentes System riskieren #### YaST2 conflicts list END ###

Hi! Am Dienstag, 28. März 2006 20:58 schrieb Michael Eichstädt:

as we don´t know which server you use we can only guess....

I use rwth-aachen.de and the source is refreshed automatically everytime the YaST-module starts up. I'll try again tommorrow. Sven

On Tue, 2006-03-28 at 23:24 +0100, ianseeks wrote:

I've tried 2 sites to download the rpms (one being ftp.suse.com) and I end up with dependency issues where KDEbase and Amarok and few others require kdelibs >= 3.5.2. Kdelibs is listed as a download release of 3.5.1-?? This has happened to me quite a lot of times over the years - is this a problem with the packagers not being diligent?

In a way. The supplementary directory is basically a testing ground. Anything you find in there is hugely untested, and is provided only for those who know the risks and accept them. The build system is almost fully automated, and it happens that there are packages in the build system which haven't been provided externally, so you get dependency problems. It also happens that the package was built in the wrong distribution environment (e.g. a 9.3 package built in a 10.0 or 10.1 environment, sometimes even vice versa) If it ever happens in an officially provided package, then would be cause to complain about lacking diligence. But these packages are experimental, built for testing only, and should not be relied on for anything serious

On Wednesday, 29. March 2006 10:34, Sven Burmeister wrote:

Thanks to all that use the supplementary, as those are people that potentially report bugs and hence help SuSE in providing a better product, which will be/is part of the next distribution and thus also a benefit for

People testing the SUSE Linux 10.1 development releases are for more valuable, there is no time to hunt SUSE 9.2 specific problems of the KDE 3.5 packages. Bye, Steve

On Tuesday, 28. March 2006 19:01, Sven Burmeister wrote:

files are dated 28th March though. Is there maybe a mistake with the version-numbers? Or is my mirror not updated properly yet?

Some rpms weren't synced out because they weren't properly within the build system. The missing packages start now to appear on the servers. Bye, Steve

On Wednesday 29 March 2006 00:00, Christian Fröbel wrote:

Hello Karaoulis,

just follow the instructions given here: http://en.opensuse.org/Restricted_Formats and you should have mp3-support.

bye, Christian

No, that's not the answer. I prefer installing rpms from packman. BUT , packman ony support KDE 3.4.2 (obvsiously) and if someone update the system via supplementary, must stick with kdemultimedia 3.4.2. So the really question is if someone install the missing rpms from kde.org (like arts-mad, kdemultimedia-mad etc) will mp3 come back in life (without using the ugly thing called realplayer) Thank you . __________________________________________________ ×ñçóéìïðïéåßôå Yahoo!; ÂáñåèÞêáôå ôá åíï÷ëçôéêÜ ìçíýìáôá (spam); Ôï Yahoo! Mail äéáèÝôåé ôçí êáëýôåñç äõíáôÞ ðñïóôáóßá êáôÜ ôùí åíï÷ëçôéêþí ìçíõìÜôùí http://mail.yahoo.gr