| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also disable it when noXlibs in NixOS.
|
|\ |
|
| |\ |
|
| | | |
|
| |\ \
| | | |
| | | | |
programs/bash: install nix-bash-completions if completion is enabled
|
| | |/ |
|
| |\ \
| | | |
| | | | |
usbguard: 0.7.0 -> 0.7.2
|
| | | |
| | | |
| | | |
| | | | |
-P flag)
|
| | |/
| |/| |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
No need to cross-compile pure data...
|
| | | |
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
pkgs/applications/misc/pytrainer/default.nix
pkgs/development/tools/pew/default.nix
pkgs/tools/misc/you-get/default.nix
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* digitalbitbox: init at 2.2.2
The commits that lead to this have been squashed from independent
commits see branch @vidbina/add/digitalbitbox-wip that did the
following:
- 0a3030fa0ec digitalbitbox: init at 2.2.2
- c18ffa3ffd4 digitalbitbox: moved meta to EOF
- 0c5f3d6972a digitalbitbox: using preConfigure + configureFlags
- a85b1dfc3fd digitalbitbox: nativeBuildInputs
- 90bdd35ef0f digitalbitbox: autoreconfHook
- 91810eea055 digitalbitbox: default installPhase & makeWrapper
- 90e43fb7e2a digitalbitbox: doc rm $PWD hack & printf-tee deal
- fd033b2fe5a digitalbitbox: cleanup, alphabetically sort attrs
- c5907982db3 digitalbitbox: added hardware module
- 88e46bc9ae0 digitalbitbox: added program module
- amend to change name: dbb-app -> digitalbitbox
- amend to add install instructions based on feedback
(https://github.com/NixOS/nixpkgs/pull/33787#issuecomment-362813149)
- amend to add longDescription
- moved program to its own dir
- overridable udev rules handling
- added docs to manual
- added package attr to program module
- added package attr to hardware module
* digitalbitbox: use libsForQt5.callPackage
|
|\| |
|
| | |
|
|\| |
|
| |\
| | |
| | | |
buildbot: 0.9.15.post1 -> 1.0.0
|
| | | |
|
| |\ \
| | | |
| | | | |
nixos/tests: add forgotten xrdp.nix
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | | |
This is to cleanup the (re-)revert of merge to master.
|
| |/ / |
|
|\| | |
|
| |\ \
| | | |
| | | | |
piwik is now matomo
|
| | | |
| | | |
| | | |
| | | | |
when we need to change it anyway for the rename.
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
syncthing,qsyncthingtray: remove syncthing-inotify
|
| | | | |
| | | | |
| | | | |
| | | | | |
syncthing-inotify is replaced by the new syncthing "fswatcher" feature.
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | |/ / /
| |/| | | |
grub module: suggest by-id paths for devices
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since they are more stable, their use should be encouraged over that of
potentially volatile identifiers like /dev/[sh]da.
|
|\| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Eelco Dolstra wrote:
Hm, this is not really the intended use of stateVersion. From the description:
Every once in a while, a new NixOS release may change
configuration defaults in a way incompatible with stateful
data. For instance, if the default version of PostgreSQL
changes, the new version will probably be unable to read your
existing databases. To prevent such breakage, you can set the
value of this option to the NixOS release with which you want
to be compatible. The effect is that NixOS will option
defaults corresponding to the specified release (such as using
an older version of PostgreSQL).
So this is only intended for options that have some corresponding on-disk state. AFAICT this is not the case for sound. In any case stateVersion is a necessary evil that only exists because we can't just upgrade Postgres databases or change SSH host keys. It's not necessary for things like whether sound is enabled. (If the user discovers that sound is suddenly disabled, they can just enable it.)
I had some vague recollection that we also had a configVersion option setting to control the defaults for non-state-related options, but I can't find it so maybe it was only discussed.
|
| | | | |
| | | | |
| | | | | |
Policy configuration files live under /etc/chromium for Chromium, and under /etc/opt/chrome for Google Chrome.
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
fwupd: 1.0.5 update & cleanups
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 11fc2bad56bb6464b161f5ce911511a0137cfe2c.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes: #32142
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use systemd to create the directory for UNIX socket. Also use localhost instead
of 127.0.0.1 as is done in default cupsd.conf so that IPv6 is enabled when
available.
|