[Pkg-telepathy-maintainers] Updating telepathy-qt

[Simon McVittie]

On 06/06/13 21:30, Diane Trout wrote:> I was working with the
debian-qt-kde and kde-telepathy teams to try and update
> kde-telepathy.
>
> We're currently blocked because one of our upstream components needs
> libtelepathy-qt4 0.9.3. and were wondering how best to go about
updating it?

Are you a DD, or do you have enough DDs on one of those teams to get
uploads sponsored? Is the kde-telepathy team the same as, or part of,
the KDE Extras Team that apparently maintains some related packages?

pkg-telepathy doesn't maintain anything else Qt, and I'm not sure
whether any of us regularly use KDE/Qt applications, so it might be best
if a KDE-related team adopts telepathy-qt. The KDE Extras Team already
apparently maintains telepathy-logger-qt; contacting that package's
maintainer about a future telepathy-logger SONAME transition is on my
to-do list.

> I've done a simple update which seems to work on my system,
> https://github.com/detrout/telepathy-qt

It looks as though fvisibility-inlines-hidden.patch may have been
applied upstream too - Ubuntu removed it with the update to 0.9.3, if
that's any indication.

Looking at the Ubuntu changelog[1], I see they have also updated some
symbols files (which you might want to pick up), and patched the package
to use a branched telepathy-farstream development package (which doesn't
exist in Debian).

I can see that this is going to be awkward when we want to upgrade
unstable from telepathy-farstream 0.4 (Farstream 0.1, GStreamer 0.10) to
telepathy-farstream 0.6 (Farstream 0.2, GStreamer 1.0), which is going
to be necessary as part of the GNOME 3.8 transition. Perhaps
libtelepathy-farstream-dev 0.6 needs to become
libtelepathy-farstream0.6-dev?

    S

[1] https://launchpad.net/ubuntu/+source/telepathy-qt/+changelog