The issue here seems to be twofold:
a) portscout/portsmon somehow doesn't see version 1.2.9 that was released on Sourceforge a while ago for some reason
b) mumble development has shifted to GitHub, so the port should be updated accordingly as the recently released 1.2.10 is not on Sourceforge.
(This probably applies to audio/mumble as well)
thanks for the heads up on this
(In reply to Mark Felder from comment #1)
I'm hitting build issues for murmur which I think are directly related to the ones we have with mumble: upstream has forked QT and backported newer crypto functionality than exists in QT4. As a result you can *only* build with their fork of QT now.
This is not permanent; this was a security-enhancement stopgap until they release 1.3.0 which will be built against QT5.
As a result I'm not sure we can update audio/murmur yet either.
Created attachment 163025 [details]
update murmur to 1.2.10
I was wrong. Can you test this? It should work :-)
Patch applied and tested. (We don't use the dbus and bonjour features, so these *might* be broken; Ice however works just fine)
Thank you very much!
(In reply to noah.bergbauer from comment #4)
Have you tested with any Windows or OSX Mumble clients? Those could possibly have crypto that this server doesn't support and be problematic. That's my main concern, but I'm not sure if the murmur server can mistakenly advertise that capability.
Neither Windows nor Linux users (with versions ranging from 1.2.8 to 1.2.10) are experiencing any issues since updating the server to 1.2.10.
We don't have any OSX users.
A commit references this bug:
Date: Thu Nov 12 20:23:54 UTC 2015
New revision: 401396
audio/murmur: Update to 1.2.10