| Age | Commit message (Collapse) | Author |
|---|
|
nixos/limesurvey: drop default encryption key and nonce
|
|
hound: convert to use freeform type
|
|
It was wrong to use StateDirectory to keep the scion-control and
scion-router runtime databases on disk for the next run. I observed that
doing this means a reboot, or power outage can corrupt the temporary
runtime databases for the next service start, leading scion ping and
other functionality to stop working permanently, since those files are
not managed in an atomic manner by the golang code.
|
|
nixos/healthchecks: add settingsFile option
|
|
python311Packages.mozilla-django-oidc: init at 4.0.1; peering-manager: add oidc support
|
|
nixos/xfce: Enable colord by default
|
|
Goes with #323010.
|
|
Co-authored-by: Thomas Gerbet <thomas@gerbet.me>
|
|
|
|
|
|
|
|
|
|
lib: deprecate mkPackageOptionMD
|
|
nixos/quickwit: fix service ReadWritePaths
|
|
nextcloud: drop 27, 28.0.6 -> 28.0.7, 29.0.2 -> 29.0.3
|
|
services/localtimed: Allow configuring packages
|
|
|
|
|
|
|
|
|
|
nixos/ollama: add `loadModels` config option
|
|
Allows users to download model files upon service startup,
instead of at the first use of the model, improving percieved startup latency.
|
|
nixos/gdm: allow logging in via fingerprint
|
|
nixos/kmscon: use upstream service file
|
|
Co-authored-by: Jenny <me@netali.de>
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
|
|
nixos/tomcat: add 'port' option
|
|
treewide: fix mkEnableOption usage
|
|
nixos/services.kubernetes.kubelet: handle non-lower case chars in hostname
|
|
nixos/vaultwarden: backup all rsa_keys
|
|
wg-access-server: init at 0.12.1
|
|
nixos/zerotierone: fix default value for localConf
|
|
Support for *runner registration tokens* is deprecated since GitLab
16.0, has been disabled by default in GitLab 17.0 and will be removed in
GitLab 18.0, as outlined in the [GitLab documentation].
It is possible to [re-enable support for runner registration tokens]
until GitLab 18.0, to prevent the registration workflow from
breaking.
*Runner authentication tokens*, the replacement for registration tokens,
have been available since GitLab 16.0 and are expected to be defined in
the `CI_SERVER_TOKEN` environment variable, instead of the previous
`REGISTRATION_TOKEN` variable.
This commit adds a new option
`services.gitlab-runner.services.<name>.authenticationTokenConfigFile`.
Defining such option next to
`services.gitlab-runner.services.<name>.registrationConfigFile` brings
the following benefits:
- A warning message can be emitted to notify module users about the
upcoming breaking change with GitLab 17.0, where *runner registration
tokens* will be disabled by default, potentially disrupting
operations.
- Some configuration options are no longer supported with *runner
authentication tokens* since they will be defined when creating a new
token in the GitLab UI instead. New warning messages can be emitted to
notify users to remove the affected options from their configuration.
- Once support for *registration tokens* has been removed in GitLab 18,
we can remove
`services.gitlab-runner.services.<name>.registrationConfigFile` as
well and make module users configure an *authentication token*
instead.
This commit changes the option type of
`services.gitlab-runner.services.<name>.registrationConfigFile` to
`with lib.types; nullOr str` to allow configuring an authentication
token in
`services.gitlab-runner.services.<name>.authenticationTokenConfigFile`
instead.
A new assertion will make sure that
`services.gitlab-runner.services.<name>.registrationConfigFile` and
`services.gitlab-runner.services.<name>.authenticationTokenConfigFile`
are mutually exclusive. Setting both at the same time would not make
much sense in this case.
[GitLab documentation]: https://docs.gitlab.com/17.0/ee/ci/runners/new_creation_workflow.html#estimated-time-frame-for-planned-changes
[re-enable support for runner registration tokens]: https://docs.gitlab.com/17.0/ee/ci/runners/new_creation_workflow.html#prevent-your-runner-registration-workflow-from-breaking
|
|
|
|
treewide: remove jonringer as package maintainer and code owner
|
|
Cinnamon updates 2024-06-24
|
|
Version will be EOL by the end of 2024-06.
|
|
|
|
|
|
Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
|
|
deepin desktop environment: update
|
|
|
|
|
|
|
|
My reasons following Mint are:
1. Geary signed https://stopthemingmy.app, per request we shouldn't pre-ship it under a themed desktop environment.
See also https://github.com/linuxmint/mint-y-icons/commit/b7937b45090f8b15f7718bd51ef7bee1eb0e263c
2. Hexchat is still gtk2 and is not maintained anymore, Mint encourages switching to Matrix instead.
See also https://blog.linuxmint.com/?p=4675 ("Joining the Matrix")
|
|
|
|
stalwart-mail: include pre-defined spam-filter
|
|
nixos: sourcehut: fix some binary paths
|
|
nixos/prometheus: Revamp tests
|
|
kkoniuszy/add-home-assistant-custom-components-spook
home-assistant-custom-components.spook: init at 3.0.1
|
|
frenck/spook includes a second manifest for an integration. The current
copyCustomComponents script assumed that only one component directory
will be found, which in this case resulted in a malformed symlink
destination:
lrwxrwxrwx 1 hass hass 224 Jun 23 17:23 spook -> '/nix/store/r41ics22zs578avzqf7x86plcgn2q71h-python3.12-frenck-spook-v3.0.1/custom_components/spook/integrations/spook_inverse'$'\n''/nix/store/r41ics22zs578avzqf7x86plcgn2q71h-python3.12-frenck-spook-v3.0.1/custom_components/spook'
|
