Bug#459198:

["Federico Grau" <grauf@rfa.org>]

Hello Caroline, 

I've been trying to chase this bug down also.  The last spot I left it at was
with debian bug 476699, which I have yet to hear a response back from the
maintainer.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476699


In brief summary, it looks like the current libsoundtouch in debian has it's
own pkg-config file which fails the "pkg-config" test in Audacity.

Hopefully an updated libsoundtouch can be released which will solve the
problem.

donfede

On Wed, Apr 30, 2008 at 08:31:14AM +0100, Caroline Ford wrote:
> I've been doing some work on the Ubuntu version of this bug
> (https://bugs.edge.launchpad.net/ubuntu/+source/audacity/+bug/193593)
> and this is what I've discovered.
> 
> libsoundtouch1-dev is already a build dependency, but wasn't set to
> compile against it. Adding  --with-soundtouch=system to
> DEB_CONFIGURE_EXTRA_FLAGS := $(T1_DEB_CONFIGURE_EXTRA_FLAGS) in
> debian/rules fixes that.
> 
> However it still doesn't find it.
> 
> http://www.audacityteam.org/forum/viewtopic.php?f=19&t=188 says that
> the test for lib-soundtouch1-dev is looking for 1.3.1 +. We have a
> lower version (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462643)
> 
> Also our lib-soundtouch1-dev has a different .pc file to upstream.
> (https://bugs.edge.launchpad.net/ubuntu/+source/soundtouch/+bug/214929)
> 
> Audacity are looking for the same name as upstream.
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-multimedia-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-- 
Federico Grau
Free Software Developer and Sysadmin
Radio Free Asia
2025 M Street, NW
Suite 300
Washington, DC  20036
202-587-2046  Telephone
202-721-7468  Facsimile
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and may
contain information that is privileged and confidential.  Any unauthorized
dissemination, distribution, or copying is strictly prohibited.  If you
receive this transmission in error, please contact network@rfa.org.