Hi Giampiero, On Wed, Apr 24, 2013 at 03:48:21PM +0200, Giampiero Salvi wrote: > Dear maintainers of the wavesurfer and libsnack2 packages, > I am one of the contributors to wavesurfer and work in the lab where both > wavesurfer and snack were developed.
Then it is very glad news to hear from you! I hadn't been quite sure what the status of this there was, but I'm very happy to hear that it really is still an active interest. > I am writing to both bug threads because I think we need some coordination > in order to solve this problem. In http://bugs.debian.org/659974 it is > said that this is not a urgent issue because not many people complained. It wasn't so much that not enough people complained, as that we were well into the freeze for the Wheezy release, and I was worried that not enough people might test it with alsa to shake out any other problems in the time we had remaining for that. I use this nearly every day too, but not with alsa, and Sergei had noted there were known problems with snack-alsa compared to OSS. > I can tell that this bug affects a whole faculty at KTH, Stockholm where I > work and use wavesurfer as a teaching tool. The way we solved the issue is > to install a binary version of wavesurfer outside the apt-get system, which > is far from optimal. I agree. Things don't get much closer to ideal than when upstream is also using the packages, bugs get found and fixed much quicker that way. > From the threads http://bugs.debian.org/659974 and > http://bugs.debian.org/567713 it is not clear if any decision has been > reached, yet. I believe the correct way, as has been suggested already, is > to have wavesurfer depend on libsnack2 (without version) and make libsnack2 > a virtual package provided alternatively by libsnack2-alsa or libsnack2-oss. Dropping the version from the wavesurfer dep isn't quite 'correct', since the version requirement is real. But we can get away with doing that as one option since the version is very old now and we can play the "not a supported upgrade" card on anyone that does get bitten by it (which realistically should be pretty close to nobody now). Given what Sergei has said he prefers for libsnack at present, that's almost surely what we'll end up doing. > However you decide to solve the issue, please do this as soon as possible, > because it affects more users than you think. It's almost certainly too late to do this for Wheezy now (since it is due to release next week) - but that means the freeze will lift then too, so I can push a fix for the next release, and the option for doing backports opens. Which means we mostly need to figure out a better plan B for making that available to your users if we can. Cheers, Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
