liboss-salsa-asound2 tries to provide a replacement to libasound2 by declaring a Provides: libasound2 and a Conflicts: libasound2
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. On the other hand, there is *no* package that strongly depends on liboss-salsa-asound2, so the problem is with liboss-salsa-asound2, and not with the other packages. I may humbly suggest one of two solutions: - either drop liboss-salsa-asound2 - 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) Hope this helps --Roberto P.S.: this problem has been discovered automatically using the algorithms for computing strong dependencies and strong conflicts among packages, described in the papers [1] and [2] below. [1] Using strong conflicts to detect quality issues in component-based complex systems, ISEC 2010, February 25-27, 2010, Mysore, India. By Roberto Di Cosmo and Jaap Boender. (http://www.mancoosi.org/papers/isec10.pdf) [2] Strong Dependencies between Software Components, ESEM 2009, October 15-16, 2009, Lake Buena Vista, Florida, USA. By Pietro Abate, Jaap Boender, Roberto di Cosmo, and Stefano Zacchiroli. (http://www.mancoosi.org/papers/esem-2009.pdf) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
