On Thu, 2005-03-31 at 11:26 +0200, Rolf Leggewie wrote: > I understand how to solve the situation at hand in my case. > What I am wondering about is how to deal with this bug (?) in general. > Should alsa-base conflict with pcmcia-modules-2.4.27-2-686 at least for > the current version? Or should I file a bug report against > pcmcia-modules-2.4.27-2-686 to make them conflict with alsa-base until > they provide those symbols? I do not think the situation should be left > as is but I also have trouble proposing the right fix. What do you suggest?
You are right that something is amiss. Either pcmcia-modules-2.4.27-2-686 is at fault for not providing the required symbols, or alsa-modules-2.4.27-2-686 is at fault for declaring: Suggests: kernel-pcmcia-modules-2.4.27-2-686 | pcmcia-modules-2.4.27-2-686 which implies that pcmcia-modules is as good as kernel-pcmcia-modules for its purposes. The same goes for -386, -k6, etc., of course. I think that declaring a Conflict is too strong since some people may want to install pcmcia-modules-2.4.27-2-686 and use non-PCMCIA drivers from alsa-modules-2.4.27-2-686. -- Thomas Hood <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]