| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
|
|
| |
The previously propagated build inputs are optional, and so are
included in checkInputs so the tests can run, but not propagated so
they aren't included if unneeded.
|
| | |
|
| |
|
|
|
| |
This is propagated by Hyperkitty, but it should really only be a
checkInput there.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit a1eacb900e1b705678b2c199cb97baafc9b77f86.
Adding dev outputs to python packages means they can't be included in
a Python environment created with python3.withPackages, because
makePythonPath will include the dev output, which is empty apart from
nix-support, rather than the out output, which contains all the Python
code.
|
| | |
|
| |
|
|
|
|
| |
This patch has not been necessary since
5425867bfa3e4ba83a3d67aa50b811b5f70d6fe5, and has in fact broken the
build since then.
|
| | |
|
| | |
|
| |
|
|
| |
This package is a dependency of GNU Mailman 3.3.x.
|
| |
|
|
|
|
| |
This fixes some two-digit year rounding bugs that started triggering
because 2020 is closer to 2070 than 1970. Apparently two digits years
are still a thing.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
They modified the release tarballs to fix a bug with the dictionary
generation. From their website:
> Re-release of all dictionary exports: Due to a bug in the IPA
> generation, some dictionaries had incorrect IPA transcriptions for
> headwords. This has been fixed for all dictionaries now.
I sent them mail requesting that they don't do this again without
calling it a new release:
https://www.freelists.org/post/freedict/Hash-changes-for-dictionary-releases
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, some files were copied into the Nixpkgs tree, which meant
we wouldn't easily be able to update them, and was also just messy.
The reason it was done that way before was so that a few NixOS
options could be substituted in. Some problems with doing it this way
were that the _package_ changed depending on the values of the
settings, which is pretty strange, and also that it only allowed those
few settings to be set.
In the new model, mailman-web is a usable package without needing to
override, and I've implemented the NixOS options in a much more
flexible way. NixOS' mailman-web config file first reads the
mailman-web settings to use as defaults, but then it loads another
configuration file generated from the new services.mailman.webSettings
option, so _any_ mailman-web Django setting can be customised by the
user, rather than just the three that were supported before. I've
kept the old options, but there might not really be any good reason to
keep them.
It also meant that one hard-coded SECRET_KEY was included in the Nix
store, AND SHARED BETWEEN ALL NIXOS USERS! As part of this change,
the secret key will now be generated along with the Hyperkitty API key
the first time the service is run, and it will never be stored in the
Nix store.
|
| |
|
|
|
| |
Also, mailman looks in /etc/mailman.cfg by default, so setting
MAILMAN_CONFIG_FILE isn't required either.
|
| |
|
|
|
|
|
| |
We already had python3Packages.mailman, but that's only really usable
as a library. The only other option was to create a whole Python
environment, which was undesirable to install as a system-wide
package.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
The Net::CIDR::Lite package was missing.
|
| |
|
|
|
|
| |
Using a custom path in the Nix store meant that users of the module
couldn't add their own config files, which is a desirable feature. I
don't think avoiding /etc buys us anything.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes
nix-shell -p 'ruby.withPackages (const [])' ruby.devdoc
which otherwise wouldn't find documentation, unlike
nix-shell -p ruby ruby.devdoc
which would, because ruby has setup hooks to accomodate for this, that
were being masked by the withPackages wrapper.
|
| |
|
|
|
|
| |
I noticed while strace-ing that Git was trying to open
/etc//gitconfig. Not a big deal, but it is definitely more correct
without the trailing slash.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces all Mailman secrets with ones that are generated the
first time the service is run. This replaces the hyperkittyApiKey
option, which would lead to a secret in the world-readable store.
Even worse were the secrets hard-coded into mailman-web, which are not
just world-readable, but identical for all users!
services.mailman.hyperkittyApiKey has been removed, and so can no
longer be used to determine whether to enable Hyperkitty. In its
place, there is a new option, services.mailman.hyperkitty.enable. For
consistency, services.mailman.hyperkittyBaseUrl has been renamed to
services.mailman.hyperkitty.baseUrl.
|
| |
|
|
|
| |
The actual upstream "mailman" name just refers to this, so we should
use the Nixpkgs convention of default.nix.
|
| |
|
|
| |
This isn't referenced anywhere, so it's just dead code.
|
| | |
|
| | |
|
| |
|
|
| |
Graham confirmed to me that this was probably a typo.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|