A new package named libasound-module-bluez5 is needed in order to distinguish between BlueZ4 and BlueZ5 versions of the aforementioned package.
Is the libasound-module-bluez have a generic api that ALSA uses such that it should not be versioned?
Dup *** This bug has been marked as a duplicate of bug 5030 ***