about summary refs log tree commit diff
path: root/pkgs/servers/xmpp
AgeCommit message (Collapse)AuthorFilesLines
2020-10-05prosody: 0.11.6 -> 0.11.7Andreas Rammhold1-4/+4
2020-09-11prosody: 0.11.5 -> 0.11.6Félix Baylac-Jacqué1-5/+5
See https://blog.prosody.im/prosody-0.11.6-released/ for the release notes.
2020-09-02Merge pull request #94917 from ju1m/biboumiFélix Baylac-Jacqué1-5/+2
nixos/biboumi: init
2020-09-02nixos/biboumi: initJulien Moutinho1-5/+2
2020-08-08prosody: update community modules to revision 2dcbc01c9931Julien Moutinho1-2/+2
2020-05-24prosody: add passthru testsFélix Baylac-Jacqué1-1/+8
2020-04-30nixos/prosody: make defaults comply with XEP-0423Félix Baylac-Jacqué1-3/+12
Setting up a XMPP chat server is a pretty deep rabbit whole to jump in when you're not familiar with this whole universe. Your experience with this environment will greatly depends on whether or not your server implements the right set of XEPs. To tackle this problem, the XMPP community came with the idea of creating a meta-XEP in charge of listing the desirable XEPs to comply with. This meta-XMP is issued every year under an new XEP number. The 2020 one being XEP-0423[1]. This prosody nixos module refactoring makes complying with XEP-0423 easier. All the necessary extensions are enabled by default. For some extensions (MUC and HTTP_UPLOAD), we need some input from the user and cannot provide a sensible default nixpkgs-wide. For those, we guide the user using a couple of assertions explaining the remaining manual steps to perform. We took advantage of this substential refactoring to refresh the associated nixos test. Changelog: - Update the prosody package to provide the necessary community modules in order to comply with XEP-0423. This is a tradeoff, as depending on their configuration, the user might end up not using them and wasting some disk space. That being said, adding those will allow the XEP-0423 users, which I expect to be the majority of users, to leverage a bit more the binary cache. - Add a muc submodule populated with the prosody muc defaults. - Add a http_upload submodule in charge of setting up a basic http server handling the user uploads. This submodule is in is spinning up an HTTP(s) server in charge of receiving and serving the user's attachments. - Advertise both the MUCs and the http_upload endpoints using mod disco. - Use the slixmpp library in place of the now defunct sleekxmpp for the prosody NixOS test. - Update the nixos test to setup and test the MUC and http upload features. - Add a couple of assertions triggered if the setup is not xep-0423 compliant. [1] https://xmpp.org/extensions/xep-0423.html
2020-04-10treewide: Per RFC45, remove all unquoted URLsMichael Reilly2-3/+3
2020-03-31prosody: 0.11.3 -> 0.11.5Martin Milata1-5/+5
- https://prosody.im/doc/release/0.11.4 - https://prosody.im/doc/release/0.11.5
2020-03-30ejabberd: 20.01 -> 20.03Izorkin1-4/+4
2020-01-26ejabberd: 19.09.1 -> 20.01R. RyanTM1-2/+2
2019-12-03ejabberd: 19.08 -> 19.09.1ajs1241-4/+4
2019-10-07prosody: 0.11.2 -> 0.11.3R. RyanTM1-2/+2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/prosody/versions
2019-09-04Merge branch 'master' into staging-nextVladimír Čunát2-2/+0
2019-09-02treewide: remove uses of doBuild and doConfigureMilan Pässler (work)2-2/+0
doBuild and doConfigure are not actually used by any builders, they were probably added by mistake and just confuse people.
2019-09-01prosody: Update for Lua search path handling changeAlexei Robyn1-4/+4
2019-08-24Merge branch 'master' into staging-nextVladimír Čunát1-3/+3
There ver very many conflicts, basically all due to name -> pname+version. Fortunately, almost everything was auto-resolved by kdiff3, and for now I just fixed up a couple evaluation problems, as verified by the tarball job. There might be some fallback to these conflicts, but I believe it should be minimal. Hydra nixpkgs: ?compare=1538299
2019-08-20ejabberd: 19.05 -> 19.08ajs1241-5/+5
2019-08-17treewide: name -> pnamevolth1-1/+2
2019-08-15treewide: name -> pname (easy cases) (#66585)volth6-15/+15
treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname
2019-06-14luaPackages: Replace all rockspec packages with generated onesAlexei Robyn1-17/+15
luaPackages replaced by generated ones: - bit32 - compat53 - cqueues - luacyrussasl -> cyrussasl (luarocks name) - luaexpat - luadbi -> luadbi front-end module + separate backend modules luadbi-{mysql,postgresql,sqlite3} - luafilesystem - luaossl - luasec - luasocket - luastdlib -> stdlib (luarocks name) - lrexlib -> lrexlib-pcre (we already have lrexlib-gnu and lrexlib-posix, lrexlib-pcre however appears to be the variant used in mudlet, which is the only current dep in nixpkgs) - luasqlite -> luasql-sqlite3 (luarocks name) - lfs -> luafilesytem (we literally had two manually written luafilesystem expressions, under different names) Changes and additions to overrides to generated luarocks packgaes, including: - busted: Install bash completions along with the zsh ones - cqueues: - Perform minor surgery on the rockspec to allow using a single rockspec to build for all supported Lua versions - Add a patch by @vcunat to work around a build issue - luuid: Wrote a tiny patch to allow for Lua 5.1/Luajit compatibility - General changes: - Sorted the packages - Attempted to make the formatting consistent - Preferenced `.override` instead of `.overrideAttrs` wherever possible Minor changes to other packages to adjust for the Lua package changes: - luakit expression simplified - prosody expression simplified; but users will now need to specify the luadbi backend module they intend to use in withExtraLibs - knot-resolver inputs correctd - mudlet inputs corrected (although this package was and should still be broken)
2019-06-02ejabberd: 19.02 -> 19.05Izorkin1-3/+3
2019-02-27ejabberd: 18.12.1 -> 19.02Izorkin1-3/+3
2019-02-26treewide: use runtimeShell instead of stdenv.shell whenever possibleJörg Thalheim2-4/+4
Whenever we create scripts that are installed to $out, we must use runtimeShell in order to get the shell that can be executed on the machine we create the package for. This is relevant for cross-compiling. The only use case for stdenv.shell are scripts that are executed as part of the build system. Usages in checkPhase are borderline however to decrease the likelyhood of people copying the wrong examples, I decided to use runtimeShell as well.
2019-02-04prosody: update communityModulesAndreas Rammhold1-3/+6
After the latest automatic updates of the prosody package the community modules were partially incompatible. The worst effect I suffered was a very high timeout (hours) on reconnects due to the stanza module throwing a runtime error on the server. We should probably try harder to keep them in sync.
2019-01-24Merge pull request #53796 from Izorkin/ejabberdSilvan Mosberger1-3/+3
ejabberd: 18.06 -> 18.12.1
2019-01-16prosody: 0.11.1 -> 0.11.2R. RyanTM1-2/+2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/prosody/versions
2019-01-11ejabberd: 18.06 -> 18.12.1Izorkin1-3/+3
2018-12-16prosody: 0.10.2 -> 0.11.1R. RyanTM1-2/+2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/prosody/versions
2018-11-15pyIRCt,pyMAILt: add licenseMarkus Kowalewski2-4/+6
2018-08-05ejabberd: 18.01 -> 18.06 (#44158)ajs1241-5/+6
ejabberd switched from imagemagick to eimp, which loads libpng, libjpeg and libwebp at runtime. These were therefore added as dependencies and the relevant binary was wrapped to be able to find them.
2018-07-27biboumi: 7.2 -> 8.3ajs1242-6/+6
also update catch from 1.5.6 to 2.2.1
2018-06-28treewide: http -> https sources (#42676)Silvan Mosberger1-1/+1
* treewide: http -> https sources This updates the source urls of all top-level packages from http to https where possible. * buildtorrent: fix url and tab -> spaces
2018-06-03prosody: 0.10.1 -> 0.10.2Andreas Rammhold1-2/+2
Fixes CVE-2018-10847 [1] and a bunch of minor things [2]. [1] https://prosody.im/security/advisory_20180531/ [2] http://blog.prosody.im/prosody-0-10-2-security-release/
2018-05-17prosody: 0.10.0 -> 0.10.1 (#40645)R. RyanTM1-2/+2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/prosody/versions. These checks were done: - built on NixOS - /nix/store/9vcfnh0ghw9qmljbmpb52l5xwq8b8k4i-prosody-0.10.1/bin/prosody passed the binary check. - Warning: no invocation of /nix/store/9vcfnh0ghw9qmljbmpb52l5xwq8b8k4i-prosody-0.10.1/bin/prosodyctl had a zero exit code or showed the expected version - /nix/store/9vcfnh0ghw9qmljbmpb52l5xwq8b8k4i-prosody-0.10.1/bin/.prosody-wrapped passed the binary check. - Warning: no invocation of /nix/store/9vcfnh0ghw9qmljbmpb52l5xwq8b8k4i-prosody-0.10.1/bin/.prosodyctl-wrapped had a zero exit code or showed the expected version - 2 of 4 passed binary check by having a zero exit code. - 0 of 4 passed binary check by having the new version present in output. - found 0.10.1 with grep in /nix/store/9vcfnh0ghw9qmljbmpb52l5xwq8b8k4i-prosody-0.10.1 - directory tree listing: https://gist.github.com/e1e8caae1a498d8e07f1c35d990846d3 - du listing: https://gist.github.com/9b3a9c7a8711da781e548e894e848cdc
2018-04-30treewide: http to httpsRyan Mulligan1-2/+2
2018-03-26unix-tools: introduce unix-tools.nixMatthew Bauer2-5/+5
unix-tools.nix has a collection of tools that are commonly installed by default in Unix derivatives. This is intended to provide compatibility between macOS and Linux users. Three Linux-only derivations are provided for compatbility: - procps - utillinux - nettools More tools are also provided. Also: treewide: use unixtools Non-comprehensive replace of Linux-only procps and util-linux with 'unixtools'.
2018-03-22Merge pull request #32960 from florianjacob/prosody-0.10Robin Gloster1-11/+12
Prosody 0.10.0
2018-03-22prosody: improve module handlingRobin Gloster1-3/+7
2018-03-12prosody: update community modulesFlorian Jacob1-2/+2
2018-03-12prosody: 0.9.12 -> 0.10.0Florian Jacob1-6/+3
updating config options, removing luazlib as mod_compression was removed for security reasons.
2018-03-07biboumi: 6.1 -> 7.2Ryan Mulligan1-2/+2
Semi-automatic update. These checks were done: - built on NixOS - ran `/nix/store/ng1gidmaivbb5ngd4awq6wgraa55yjd5-biboumi-7.2/bin/biboumi --help` got 0 exit code - found 7.2 with grep in /nix/store/ng1gidmaivbb5ngd4awq6wgraa55yjd5-biboumi-7.2 - found 7.2 in filename of file in /nix/store/ng1gidmaivbb5ngd4awq6wgraa55yjd5-biboumi-7.2
2018-02-25ejabberd: 17.07 -> 18.01Nikolay Amiantov1-9/+9
2018-01-10treewide: Fix deps in a few other fixed output derivationsJohn Ericson1-1/+1
2017-11-06prosody: remove flosse from the list of maintainersMarkus Kohlhase1-1/+1
2017-11-01prosody.communityModules: 590ac12b7671 -> 9a3e51f348feSatoshi Shishiku1-2/+2
2017-11-01prosody: support for DBI, extra community modules and extra Lua librariesSatoshi Shishiku1-10/+18
2017-10-20biboumi: init at 6.1 (#30193)Frank Doepper2-0/+74
* biboumi: init at 6.1 TODO: integrate config in NixOS * biboumi: remove external buildtime dep - fetch catch.hpp in a reproducible way - add maintainer - enable tests - remove git dep - enable parallel building - add pandoc dep for man page - nitpicks * biboumi: refine substitutions - only CMakeLists.txt has to be patched regarding /etc/biboumi - substitute /bin/kill in systemd service file - prepare for configuring policy_directory in a future cfg file
2017-07-27ejabberd: 17.01 -> 17.07Nikolay Amiantov1-3/+3
2017-04-30/bin/sh -> ${stdenv.shell}rht2-2/+2