Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2/bin/liferea -h` got 0 exit code
- ran `/nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2/bin/liferea --help` got 0 exit code
- ran `/nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2/bin/liferea -v` and found version 1.12.2
- ran `/nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2/bin/liferea --version` and found version 1.12.2
- ran `/nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2/bin/.liferea-wrapped -h` got 0 exit code
- ran `/nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2/bin/.liferea-wrapped --help` got 0 exit code
- ran `/nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2/bin/.liferea-wrapped -v` and found version 1.12.2
- ran `/nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2/bin/.liferea-wrapped --version` and found version 1.12.2
- found 1.12.2 with grep in /nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2
- found 1.12.2 in filename of file in /nix/store/wjf8q5k0hh2vcjw65v2skcn54pq3vb0q-liferea-1.12.2
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 1.0.3 with grep in /nix/store/5n2jwjv8x9a1sic8ia32vncq5i5smd0f-inboxer-1.0.3
- found 1.0.3 in filename of file in /nix/store/5n2jwjv8x9a1sic8ia32vncq5i5smd0f-inboxer-1.0.3
This is necessary because the standard library which is distributed with
lumail (the lumail core configuration so to speak) is written for lua5.1
apparently.
The website states 5.1 or 5.2 or 5.3, but 5.2 fails because "loadstring"
was deprecated in lua 5.2.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Includes:
* Package gets a flag to use the debug build
* install phase installs all lua scripts from the package and makes
lumail find them
* global configuration which is shipped with the package can be
overridden, if desired
* parallel building enabled
Those version specs only exist to keep compat with python 3.3 which we
are not using anyway.
(cherry picked from commit 560b2bce6ce84628f97e242a3015201378a90eef)
Semi-automatic update. These checks were done:
- built on NixOS
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk -h` got 0 exit code
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk --help` got 0 exit code
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk help` got 0 exit code
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk -v` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk --version` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk version` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk -h` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk --help` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk help` and found version 3.7.7
- found 3.7.7 with grep in /nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7
- found 3.7.7 in filename of file in /nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7
Semi-automatic update. These checks were done:
- built on NixOS
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/.syncplay-wrapped -h` got 0 exit code
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/.syncplay-wrapped --help` got 0 exit code
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/.syncplay-wrapped -v` and found version 1.5.2
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/.syncplay-wrapped --version` and found version 1.5.2
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/syncplay -h` got 0 exit code
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/syncplay --help` got 0 exit code
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/syncplay -v` and found version 1.5.2
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/syncplay --version` and found version 1.5.2
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/.syncplay-server-wrapped -h` got 0 exit code
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/.syncplay-server-wrapped --help` got 0 exit code
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/syncplay-server -h` got 0 exit code
- ran `/nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2/bin/syncplay-server --help` got 0 exit code
- found 1.5.2 with grep in /nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2
- found 1.5.2 in filename of file in /nix/store/s02mpddajsz1q5h5r8mvmyd31np2ha26-syncplay-1.5.2
This is optional (`libcardiacarrest` has a workaround for this bug
because there's `firefox-bin` that I can't fix), but with this applied things
are a bit smoother.
Semi-automatic update. These checks were done:
- built on NixOS
- ran `/nix/store/vfr6b50xzj4rj0xhl83vfqqq127lx79s-pig-0.16.0/bin/pig --help` got 0 exit code
- ran `/nix/store/vfr6b50xzj4rj0xhl83vfqqq127lx79s-pig-0.16.0/bin/pig --version` and found version 0.16.0
- ran `/nix/store/vfr6b50xzj4rj0xhl83vfqqq127lx79s-pig-0.16.0/bin/pig -h` and found version 0.16.0
- found 0.16.0 with grep in /nix/store/vfr6b50xzj4rj0xhl83vfqqq127lx79s-pig-0.16.0
Semi-automatic update. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 27.8.0 with grep in /nix/store/vqardwl9d7s3wdgapj4ybzrgpw5w3671-palemoon-27.8.0
Semi-automatic update. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 0.6.0 with grep in /nix/store/20rzgnqnxfx21j49wr48pd4p9wb0ai5z-cni-0.6.0
- found 0.6.0 in filename of file in /nix/store/20rzgnqnxfx21j49wr48pd4p9wb0ai5z-cni-0.6.0
Semi-automatic update. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 0.5.8 with grep in /nix/store/v1xv4aj5wq1mw5mdml2hwh4qd5bfdcim-baresip-0.5.8
- found 0.5.8 in filename of file in /nix/store/v1xv4aj5wq1mw5mdml2hwh4qd5bfdcim-baresip-0.5.8
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/651sa1wikygbqqvimg3a609n37isc78w-tcpkali-1.1.1/bin/tcpkali --version` and found version 1.1.1
- found 1.1.1 with grep in /nix/store/651sa1wikygbqqvimg3a609n37isc78w-tcpkali-1.1.1
- found 1.1.1 in filename of file in /nix/store/651sa1wikygbqqvimg3a609n37isc78w-tcpkali-1.1.1
cc "@ethercrow"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua -h` got 0 exit code
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua --help` got 0 exit code
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua help` got 0 exit code
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua -V` and found version 2.7.2
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua -v` and found version 2.7.2
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua --version` and found version 2.7.2
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua version` and found version 2.7.2
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua -h` and found version 2.7.2
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua --help` and found version 2.7.2
- ran `/nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2/bin/pjsua help` and found version 2.7.2
- found 2.7.2 with grep in /nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2
- found 2.7.2 in filename of file in /nix/store/3wqj8kyahgi1r25wp8vfhhsg0m1mzpkx-pjsip-2.7.2
cc "@viric @olynch"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/qan26dfxzzbh27cd91hcvad69ls7xnhw-snort-2.9.11.1/bin/snort -V` and found version 2.9.11.1
- ran `/nix/store/qan26dfxzzbh27cd91hcvad69ls7xnhw-snort-2.9.11.1/bin/snort --version` and found version 2.9.11.1
- ran `/nix/store/qan26dfxzzbh27cd91hcvad69ls7xnhw-snort-2.9.11.1/bin/u2spewfoo help` got 0 exit code
- ran `/nix/store/qan26dfxzzbh27cd91hcvad69ls7xnhw-snort-2.9.11.1/bin/.snort-wrapped -V` and found version 2.9.11.1
- ran `/nix/store/qan26dfxzzbh27cd91hcvad69ls7xnhw-snort-2.9.11.1/bin/.snort-wrapped --version` and found version 2.9.11.1
- found 2.9.11.1 with grep in /nix/store/qan26dfxzzbh27cd91hcvad69ls7xnhw-snort-2.9.11.1
- found 2.9.11.1 in filename of file in /nix/store/qan26dfxzzbh27cd91hcvad69ls7xnhw-snort-2.9.11.1
cc "@aycanirican"
Semi-automatic update. These checks were performed:
- built on NixOS
- found 6.1.5 with grep in /nix/store/7y211zn1irykpjfgf8n38vbhh57xgaq2-seafile-client-6.1.5
- found 6.1.5 in filename of file in /nix/store/7y211zn1irykpjfgf8n38vbhh57xgaq2-seafile-client-6.1.5
cc "@calrama"
Semi-automatic update. These checks were performed:
- built on NixOS
- found 1.2.235 with grep in /nix/store/9z3lbwjmcvgxpicxnkqsqyn2bmkyqvsw-psi-plus-1.2.235
cc "@orivej"
Semi-automatic update. These checks were performed:
- built on NixOS
- found 0.8 with grep in /nix/store/di49z3ic9sk7mrg6rhf0c67qk8pda3kg-pidgin-xmpp-receipts-0.8
- found 0.8 in filename of file in /nix/store/di49z3ic9sk7mrg6rhf0c67qk8pda3kg-pidgin-xmpp-receipts-0.8
cc "@orivej"
Semi-automatic update. These checks were performed:
- built on NixOS
- found 0.9 with grep in /nix/store/k19kx1lh4211srqcgnrwq7yfkvqclf9m-ostinato-0.9
- found 0.9 in filename of file in /nix/store/k19kx1lh4211srqcgnrwq7yfkvqclf9m-ostinato-0.9
cc "@rick68"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/glm49diswdg3qi1vxpffqmdrzmkykvqj-nomad-0.7.1-bin/bin/nomad -h` got 0 exit code
- ran `/nix/store/glm49diswdg3qi1vxpffqmdrzmkykvqj-nomad-0.7.1-bin/bin/nomad --help` got 0 exit code
- ran `/nix/store/glm49diswdg3qi1vxpffqmdrzmkykvqj-nomad-0.7.1-bin/bin/nomad -v` and found version 0.7.1
- ran `/nix/store/glm49diswdg3qi1vxpffqmdrzmkykvqj-nomad-0.7.1-bin/bin/nomad --version` and found version 0.7.1
- ran `/nix/store/glm49diswdg3qi1vxpffqmdrzmkykvqj-nomad-0.7.1-bin/bin/nomad version` and found version 0.7.1
- found 0.7.1 with grep in /nix/store/glm49diswdg3qi1vxpffqmdrzmkykvqj-nomad-0.7.1-bin
- found 0.7.1 in filename of file in /nix/store/glm49diswdg3qi1vxpffqmdrzmkykvqj-nomad-0.7.1-bin
cc "@rushmorem @pradeepchhetri @ehmry @lethalman"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/3f76mczmag2wnkww6la0hcdnf82jly92-lsyncd-2.2.2/bin/lsyncd --version` and found version 2.2.2
- found 2.2.2 with grep in /nix/store/3f76mczmag2wnkww6la0hcdnf82jly92-lsyncd-2.2.2
- found 2.2.2 in filename of file in /nix/store/3f76mczmag2wnkww6la0hcdnf82jly92-lsyncd-2.2.2
cc "@bobvanderlinden"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/hclwimgs404fz9k2lrx35xcxa16bgb9x-kops-1.8.1-bin/bin/kops -h` got 0 exit code
- ran `/nix/store/hclwimgs404fz9k2lrx35xcxa16bgb9x-kops-1.8.1-bin/bin/kops --help` got 0 exit code
- ran `/nix/store/hclwimgs404fz9k2lrx35xcxa16bgb9x-kops-1.8.1-bin/bin/kops help` got 0 exit code
- ran `/nix/store/hclwimgs404fz9k2lrx35xcxa16bgb9x-kops-1.8.1-bin/bin/kops version` and found version 1.8.1
- found 1.8.1 with grep in /nix/store/hclwimgs404fz9k2lrx35xcxa16bgb9x-kops-1.8.1-bin
- found 1.8.1 in filename of file in /nix/store/hclwimgs404fz9k2lrx35xcxa16bgb9x-kops-1.8.1-bin
cc "@offline @zimbatm @ehmry @lethalman"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/lbk05ajkfj5za1zgz0haz57sfipiv38y-kompose-1.9.0-bin/bin/kompose -h` got 0 exit code
- ran `/nix/store/lbk05ajkfj5za1zgz0haz57sfipiv38y-kompose-1.9.0-bin/bin/kompose --help` got 0 exit code
- ran `/nix/store/lbk05ajkfj5za1zgz0haz57sfipiv38y-kompose-1.9.0-bin/bin/kompose help` got 0 exit code
- ran `/nix/store/lbk05ajkfj5za1zgz0haz57sfipiv38y-kompose-1.9.0-bin/bin/kompose version` and found version 1.9.0
- found 1.9.0 with grep in /nix/store/lbk05ajkfj5za1zgz0haz57sfipiv38y-kompose-1.9.0-bin
- found 1.9.0 in filename of file in /nix/store/lbk05ajkfj5za1zgz0haz57sfipiv38y-kompose-1.9.0-bin
cc "@thpham @ehmry @lethalman"
Semi-automatic update. These checks were performed:
- built on NixOS
- found 1.0.2 with grep in /nix/store/r58bhh86hprpzb4fh5xk0snaqgbqa8vy-inboxer-1.0.2
- found 1.0.2 in filename of file in /nix/store/r58bhh86hprpzb4fh5xk0snaqgbqa8vy-inboxer-1.0.2
cc "@mgttlinger"
Semi-automatic update. These checks were performed:
- built on NixOS
- found 1.8 with grep in /nix/store/4ml6hcsv9k8gshqc461w2vvfpq3j9lh4-ii-1.8
- found 1.8 in filename of file in /nix/store/4ml6hcsv9k8gshqc461w2vvfpq3j9lh4-ii-1.8
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/k309zjlgh7pn9h1gpzf5rrmnxzmfifil-daq-2.2.2/bin/daq-modules-config -h` got 0 exit code
- ran `/nix/store/k309zjlgh7pn9h1gpzf5rrmnxzmfifil-daq-2.2.2/bin/daq-modules-config --help` got 0 exit code
- ran `/nix/store/k309zjlgh7pn9h1gpzf5rrmnxzmfifil-daq-2.2.2/bin/daq-modules-config help` got 0 exit code
- found 2.2.2 with grep in /nix/store/k309zjlgh7pn9h1gpzf5rrmnxzmfifil-daq-2.2.2
- found 2.2.2 in filename of file in /nix/store/k309zjlgh7pn9h1gpzf5rrmnxzmfifil-daq-2.2.2
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/l58hq30xhskjp4cvqpjjdxzjqi9q21wi-bro-2.5.3/bin/bro-config --version` and found version 2.5.3
- ran `/nix/store/l58hq30xhskjp4cvqpjjdxzjqi9q21wi-bro-2.5.3/bin/binpac -V` and found version 2.5.3
- ran `/nix/store/l58hq30xhskjp4cvqpjjdxzjqi9q21wi-bro-2.5.3/bin/binpac -v` and found version 2.5.3
- ran `/nix/store/l58hq30xhskjp4cvqpjjdxzjqi9q21wi-bro-2.5.3/bin/binpac --version` and found version 2.5.3
- ran `/nix/store/l58hq30xhskjp4cvqpjjdxzjqi9q21wi-bro-2.5.3/bin/bro -v` and found version 2.5.3
- ran `/nix/store/l58hq30xhskjp4cvqpjjdxzjqi9q21wi-bro-2.5.3/bin/bro --version` and found version 2.5.3
- found 2.5.3 with grep in /nix/store/l58hq30xhskjp4cvqpjjdxzjqi9q21wi-bro-2.5.3
- found 2.5.3 in filename of file in /nix/store/l58hq30xhskjp4cvqpjjdxzjqi9q21wi-bro-2.5.3
Missing quotes of $UNAME_CMD in the firehol bash script
result in an error if the path to uname contains a dash,
as in /nix/store/...-coreutils-.../bin/uname.
Might be considered an upstream bug but only appears
in this special case, unlikely to occur in other distros.
- Fix GOPATH checks
- Install manpages
- Also build and install discovery and relay servers + cli
- Make the build more pure by explicitly setting the build username/host
* remove EOL ruby versions for security and maintenance reasons.
* only expose ruby_MAJOR_MINOR to the top-level. we don't provide
guarantees for the TINY version.
* mark all related packages as broken
* switch the default ruby version from 2.3.x to 2.4.x
The patches do no longer apply on-top of the pjsip version we provice.
One of the maintainers (@Radvendii @olynch) should have a look what can
be done about this.
The build has been failing since 2017-07-31…
This version bump contains the following fixes:
v8:
- Avoid a segmentation fault when notmuch_message_get_header() returns NULL. (Patch by Víctor M. Jáquez <vjaquez@igalia.com>).
v9:
- Do not use the deprecated notmuch_query_count_messages_st function when using Notmuch 0.25. (Patch by Adam Ruzicka <a.ruzicka@outlook.com>.)
We already had this patch in our tree.
- Fix crash in when running queries and the program is build with Notmuch 0.25. (Patch by Joshua Krusell <joshua.krusell@v-dem.net>).
- Fix conditional compilation when using Notmuch 0.25. (Patch by David Bremner <bremner@debian.org>).
Adaptation of #23058 by @spinus to 1.0.0rc1. See #23058 and #28111 for discussion.
This patch keeps the warnings. But I think it is useful to have a sanely working
version in nixpkgs, even if it is still considered insecure, just to follow the
upstream development by actually running it instead of reading the log.
Upstream changes:
* Improve Zeroconf behavior
* Fix showing normal message event
* remove usage of OpenSSL.rand
* a few minor bugfixes
The really important part here is the third point about OpenSSL.rand,
because the rand attribute no longer exists in pyopenssl and thus Gajim
doesn't even start.
Also the fix-tests.patch has been fixed upstream as well, so we don't
need it anymore.
Another change in 0.16.9 that's not included in the changelog is that
there is a test_nogui target, which is also run by the CI upstream is
using, so let's use that and remove xvfb_run.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @7c6f434c, @Mic92
Since firefox 58.0.1 the google api key is now stored at an absolute
path ($TMPDIR/ga). Since variable expansion in `configureFlags` does not
really work (as expected) the build started failing when using the
legacy firefox build system. With the newer `./mach` based builds
firefox reads the configure flags from `.mozconfig` instead.
This commit moves the `with-google-api-keyfile=` setting into the
`preConfigure` phase where we can properly expand `$TMPDIR` into
whatever the path is.
As stated by Sylvestre Ledru (@sylvestre) on Nov 22, 2017 at
https://github.com/NixOS/nixpkgs/issues/31843#issuecomment-346372756 we
have permission to use the official firefox branding.
Fur purposes of documentation the statement of @sylvestre:
> As the person who did part of the work described in the LWN article
> and release manager working for Mozilla, I can confirm the statement
> that I made in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815006
>
> @garbas shared with me the list of patches applied for the Nix package.
> As they are just for portability and tiny modifications, they don't
> alter the experience of the product. In parallel, Rok also shared the
> build options. They seem good (even if I cannot judge the quality of the
> packaging of the underlying dependencies like sqlite, png, etc).
> Therefor, as long as you keep the patch queue sane and you don't alter
> the experience of Firefox users, you won't have any issues using the
> official branding.
This is already tracked in upstream issue mumble-voip/mumble#3281 and a
fix has been merged in mumble-voip/mumble@caa187373e.
The patch I'm adding here is using the merged commit
mumble-voip/mumble@ea861fe867 and I've
only added it for the stable release because the patch is already
included in the git version.
@pbogdan also had a similar commit to this
(pbogdan/nixpkgs@8029edea29), but the
patch was applied to both stable and git and thus the git version would
have been broken.
Tested by building mumble and mumble_git and running the mumble NixOS VM
test.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @viric, @jgeerds, @abbradar
Fixes: #33655
