Roberto Di Cosmo, le Sat 19 Mar 2011 14:46:01 +0100, a écrit : > liboss-salsa-asound2 tries to provide a replacement to libasound2 > by declaring a Provides: libasound2 and a Conflicts: libasound2
Yes. And fails to, that's a known wontfix issue. > Unfortunately, 1889 packages in squeeze absolutely need (we say 'strongly > depend on' [2]) the real package libasound2, and not the virtual one > (because the declared dependencies are versioned); actually, for the > same reason, a total of 2531 packages are incompatible (we say > 'strongly conflict' [1]) with liboss-salsa-asound2. Unfortunately, yes. > On the other hand, there is *no* package that strongly depends on > liboss-salsa-asound2, Sure, since in principle people use alsa, not oss-under-alsa (they should be fixed into simply using oss instead, if they did). > so the problem is with liboss-salsa-asound2, and not with the other > packages. Agreed, but still wontfix. > I may humbly suggest one of two solutions: > > - either drop liboss-salsa-asound2 Why? It can be useful in the cases where it can be installed. And we _do_ need it on kfreebsd & hurd. > - or change the metadata by simply allowing liboss-salsa-asound2 to > overwrite files belonging to libasound2 (if this is enough that > /usr/lib/libasound.so.2 is the one contained in this package for > everything to work fine) The libasound.so.2 provided by libsalsa clearly doesn't provide enough support for everything to work fine: the announced compatibility is only 1.0.5, and there's no seq support. So yes, it provides poor support for Linux, but that's an upstream lack of feature, and not a reason for dropping it completely. Samuel -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
