libfarsight incorrectly linked against libjingle

[Michael Sheldon]

This is under Jaunty x86_64.

libjingle-transmitter in libfarsight looks for libjingle files in the form libjingle*-0.3.so.0, whereas they are now named libjingle*.so.0 (without the -0.3).

e.g.
/usr/lib/libjinglebase-0.3.so.0 -> /usr/lib/libjinglebase.so.0
/usr/lib/libjinglep2pclient-0.3.so.0 -> /usr/lib/libjinglep2pclient.so.0
/usr/lib/libjinglep2pbase-0.3.so.0 -> /usr/lib/libjinglep2pbase.so.0
etc.

This prevents things like telepathy's stream-engine (and any applications that make use of it) from being able to provide VoIP functionality for Google talk.

[Laurent Bigonville (bigon)]

I've just uploaded 0.1.28-2build1 that should fix this

[Martin Pitt (pitti)]

Accepted farsight into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Tico (ballagas)]

I just verified that this issue is resolved. It seems to address the problem as stated above.

laptop:/usr/lib/farsight-0.1-3$ ldd libjingle-transmitter.so
 libjinglebase.so.0 => /usr/lib/libjinglebase.so.0 (0xb8032000)
 libjinglep2pbase.so.0 => /usr/lib/libjinglep2pbase.so.0 (0xb7fc6000)
 libjinglep2pclient.so.0 => /usr/lib/libjinglep2pclient.so.0 (0xb7f9f000)

[Launchpad Janitor (janitor)]

This bug was fixed in the package farsight - 0.1.28-2build1

---------------
farsight (0.1.28-2build1) jaunty-proposed; urgency=low

  * Rebuild against new libjingle packages name (LP: #389203)

 -- Laurent Bigonville <email address hidden> Fri, 03 Jul 2009 16:58:03 +0200