| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
| |
Per reviewer comment (thanks!).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
environment.sessionVariables cannot refer to the values of env vars,
and as a result this has caused problems in a variety of scenarios.
One use for these is that they're injected into /etc/profile,
elewhere these are used to populate an 'envfile' for pam
(`pam 5 pam_env.conf`) which mentions use of HOME being
potentially problematic.
Anyway if the goal is to make things easier for users,
simply do the NIX_PATH modification as extraInit.
This fixes the annoying problems generated by the current approach
(#40165 and others) while hopefully serving the original goal.
One way to check if things are borked is to try:
$ sudo env | grep NIX_PATH
Which (before this change) prints NIX_PATH variable with
an unexpanded $HOME in the value.
-------
This does mean the following won't contain user channels for 'will':
$ sudo -u will nix-instantiate --eval -E builtins.nixPath
However AFAICT currently they won't be present either,
due to unescaped $HOME. Unsure if similar situation for other users
of sessionVariables (not sudo) work with current situation
(if they exist they will regress after this change AFAIK).
|
|
|
|
| |
Fork of sonarr (as radarr) but for music instead of series and movies.
|
|\
| |
| | |
Sickbeard/Sickgear/Sickrage: Init and module
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Introduced by 0f3b89bbedc1a33cc1fc3c142e235da2c64614c3.
If services.nixosManual.showManual is enabled and
documentation.nixos.enable is not, there is no
config.system.build.manual available, so evaluation fails. For example
this is the case for the installer tests.
There is however an assertion which should catch exactly this, but it
isn't thrown because the usage of config.system.build.manual is
evaluated earlier than the assertions.
So I split the assertion off into a separate mkIf to make sure it is
shown appropriately and also fixed the installation-device profile to
enable documentation.nixos.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @oxij
|
|\ \
| | |
| | | |
nixos: fix fallout from #46193
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This updates the path to the 'gitlab-shell' to the
correct store path when gitlab is restarted.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 67c8c4917799496dcf2ad6a500441fbbaeb918c9.
'nix run nixos.firefox' is *not* supposed to work - the Nix 2.x
interface attempts to standardize on nixpkgs.*, to get rid of the
nixos/nixpkgs confusion that existed with the channels interface. So
let's not bring that confusion back.
|
|\| |
| | |
| | | |
nixos: doc: implement #12542
|
| | |
| | |
| | |
| | | |
`documentation.nixos`
|
| | |
| | |
| | |
| | |
| | |
| | | |
Because when I see "config.system.build.manual.manual" after I forgot
what it means I ask "Why do I need that second `.manual` there again?".
Doesn't happen with `config.system.build.manual.manualHTML`.
|
|\ \ \
| | | |
| | | | |
nixos: set nixos in nixPath
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This makes using the nixos channel work out of the box with the new
Nix commands. For example:
$ nix run nixos.firefox -c firefox
Fixes #46536
|
|/ / |
|
|/
|
|
|
| |
This allows the user, among other things, to configure jukebox output
to go to non-default alsa devices.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds several improvements the previously introduced
`services.weechat` module:
* Dropped `services.weechat.init` as the initialization script can now
be done on package-level since 2af41719bc using the `configure`
function.
* Added `sessionName` option to explicitly configure a name for the
`screen` session (by default: weechat-screen).
* Added `binary` option to configure the binary name (e.g.
`weechat-headless`).
* Added docs regarding `screen` session and `weechat.service`.
|
| |
|
|\
| |
| | |
nixos/manual: nixos-help knows about colon-separated BROWSER
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is the semantics as understood by `xdg-open`. Using these semantics
on a non-colon-separated variable works because it acts as if it was a
one element long list.
This fixes an issue where it would try to exec
`google-chrome-beta:google-chrome:chromium:firefox` on a system
configured with these semantics in mind.
|
|/ |
|
|
|
|
| |
The gitea path is hardcoded in hooks directory in files of paths like:
repositories/<user>/<repo>.git/hooks/update.d/gitea
|
|
|
|
| |
It is deprecated and will be removed after 18.09.
|
|
|
|
|
|
|
| |
This prevents issues when gitea adds new locales etc. And if they
change locale values in future versions. Or if you rollback to a
previous version of gitea it might be a good idea to use the previous
locale files.
|
|\
| |
| | |
redmine: 2.5.2 -> 3.4.6
|
| | |
|
| |
| |
| |
| | |
added some security features like database.passwordFile
|
| |
| |
| |
| | |
an example
|
|\ \
| |/
|/| |
nixos/nix-daemon: build-max-jobs, add support to auto
|
| | |
|
|\ \
| | |
| | | |
services.synergy: Use graphical target (fixes #9468)
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This code was referenced.
This reverts commit 87f5930c3fb2c852f5243278b7a9da8e117d95e4.
cc @volth
|
| | |
| | |
| | |
| | | |
with previous release
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Broke evaluation of the nixos options.
The option `services.dysnomia' defined in `.../nixos/modules/rename.nix' does not exist.
This reverts commit 5c897b4effc4f51b2d6aa5dba158a839b179d964.
|
| | | |
|
|\ \ \
| | | |
| | | | |
nixos/nix-daemon: default `nix.useSandbox` to `true`.
|
| | |/
| |/| |
|
| | |
| | |
| | |
| | | |
Fixes #41476
|
| | |
| | |
| | |
| | |
| | |
| | | |
It seems like Gitlab doesn't pick up GITLAB_UPLOADS_PATH. The internal uploads
folder is already symlinked to /run/gitlab/uploads by the gitlab package. Here
we symlink this further to ${statePath}/uploads, since /run is (usually) a tmpfs.
|
|/ /
| |
| |
| | |
The old behaviour caused new instances to be unable to start
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 095fe5b43def40279a243e663c662b02caac5318.
Pointless renames considered harmful. All they do is force people to
spend extra work updating their configs for no benefit, and hindering
the ability to switch between unstable and stable versions of NixOS.
Like, what was the value of having the "nixos." there? I mean, by
definition anything in a NixOS module has something to do with NixOS...
|
|\ \
| | |
| | | |
[bot] nixos/*: remove unused arguments in lambdas
|
| | | |
|
|/ / |
|