Daniel Kahn Gillmor:
> Package: mumble
> Version: 1.2.18-1
> Severity: wishlist
> 
> Mumble upstream apparently supports qt5 (at least in the 1.3.0
> prerelease series, i don't know about earlier).
> 
> see for example mentions of a QT5-only patch here:
> 
>    https://github.com/mumble-voip/mumble/issues/2728
> 
> and the build instructions here:
> 
>    https://wiki.mumble.info/wiki/BuildingLinux#1.3.x
> 
> mumble is one of the few remaining tools that keep me from purging
> qt4.  it'd be great to have a version built against QT5.  maybe use in
> debian experimental since 1.3.x hasn't been released yet?
> 
>        --dkg

Hello again, Daniel.

Here's where the mumble package stands:

  - mumble 1.2.x is not compilable with QT5.
  - mumble 1.3.x is compilable with QT4 and QT5
  - After the painful experience when Ron Lee was the maintainer of
    the mumble package, upstream requested that I only release stable
    releases, and not snapshots.
  - mumble 1.3.x is desirable because with QT5 it supports encryption
    modes that provide perfect forward secrecy
  - I've had working packaging prepared for mumble 1.3.x for a long time
    (> 1 year)
  - mumble 1.3.x has not yet been released
  - mumble 1.3.x source contains unreleasable files including IETF RFCs
    such that building a -dfsg tarball would be needed to upload a
    1.3.x version to experimental. I've discussed this problem with
    upstream -- their tarball release scripts need to be updated to
    strip these unreleasable files, but that work only needs to be done
    once a release is ready...
  - I discussed the -dfsg issue with several people at DebConf17 and
    some have mentioned using Files-Excluded in debian/copyright and
    tweaks to debian/watch to get uscan to build a -dfsg tarball
    automatically, which I'm looking into.

I'm aware QT4 needs to be removed from Debian. I can talk to upstream
about this, and see what I can do to create a mumble 1.3.x package that
could be uploaded to experimental. *shrug*

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Reply via email to