Age | Commit message (Collapse) | Author | Files | Lines |
|
telegraf 1.13.2 -> 1.13.3
|
|
|
|
In 87a19e9048773d5a363679617406ad148d36c3b8 I merged staging-next into master using the GitHub gui as intended.
In ac241fb7a570d6cf81d229ad22a8889602639160 I merged master into staging-next for the next staging cycle, however, I accidentally pushed it to master.
Thinking this may cause trouble, I reverted it in 0be87c79797a5fa384fbc356c74ed54f9f7829ea. This was however wrong, as it "removed" master.
This reverts commit 0be87c79797a5fa384fbc356c74ed54f9f7829ea.
|
|
I merged master into staging-next but accidentally pushed it to master.
This should get us back to 87a19e9048773d5a363679617406ad148d36c3b8.
This reverts commit ac241fb7a570d6cf81d229ad22a8889602639160, reversing
changes made to 76a439239eb310d9ad76d998b34d5d3bc0e37acb.
|
|
Staging next
|
|
The service needed lots of changes. A few smaller changes
are added into the PR, e.g. replacement for PR #72014.
See the commit messages for details.
|
|
https://gitlab.labs.nic.cz/knot/knot-resolver/tags/v5.0.1
|
|
https://github.com/documize/community/releases/tag/v3.7.0
|
|
|
|
|
|
The primary motivation of this change was to allow third-party modules
to be used with OpenResty, but it also results in a significant
reduction of code duplication.
|
|
The fork was merged back upstream but has yet to see a formal release.
|
|
https://github.com/tulir/mautrix-telegram/releases/tag/v0.7.1
|
|
dependency"
This reverts commit ce6b2419be6e16cc6b9096c99798a0d365b16486, which
was unnecessary (mailman worked just fine on its parent commit).
See #79222.
|
|
Please remove the explicit urllib3 dependency from this expression again once
https://github.com/NixOS/nixpkgs/issues/79222 is fixed.
|
|
|
|
mariadb: mytop add "clear" to PATH
|
|
nginxMainline: 1.17.3 -> 1.17.8
|
|
The following error was printed every second:
Can't exec "clear": Not a directory at /nix/store/.../bin/.mytop-wrapped line 110.
Use of uninitialized value $CLEAR in string at /nix/store/.../bin/.mytop-wrapped line 781.
Therefore the mytop output was repeatedly displayed instead of updating itself "in-place".
|
|
appdaemon: 3.0.5 -> 4.0.1
|
|
prometheus-xmpp-alerts: init at 0.4.2
|
|
Staging next
|
|
|
|
If Confluence should be connected to a MySQL database, the JDBC driver
is required.
Also switch to stdenvNoCC, because we don't really use cc.
|
|
endlessh: 1.0 -> 1.1
|
|
|
|
|
|
The merge 98640fd48212f8e6552517f667bba1901f5936d4 was done incorrectly.
|
|
hylafaxplus: 7.0.1 -> 7.0.2
|
|
|
|
We _do_ want minimum versions in our packages.
|
|
|
|
https://github.com/skeeto/endlessh/releases/tag/1.1
|
|
Minor incompatibilities due to moving to upstream defaults:
- capabilities are used instead of systemd.socket units
- the control socket moved:
/run/kresd/control -> /run/knot-resolver/control/1
- cacheDir moved and isn't configurable anymore
- different user+group names, without static IDs
Thanks Mic92 for multiple ideas.
|
|
Part of this is approximate revert of commit f0d2da43a7a449b5888.
|
|
|
|
|
|
|
|
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.
|
|
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.
|
|
|
|
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.
|
|
squid: 4.9 -> 4.10
|
|
The cqueues fix is in nixpkgs already, so it works now.
|
|
uftp: 4.10 -> 4.10.1
|
|
|
|
nixos/freeswitch: init
|
|
|
|
|
|
VictoriaMetrics: init at v1.32.5, add module, tests
|