desktop-packages team mailing list archive

[Launchpad Bug Tracker <1295207@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package pidgin - 1:2.10.11-0ubuntu2

---------------
pidgin (1:2.10.11-0ubuntu2) wily; urgency=medium

  * debian/control:
    - Build-depend on libgstreamer1.0-dev, libgstreamer-plugins-base1.0-dev,
      libfarstream-0.2
    - Recommend gstreamer1.0-plugins-base, gstreamer1.0-plugins-good
  * debian/patches/gstreamer1.patch:
    - Use gstreamer 1.0 (LP: #1295207)

 -- Robert Ancell <robert.ancell@xxxxxxxxxxxxx>  Fri, 29 May 2015
11:28:51 +1200

** Changed in: pidgin (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1295207

Title:
  Migrate to farsight 0.2* / gstreamer 1.0

Status in Pidgin:
  Unknown
Status in pidgin package in Ubuntu:
  Fix Released
Status in pidgin package in Debian:
  Confirmed
Status in pidgin package in Fedora:
  Unknown

Bug description:
  1) Ubuntu 14.04
  2) 1:2.10.9-0ubuntu2
  3) I expect it to depend against the latest farsight/gstreamer 1.0
  4) Instead, it's one of the reasons we still have gstreamer0.10 on the trusty cd, through libpurple.

  It seems upstream already supports building against farstream-0.2 and gstreamer1.0, see:
  https://developer.pidgin.im/wiki/Dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/pidgin/+bug/1295207/+subscriptions