| Git Clone URL: | https://aur.archlinux.org/mumble-git.git (read-only, click to copy) |
|---|---|
| Package Base: | mumble-git |
| Description: | An Open Source, low-latency, high quality voice chat software (git version) |
| Upstream URL: | https://www.mumble.info |
| Keywords: | audio communication multimedia network voip |
| Licenses: | BSD |
| Conflicts: | mumble |
| Provides: | mumble |
| Submitter: | None |
| Maintainer: | Radioactiveman |
| Last Packager: | Radioactiveman |
| Votes: | 45 |
| Popularity: | 0.000000 |
| First Submitted: | 2009-05-30 19:46 (UTC) |
| Last Updated: | 2026-03-04 19:26 (UTC) |
If you're running into this warning that later results in a build error:
/usr/bin/ld: warning: libfmt.so.12, needed by /usr/lib/libspdlog.so.1.17.0, may conflict with libfmt.so.9
Run pacman -Qs libfmt and notice that you have two libfmt versions installed. Remove libfmt9 (and packages that depend on it) and try building again.
@ChrisLane: Ah, I see. Changed accordingly now, thanks for the clarification and suggestion.
@Radioactiveman I am aware of the requirements around VCS package version bumps and I am not claiming that the version needs changing in order to simply increase the version number or build the latest version.
What I am claiming is that there is a bug in your pkgver() sed expression that leads to incorrect results when the upstream repo's most recent reachable tag has a v prefix (e.g. v1.6.870). In that case, git describe --long --tags produces something like v1.6.870-2-gc73aee6e4, and your sed turns it into v1.6.870.r2.gc73aee6e4 - retaining the leading v.
Pacman's vercmp demonstrates the relationship between two versions to determine whether the current package version is behind what is in AUR. The leading v causes incorrect ordering. The result is that after building from the latest commit, the installed version (v1.6.870.r2.gc73aee6e4) is considered older than the PKGBUILD's stored pkgver (1.4.0.development.snapshot.006.r2268.g5e86794bc), causing AUR helpers to perpetually flag the package as upgradeable.
You can verify this yourself with vercmp 'v1.6.870.r2.gc73aee6e4' '1.4.0.development.snapshot.006.r2268.g5e86794bc'.
This is also explicitly covered in the VCS package guidelines, which state that tag prefixes such as v should be stripped from the output of git describe. The fix is a one-token addition to the sed expression:
git describe --long --tags | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g'
@ChrisLane: A -git AUR package always builds the latest development version. There is no point in updating the PKGBUILD if only the package version changes.
@Radioactiveman I think the pkgver() needs updating. My package manager (yay) is detecting recent versioning as behind this package's stored version.
aur/mumble-git 1:v1.6.870.r2.gc73aee6e4-1 -> 1:1.4.0.development.snapshot.006.r2268.g5e86794bc-1
@IncredibleLaser: It seems 'pipewire' (or meanwhile 'libpipewire') is not required at all as make dependency.
Mumble uses the files from /mumble/3rdparty/pipewire/ for compilation and the build option is always enabled by default. The file /usr/lib/libpipewire-0.3.so from 'libpipewire' is loaded on runtime if it is installed.
So only an opt-dep is required. Mumble 1.5 from [community] does not list it though. You may file a bug report if this bothers you.
@IncredibleLaser: Thanks for the suggestion. PipeWire is now a make/opt dependency.
Mumble now has support for using pipewire directly (https://github.com/mumble-voip/mumble/pull/4970). Could you add pipewire as a dependency and enable the build option please (enabled by default though)? Thanks in advance!
@talos767: Done, thanks for the hint.
Pinned Comments
Radioactiveman commented on 2020-06-02 17:17 (UTC)
If you experience the problem below when updating packages, first remove
mumble-git, then update all packages includingprotobufand finally compilemumble-gitagain.