Notice: Undefined variable: name in /srv/http/vhosts/ on line 248

Package Details: mumble-snapshot 1.3.0_1902_gd871f34-1

Git Clone URL: (read-only)
Package Base: mumble-snapshot
Description: A high quality voice chat program.
Upstream URL:
Licenses: BSD
Conflicts: mumble
Provides: mumble
Submitter: synapse84
Maintainer: synapse84
Last Packager: synapse84
Votes: 5
Popularity: 0.558636
First Submitted: 2014-08-01 01:30
Last Updated: 2017-02-04 10:56

Pinned Comments

synapse84 commented on 2016-10-23 05:49

PGP signature verification is now enabled.

To verify the signature you must retrieve the key with the following command:
$ gpg --keyserver --recv-keys C4666C6767A26017CE68406988048D0D625297A0

2017-01-24: key updated

Latest Comments

synapse84 commented on 2016-10-23 05:49

PGP signature verification is now enabled.

To verify the signature you must retrieve the key with the following command:
$ gpg --keyserver --recv-keys C4666C6767A26017CE68406988048D0D625297A0

2017-01-24: key updated

synapse84 commented on 2016-10-23 02:22

@Kiwii Sorry for the late response, I've been rather busy lately.

I've tried to use the pgp signature in the past, but it's always forced user intervention. I dislike requiring user intervention if i can prevent it, but I agree using the pgp signature is better. I'll see about using the signature over the next few days.

I don't know much about the aur comments markup, so I'm not sure if you can prevent it from stripping leading spaces.

Kiwii commented on 2016-10-18 17:38

May I suggest changing the pkgbuild to check the pgp signature provided by upstream instead of the sha256 generated by you?

That way you don't have to regenerate the hash for every version bump and we have a stronger verification of the authenticity of the source files.

GnuPG is present on all Arch installs anyway since pacman depends on gpgme, so the only inconvenience is the user having to import the key once¹.

All you'd have to do is add the *.sig file to the source array, list the valid key fingerprint and skip the sha256, like so:


The fingerprint can be found on upstream's github² in the form "3BD0 ECA5 9253 19AF 89C2 5865 B585 609C 5A2B E0C1" and belongs to "Mumble Automatic Build Infrastructure 2016 <>". Apparently upstream generates a new key each year.

Arch Wiki also recommends this over checksums: "If possible, however, always test the authenticity of the files by adding their signatures to the source array: in this case you will also be able to safely skip their checksum verification altogether"³

Is there a good reason not to do this change?

Edit: Offtopic but do aur comments support some markup language to prevent it from stripping leading spaces?

¹ $ gpg --keyserver --recv-keys 3BD0ECA5925319AF89C25865B585609C5A2BE0C1

synapse84 commented on 2015-12-26 23:50

@MKody Added 'qt5-svg' as a dependency. Thanks.

MKody commented on 2015-12-25 20:48

Hi, "qt5-svg" should be added to the dependencies. It was missing for me and the make was failing without it.

synapse84 commented on 2015-12-21 08:16

@manuel_v Sorry for the delay. I've updated the package to include qt5-tools. Thanks

manuel_v commented on 2015-12-14 22:30

The build process tries to call lrelease-qt5 which is in qt5-tools. I guess that package should be added as build dependency.

synapse84 commented on 2015-12-08 09:22

@Kiwii Upgrading the package to Qt5 is something I've had on my todo list for a while. I've kept it held back on Qt4 for a few reasons, but the main thing stopping it now is data loss with the server list. During the Qt5 migration the search location for the mumble sqlite database file got changed from `QDesktopServices::DataLocation` (~/.local/share/data) to `QStandardPaths::DataLocation` (~/.local/share). This of course results in mumble not being able to load the existing client database.

I've posted an issue to the mumble github, but haven't gotten around to fixing it myself. Since compiling against Qt4 is starting to cause issues, I'll see about fixing it and upgrading this package to Qt5.

The latest snapshot (874 in my case) doesn't compile because of a copy assignment operation with a class that doesn't allow copying.

Also, Good catch on the PLUGIN_PATH, I'll update that soon.

*EDIT 2015-12-11*
I have submitted a pull request to mumble to migrate data from Qt4 to Qt5 builds. I'll upgrade both of my AUR mumble packages to Qt5 when my pull request is merged.

*EDIT 2015-12-13*
Mumble pull request was merged, updated to Qt5.

Kiwii commented on 2015-12-07 21:39

I also just noticed the pkgbuild defines PLUGIN_PATH=/usr/lib/mumble but in the package function it copies and into /usr/lib/mumble/plugins/ so mumble doesn't actually find them.

Kiwii commented on 2015-12-07 20:58

Any particular reason the pkgbuild doesn't use Qt5 yet? During build with Qt4 it gives the warning:

> Mumble client support for Qt 4 is deprecated and will be dropped
> completely in the future. We highly recommend switching to
> building Mumble with Qt 5. When built with Qt 4, Mumble might
> lack certain bug-fixes and capabilities available when built
> with Qt 5 already.

Also, the second latest snapshot 867_g197f13e builds fine with Qt5 when copying depends, makedepends and build lines from the mumble-git package into this pkgbuild. The latest snapshot 868_g21673bf wouldn't build at all for me, so I don't know what's up with that.