Joseph Zitt wrote:
Joseph Zitt wrote:
Clemens Ladisch wrote:
Yes, please remove _all_ old ALSA packages before
installing the new
ones.
I'll try that now.
Well, this is proving difficult and a bit confusing:
[root@localhost Documents]# ls alsa*.rpm
alsa-driver-0.9.4-fr2.i386.rpm alsaplayer-0.99.75-fr1.i386.rpm
alsa-lib-0.9.4-fr1.i386.rpm alsa-utils-0.9.4-fr1.i386.rpm
[root@localhost Documents]# rpm -Uvh alsa-*.rpm
Preparing... ###########################################
[100%]
package alsa-utils-0.9.4-fr1 is already installed
file /usr/share/alsa/alsa.conf from install of alsa-lib-0.9.4-fr1
conflicts with file from package libalsa-data-0.9.2-5mdk
Uninstall libalsa-data-0.9.2-5mdk, too.
[root@localhost Documents]# rpm -e
libalsa2-0.9.2-5mdk
libalsa-data-0.9.2-5mdk
error: removing these packages would break dependencies:
libalsa2 is needed by alsaplayer-0.99.74-1mdk
libalsa2 = 0.9.2 is needed by libalsa2-docs-0.9.2-5mdk
alsa-lib >= 0.9.0 is needed by alsa-utils-0.9.4-fr1
libasound.so.2 is needed by [many packages]
...
I suspect that this is less scary than it appears... but it at least
looks like installing from RPMs will break a whole lot of things.
Unfortunately, as far as I can tell, Mandrake only supplies RPMs up
through ALSA 0.9.2 which I understand from earlier messages is terribly
outdated in its USB-audio support.
What's my next step?
You could uninstall the old packages anyway (rpm has a parameter
--force or something like that), and then install the new packages;
the new library version should be compatible with the old one.
Or you could compile ALSA from the sources. When installing, the new
library will overwrite the old one, and rpm won't notice until it's
too late. ;-)
HTH
Clemens