Migrate to farsight 0.2* / gstreamer 1.0
Bug #1295207 reported by
Bryan Quigley
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Pidgin |
Unknown
|
Unknown
|
|||
pidgin (Debian) |
Fix Released
|
Unknown
|
|||
pidgin (Fedora) |
Fix Released
|
Undecided
|
|||
pidgin (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
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:/
description: | updated |
Changed in pidgin (Debian): | |
status: | Unknown → Confirmed |
Changed in pidgin (Debian): | |
status: | Confirmed → Fix Released |
Changed in pidgin (Fedora): | |
importance: | Unknown → Undecided |
status: | Unknown → Fix Released |
To post a comment you must log in.
We would like to complete the gstreamer 1.0 transition and get rid of gstreamer 0.10 from the live cd entirely. libpurple is one of the remaining obstacles to reaching this goal.
https:/ /developer. pidgin. im/ticket/ 15386 has a patch to port pidgin to 1.0