Package Details: mumble-git 1:1.3.0.rc2.r1004.gf5489231a-1

Git Clone URL: (read-only, click to copy)
Package Base: mumble-git
Description: An Open Source, low-latency, high quality voice chat software (git version)
Upstream URL:
Keywords: audio communication multimedia network voip
Licenses: BSD
Conflicts: mumble
Provides: mumble
Submitter: None
Maintainer: Radioactiveman
Last Packager: Radioactiveman
Votes: 47
Popularity: 0.000000
First Submitted: 2009-05-30 19:46
Last Updated: 2020-10-28 22:53

Dependencies (34)

Required by (6)

Sources (5)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

mqs commented on 2020-11-12 01:54

Thank you for providing this, the "normal" mumble package seems to crash quite often on my system.

When trying to build this package, I get the following error since a while (the last working version I have installed is 1:1.3.0.rc2.r591.g7c67ea33f-1):

-- speexdsp found | Version: 1.2.0
-- Disabling warnings for targets: rnnoise
-- speech-dispatcher found | Version: 0.10.1
-- Qt5 component found: DBus | Version: 5.15.1
-- Qt5 component found: LinguistTools | Version: 5.15.1
-- ALSA found
-- Looking for sys/cdefs.h
-- Looking for sys/cdefs.h - not found
CMake Error at overlay_gl/CMakeLists.txt:39 (message):
  Can't find the 32bit version of sys/cdefs.h - did you install g++-multilib?

-- Configuring incomplete, errors occurred!
See also "/home/mqus/.cache/yay/mumble-git/src/mumble/build/CMakeFiles/CMakeOutput.log".
See also "/home/mqus/.cache/yay/mumble-git/src/mumble/build/CMakeFiles/CMakeError.log".

In case you noticed yay in the logs: Yes, I also tried to build it manually with makepkg -sr but the same error was thrown. Let me know if you also need the log files referenced above.

Radioactiveman commented on 2020-06-02 17:17

If you experience the problem below when updating packages, first remove mumble-git, then update all packages including protobuf and finally compile mumble-git again.

# pacman -Syu
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing protobuf (3.12.0-1) breaks dependency '' required by mumble-git

Radioactiveman commented on 2020-04-13 12:36

@dvzrv: Alright, I have updated the PKGBUILD accordingly.

dvzrv commented on 2020-04-13 12:22

@Radioactiveman: No, that is the next stable release version, that is referred to from within that application.

The latest git tag is:

git ls-remote -t |cut -d '/' -f3 |sort -r |head -n1

The version this package needs to track is the latest version tag + how many commits since that tag, not some arbitrary next release version number in a file.

We have the VCS package guidelines for a reason, please stick to them.

Radioactiveman commented on 2020-04-13 12:08

@dvzrv: But the Git version is 1.4.0, not 1.3.0-RC2 - see mumble.pri. However appending "git version" to the description would help maybe.

dvzrv commented on 2020-04-10 14:47

@Radioactiveman: Please introduce an epoch and remove the custom _version in your PKGBUILD.

We're getting out-of-date notifications from unknowing users, thinking that 1.4.0 is out (which it is not).

The right way to get the current version string would be to use the following (as stated in the VCS package guidelines):

pkgver() {
  cd "$_pkgname"
  git describe --long --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g'

IncredibleLaser commented on 2019-04-11 16:55

Thanks for the quick update. I can confirm building in a clean CHROOT works now.

Radioactiveman commented on 2019-04-11 16:36

@IncredibleLaser Fixed, thank you.

IncredibleLaser commented on 2019-04-11 16:15

This package currently doesn't build without python installed. You'll get "Project ERROR: Unable to find the system's Python binary. Some scripts invoked during the Mumble build use Python. You can manually specify it via the MUMBLE_PYTHON environment variable (either 2 or 3)." Please add python as a make dependency. Thanks.

Radioactiveman commented on 2019-03-31 16:50

@C0rn3j: Sorry for the late response as well. But I have found a solution. :) Install espeak-ng instead of espeak. See also