Comment 4 for bug 956422

You are correct, we in fact disabled audio/video support because of
missing codecs.

Now to the issue: if a simple rename does the trick i guess there
should be no problem in having it since the codepaths are never (?)
executed.

Hence I don't think it is worth investigating this issue further but
ofcourse ymmv.

btw: i think (hello upstream) this could be solved with some
try..except import trick like:
try
import farsight
except importerror
import farstream as farsight

or something like that, so we mantain compatibility with older
oses..but ofcourse this has nothing to do with precise's package

greets

2012/3/16 Jason Conti <email address hidden>:
> Although, since audio/video are disabled anyway, maybe we could just
> drop the python-farstream dependency? I verified all of the symbols
> renamed in the patch, but
> http://www.freedesktop.org/wiki/Farstream/ApiChanges makes me think
> there may be a few more changes required.
>
> Plus, I'm not sure we have the codecs available necessary to test if any
> of this actually works, even if support was re-enabled.
>
> --
> You received this bug notification because you are subscribed to emesene
> in Ubuntu.
> https://bugs.launchpad.net/bugs/956422
>
> Title:
>  Port to farstream (2.12.1+dfsg-1ubuntu1 conflicts with empathy)
>
> Status in “emesene” package in Ubuntu:
>  New
>
> Bug description:
>  emesene currently depends on python-farsight from the farsight2
>  package, however this may soon be removed:
>  https://bugs.launchpad.net/ubuntu/+source/farsight2/+bug/954026 since
>  it was renamed to farstream upstream.
>
>  Currently, installing emesene will result in empathy being removed
>  because of conflicts between the farsight and farstream packages. The
>  symbols in the python-farstream package haven't changed, except for a
>  mass renaming from farsight to farstream.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/956422/+subscriptions