| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Only packages I'm not able to maintain anymore as of today. Mostly
because I'm haven't been using them in a while.
|
|
I give up on that one.
|
|
See https://blog.prosody.im/prosody-0.12.0-released for more
informations.
We remove the various lua wrappers introduced by
6799a9184336146467eb71298d6b18ba7f45e0dc and
16d0b4a69f94adb523da8732b231b0d1738bd713. It seems like we don't need
them anymore. I'm not brave enough to dig into the Lua machinery to
see what resolved that. Sorry, you'll have to trust me on that one.
We should probably think about the migration from http_upload to
http_file_share for the NixOS module. It's not trivial, we need to
make sure we don't break the already uploaded URLs.
|
|
|
|
It was marked in commit 567c1a360f1f3b531847432e734e6f7e6eec41a5 by Michael Raskin on 2017-01-04 (commited on 2017-01-04)
|
|
Conflicts:
pkgs/development/python-modules/symengine/default.nix
|
|
This reverts commit 16d0b4a69f94adb523da8732b231b0d1738bd713.
|
|
|
|
|
|
This allows an override to add dependencies in the way that
`withExtraLibs` enabled in the past.
|
|
This seems to have been caused by #128503, because the values to be
prefixed contain special/wildcard characters.
|
|
This seems to be fallout from #136615
|
|
4369bebd9a32658ded22b580886587cdc577a29d removed the prosody-mysql
test. We forgot to remove the associated passthru test entry in the
prosody derivation.
|
|
This fixes CVE-2022-0217 [0].
[0] https://prosody.im/security/advisory_20220113/
|
|
Using unstable version because the release happened more than a year
ago, and since then several important fixes have been introduced,
including security ones.
|
|
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
|
|
|
|
fix CVE-2021-37601
annoucement: https://blog.prosody.im/prosody-0.11.10-released/
|
|
|
|
ejabberd: 20.12 -> 21.04
|
|
riak project is dead.
|
|
|
|
The prosody project has issues a new [release] and published security
[advisory] for CVE-2021-32918, CVE-2021-32920, CVE-2021-32921,
CVE-2021-32917 and CVE-2021-32919.
[advisory]: https://prosody.im/security/advisory_20210512/
[release]: https://blog.prosody.im/prosody-0.11.9-released/
|
|
|
|
|
|
It's a minor release, there's no major improvement/breaking change.
See https://blog.prosody.im/prosody-0.11.8-released/ for the full changelog.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- remove trailing whitespace
- use spaces for indentation
|
|
continuation of #109595
pkgconfig was aliased in 2018, however, it remained in
all-packages.nix due to its wide usage. This cleans
up the remaining references to pkgs.pkgsconfig and
moves the entry to aliases.nix.
python3Packages.pkgconfig remained unchanged because
it's the canonical name of the upstream package
on pypi.
|
|
|
|
Part of: https://github.com/NixOS/nixpkgs/issues/108938
meta = with stdenv.lib;
is a widely used pattern. We want to slowly remove
the `stdenv.lib` indirection and encourage people
to use `lib` directly. Thus let’s start with the meta
field.
This used a rewriting script to mostly automatically
replace all occurances of this pattern, and add the
`lib` argument to the package header if it doesn’t
exist yet.
The script in its current form is available at
https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
|
|
|
|
|
|
|
|
|
|
See https://blog.prosody.im/prosody-0.11.6-released/ for the release
notes.
|
|
nixos/biboumi: init
|
|
|
|
|
|
|
|
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
|
|
|
|
- https://prosody.im/doc/release/0.11.4
- https://prosody.im/doc/release/0.11.5
|
|
|
