| Commit message (Collapse) | Author | Age |
|\
| |
| | |
simp_le: 0.9.0 -> 0.16.0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Let's encrypt bumped ACME to V2. We need to update our nixos test to
be compatible with this new protocol version.
We decided to drop the Boulder ACME server in favor of the more
integration test friendly Pebble.
- overriding cacert not necessary
- this avoids rebuilding lots of packages needlessly
- nixos/tests/acme: use pebble's ca for client tests
- pebble always generates its own ca which has to be fetched
TODO: write proper commit msg :)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Updating:
- nixos module to use the new `account_reg.json` file.
- use nixpkgs pebble for integration tests.
Co-authored-by: Florian Klink <flokli@flokli.de>
Replace certbot-embedded pebble
|
|\ \ |
|
| | | |
|
| | |
| | |
| | | |
Fix typo in the ``users.users.<name>.packages`` option description.
|
| |\ \
| | | |
| | | | |
nixos/smokeping: replace smokeping.fcgi with a symlink
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes a regression from bb649d96b038ab2c567439987bc182f6797bae5a.
There were permission problems, when the preStart script tried to copy
the smokeping.fcgi file over the old file.
|
|\| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Just maching all network interfaces caused many breakages, see #18962
and #71106.
We already don't support the global networking.useDHCP,
networking.defaultGateway(6) options if networking.useNetworkd is
enabled, but direct users to configure the per-device
networking.interfaces.<name?>.… options.
|
|\| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds support for deploying to remote hosts without being root:
sudo nixos-rebuild --target-host non-root@host
Without this change, only root@host is able to deploy.
The idea is that if the local command is run with sudo, so should the
remote one, thus there is no need for adding any CLI options.
|
| |\ \ \
| | | | |
| | | | | |
nixos/lidarr: Add dataDir option
|
| | | |/
| | |/|
| | | |
| | | |
| | | | |
This will bring this module to a state to be consistent with how the
other forks (sonarr & radarr) works.
|
|\| | | |
|
| |\ \ \
| | | | |
| | | | | |
nixos/seahorse: Use seahorse's askpass by default
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
systemd-oneshot
|
| |\ \ \ \
| | |/ / /
| |/| | | |
gitlab: Get rid of most 'already initialized constant'-warnings
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
On start, unicorn, sidekiq and other parts running ruby code emits
quite a few warnings similar to
/var/gitlab/state/config/application.rb:202: warning: already initialized constant Gitlab::Application::LOOSE_EE_APP_ASSETS
/nix/store/ysb0lgbzxp7a9y4yl8d4f9wrrzy9kafc-gitlab-ee-12.3.5/share/gitlab/config/application.rb:202: warning: previous definition of LOOSE_EE_APP_ASSETS was here
/var/gitlab/state/lib/gitlab.rb:38: warning: already initialized constant Gitlab::COM_URL
/nix/store/ysb0lgbzxp7a9y4yl8d4f9wrrzy9kafc-gitlab-ee-12.3.5/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was here
This seems to be caused by the same ruby files being evaluated
multiple times due to the paths being different - sometimes they're
loaded using the direct path and sometimes through a symlink, due to
our split between config and package data. To fix this, we make sure
that the offending files in the state directory always reference the
store path, regardless of that being the real file or a symlink.
|
| |\ \ \ \
| | | | | |
| | | | | | |
collectd: plugins configuration, buildMinimalPackage
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
nixos/nix-daemon: don't refer to deprecated option aliases
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The `gc-` prefixed versions of these options have been
deprecated since Nix 2.0.
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos/httpd: remove deprecated extraSubservices option
|
| | | |_|_|/ /
| | |/| | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos/networkmanager: remove networking.networkmanager.dynamicHosts
|
| | | |/ / / /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This option was removed because allowing (multiple) regular users to
override host entries affecting the whole system opens up a huge attack
vector. There seem to be very rare cases where this might be useful.
Consider setting system-wide host entries using networking.hosts,
provide them via the DNS server in your network, or use
networking.networkmanager.appendNameservers to point your system to
another (local) nameserver to set those entries.
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos release notes: interfaces might get renamed
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Fixes #71086.
|
| |\ \ \ \ \ \ \
| | |/ / / / / /
| |/| | | | | | |
system-config-printer: 1.5.11 -> 1.5.12
|
| | | | | | | | |
|
| | | | | | | | |
|
| | |_|/ / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Even though the release obviously already happened, I think it might
still make sense to add a short note about the attributes not being
supported any longer (and going forward).
(cherry picked from commit 7163d3a9df35904d0c9acc9f643fd70ee3108539)
(cherry picked from commit a64b8c3c191af1317cfdc1ea4f4e5f881c4cf503)
|
|\| | | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Revert "nixos/gitlab: properly clear out initializers"
|
| | | |_|_|/ /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This reverts commit 2ee14c34ed1912ee31f1d4cc117b0ab25a3b20b1.
This caused the initializers directory to be cleaned out while gitlab
was running in some instances. We clean out the directory on the
preStart stage already, so ensuring existance and permissions should
suffice.
|
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 60aedadc59030477a9340af69866c728ac05d924.
Using tests from #71212 I am now unable to reproduce there being issues
with starting the default metacity flashback session without this.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
nixos/plymouth: do not order `plymouth-quit` after `display-manager`
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
GDM now specifies ordering between `plymouth-quit` and `display-manager`:
9be5321097c16
This causes an ordering cycle between GDM and plymouth-quit which can result in
systemd breaking GDM:
```
plymouth-quit.service: Job display-manager.service/start deleted to break
ordering cycle starting with plymouth-quit.service/start
```
Not sure how often this triggers, as I've run my system with plymouth and
9be5321097c16 without any issues. But I did catch a VM doing this.
NOTE: I also tried to remove the ordering in GDM to see if plymouth managed to
live longer, but it didn't seem to help. So I opted to stick as close to
upstream (upstream GDM specifies ordering, but plymouth does not).
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos/gnome3: fix gnome-flashback
|
| | | | | | | | |
|
| | | |_|_|_|/
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This session would fail to start because we didn't have it in systemd.packages
(as we've switched to systemd gnome-session).
Haven't tested custom sessions.
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
networkmanager-fortisslvpn: create the local state directory
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Otherwise connecting simply fails:
VPN connection: failed to connect: 'La création du fichier « /tmp/lib/NetworkManager-fortisslvpn/0507e3ef-f0e0-4153-af64-b3d9a025877c.config.XSB19Z » a échoué : No such file or directory'
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
nixos/make-iso9660-image: Fix storeContents documentation
|
| | | | | | | | | |
|
| | |/ / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
`packages` was renamed to `storeContents` in
668c146e33291e933ccfb19fd39fab9cd2b7900d, but this comment
describing its purpose was not updated to match.
|