about summary refs log tree commit diff
path: root/nixos
Commit message (Collapse)AuthorAge
* Merge pull request #143314 from bobby285271/pantheonBobby Rong2021-10-29
|\ | | | | Pantheon updates 2021-10-27
| * nixos/pantheon: mention latest appcenter changes in manualBobby Rong2021-10-29
| |
| * nixos/pantheon: use Inter as default sans-serif fontBobby Rong2021-10-28
| |
* | Merge pull request #143366 from Synthetica9/yq-test-rmSandro2021-10-28
|\ \
| * | nixosTests.yq: remove, move to yq packagePatrick Hilhorst2021-10-28
| | |
* | | rl-2111: Note the addition of virtualisation.useNixStoreImage...talyz2021-10-28
| | | | | | | | | | | | ...and rename of virtualisation.pathsInNixDB.
* | | make-disk-image: Add an argument to only build a Nix store imagetalyz2021-10-28
| | | | | | | | | | | | | | | | | | Add the `onlyNixStore` argument which enables building images containing the contents of the Nix store at the root, instead of a full system.
* | | gitlab.tests: Improve test performancetalyz2021-10-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Massively reduce the time it takes running the test by building a proper root disk image and increasing the virtualized core count to 4. This should make it much easier for the tests to pass even on weaker systems. With my laptop (AMD Ryzen 7 PRO 2700U) as the reference system, I see the following test run times: - No change: Times out after 28 mins - Building a root image: 7 mins, 48 secs - Building a root image and bumping the core count: 7 mins, 17 secs The times include the time it takes to build the image (~1 min, 20 secs).
* | | discourse.tests: Improve test performancetalyz2021-10-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Massively reduce the time it takes running the test by building a proper root disk image and increasing the virtualized core count to 4. This should make it much easier for the tests to pass even on weaker systems. With my laptop (AMD Ryzen 7 PRO 2700U, 32GB RAM) as the reference system, I see the following test run times: - No change: 25 mins, 49 secs - Building a root image: 4 mins, 44 secs - Building a root image and bumping the core count: 3 mins, 6 secs The times include the time it takes to build the image (~40 secs).
* | | nixos/testing-python: Copy test script derivations to nodestalyz2021-10-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | Make sure the all derivations referenced by the test script are available on the nodes. Accessing these derivations works just fine without this change when using 9p to mount the host's store, but when an image is built (virtualisation.buildRootImage), the dependencies need to be copied to the image. We don't want to copy the script itself, though, since that would trigger unnecessary image rebuilds.
* | | nixos/qemu-vm: Rename pathsInNixDB to additionalPathstalyz2021-10-28
| | | | | | | | | | | | | | | | | | pathsInNixDB isn't a very accurate name when a Nix store image is built (virtualisation.useNixStoreImage); rename it to additionalPaths, which should be general enough to cover both cases.
* | | nixos/qemu-vm: Allow building a Nix store image instead of using 9ptalyz2021-10-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add the `useNixStoreImage` option, allowing a disk image with the necessary contents from the Nix store to be built using make-disk-image.nix. The image will be mounted at `/nix/store` and acts as a drop-in replacement for the usual 9p mounting of the host's Nix store. This removes the performance penalty of 9p, drastically improving execution speed of applications which do lots of reads from the Nix store. The caveats are increased disk space usage and image build time.
* | | make-disk-image: Add additionalPaths argumenttalyz2021-10-28
| | | | | | | | | | | | | | | Add an argument which makes it possible to add additional paths to the image's nix store.
* | | make-disk-image: Add copyChannel argumenttalyz2021-10-28
| | | | | | | | | | | | | | | | | | | | | | | | Add a copyChannel argument which controls whether the current source tree will be made available as a nix channel in the image or not. Previously, it always was. Making it available is useful for interactive use of nix utils, but changes the hash of the image when the sources are updated.
* | | make-disk-image: Reintroduce the installBootLoader argumenttalyz2021-10-28
| |/ |/| | | | | | | | | installBootLoader was removed in f1708a9d7d79e2bf2961fc648625578b23b3460f; probably by mistake, since only the logic was removed, not the argument.
* | Merge pull request #142810 from bobby285271/pantheonBobby Rong2021-10-28
|\ \ | | | | | | Pantheon updates 2021-10-25, 2021-10-26
| * | pantheon.elementary-settings-daemon: 1.0.0 -> 1.1.0Bobby Rong2021-10-26
| | |
| * | xdg-desktop-portal-pantheon: init at 1.0.0Bobby Rong2021-10-26
| | |
* | | Merge pull request #143074 from iAmMrinal0/update/google-cloud-sdkJonas Chevalier2021-10-27
|\ \ \ | | | | | | | | google-cloud-sdk: 361.0.0 -> 362.0.0
| * | | nixos/tests: add google-cloud-sdkMrinal Purohit2021-10-27
| | | |
* | | | Merge pull request #113198 from Izorkin/update-mastodon-mailGuillaume Girol2021-10-27
|\ \ \ \ | |_|_|/ |/| | | nixos/mastodon: fix send e-mail notifications
| * | | nixos/mastodon: fix send e-mail notificationsIzorkin2021-10-26
| | | |
* | | | Merge pull request #142800 from Ma27/drop-nextcloud-20Maximilian Bosch2021-10-27
|\ \ \ \ | | | | | | | | | | nextcloud20: drop
| * | | | nixos/nextcloud: drop obsolete assertionMaximilian Bosch2021-10-27
| | | | |
| * | | | nextcloud20: dropMaximilian Bosch2021-10-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The version 20 of Nextcloud will be EOLed by the end of this month[1]. Since the recommended default (that didn't raise an eval-warning) on 21.05 was Nextcloud 21, this shouldn't affect too many people. In order to ensure that nobody does a (not working) upgrade across several major-versions of Nextcloud, I replaced the derivation of `nextcloud20` with a `throw` that provides instructions how to proceed. The only case that I consider "risky" is a setup upgraded from 21.05 (or older) with a `system.stateVersion` <21.11 and with `services.nextcloud.package` not explicitly declared in its config. To avoid that, I also left the `else-if` for `stateVersion < 21.03` which now sets `services.nextcloud.package` to `pkgs.nextcloud20` and thus leads to an eval-error. This condition can be removed as soon as 21.05 is EOL because then it's safe to assume that only 21.11. is used as stable release where no Nextcloud <=20 exists that can lead to such an issue. It can't be removed earlier because then every `system.stateVersion < 21.11` would lead to `nextcloud21` which is a problem if `nextcloud19` is still used. [1] https://docs.nextcloud.com/server/20/admin_manual/release_schedule.html
* | | | | Merge #143048: nixosTests.hibernate: Shut down when finishedVladimír Čunát2021-10-27
|\ \ \ \ \ | |_|_|/ / |/| | | |
| * | | | nixosTests.hibernate: Make sure machines are shut down when finishedAnders Kaseorg2021-10-26
| | |/ / | |/| | | | | | | | | | | | | | Co-authored-by: Janne Heß <janne@hess.ooo> Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* | | | pam_mount: do not re-prompt for passwordPeter Hoeg2021-10-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | nixos-rebuild test causes pam_mount to prompt for a password when running with an encrypted home: building '/nix/store/p6bflh7n5zy2dql8l45mix9qnzq65hbk-nixos-system-mildred-18.09.git.98592c5da79M.drv'... activating the configuration... setting up /etc... reenter password for pam_mount: (mount.c:68): Messages from underlying mount program: (mount.c:72): crypt_activate_by_passphrase: File exists (pam_mount.c:522): mount of /dev/mapper/vg0-lv_home_peter failed kbuildsycoca5 running... This change makes pam_mount not prompt. It still tries to remount (and fails in the process) but that message can be ignored. Fixes: #44586
* | | | nixos/restic: rename s3CredentialsFile to environmentFileeyjhb2021-10-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This is done as the s3CredentialsFile specifies the environmentFile for the systemd service, which can be used for more than just s3. Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com>
* | | | nixos/step-ca: fix comment typoWei Tang2021-10-26
| | | |
* | | | Merge pull request #119719 from greizgh/seafileSandro2021-10-26
|\ \ \ \ | |/ / / |/| | |
| * | | nixos/seafile: init serviceGreizgh2021-10-23
| | | |
* | | | Merge #142864: nixos/gnome: fix an alias referenceVladimír Čunát2021-10-26
|\ \ \ \
| * | | | nixos/gnome: remove alias reference to source-sans-proJonathan Ringer2021-10-25
| | | | |
* | | | | nixos/doc: add jibri to release notesCleeyv2021-10-25
| | | | |
* | | | | nixos/jibri: add nixos testCleeyv2021-10-25
| | | | |
* | | | | nixos/jibri: fix & docs for enable not via meetCleeyv2021-10-25
| | | | |
* | | | | nixos/jibri: add finalize script optionCleeyv2021-10-25
| | | | |
* | | | | nixos/jibri: init at 8.0-93-g51fe7a2Cleeyv2021-10-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This module was written by @puckipedia for nixcon-video-infra 2020. Minor changes made by @cleeyv for compat with existing jibri package. Co-authored-by: Puck Meerburg <puck@puck.moe>
* | | | | nixos/jitsi-meet: add jibri.enableCleeyv2021-10-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This option enables a jibri service on the same host that is running jitsi-meet. It was written, along with the jibri module, by @puckipedia for nixcon-video-infra 2020. Co-authored-by: Puck Meerburg <puck@puck.moe>
* | | | | Merge pull request #142869 from jonringer/fix-21.11-release-name-in-notesTimothy DeHerrera2021-10-25
|\ \ \ \ \ | | | | | | | | | | | | nixos/release-notes: fix 21.11 release name
| * | | | | nixos/release-notes: fix 21.11 release nameJonathan Ringer2021-10-25
| |/ / / /
* | | | | Merge pull request #139311 from NinjaTrappeur/nin-acme-fix-webrootMartin Weinelt2021-10-25
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | nixos/acme: add webroots to ReadWritePathsFélix Baylac-Jacqué2021-10-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since 7a10478ea7b992ffa1f19f389e53df0fe2aa936d, all /var except /var/lib/acme gets mounted in a read-only fashion. This behavior breaks the existing acme deployments having a webroot set outside of /var/lib/acme. Collecting the webroots and adding them to the paths read/write mounted to the systemd service runtime tree. Fixes #139310
* | | | | Merge pull request #142570 from flokli/add-missing-cryptsetup-targetsFlorian Klink2021-10-25
|\ \ \ \ \ | | | | | | | | | | | | nixos/systemd: add remote-cryptsetup.target
| * | | | | nixos/systemd: add remote-cryptsetup.targetFlorian Klink2021-10-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | /etc/crypttab can contain the _netdev option, which adds crypto devices to the remote-cryptsetup.target. remote-cryptsetup.target has a dependency on cryptsetup-pre.target. So let's add both of them. Currently, one needs to manually ssh in and invoke `systemctl start systemd-cryptsetup@<name>.service` to unlock volumes. After this change, systemd will properly add it to the target, and assuming remote-cryptsetup.target is pulled in somewhere, you can simply pass the passphrase by invoking `systemd-tty-ask-password-agent` after ssh-ing in, without having to manually start these services. Whether remote-cryptsetup.target should be added to multi-user.target (as it is on other distros) is part of another discussion - right now the following snippet will do: ``` systemd.targets.multi-user.wants = [ "remote-cryptsetup.target" ]; ```
* | | | | | Merge #142786: plasma5: fix eval without aliasesVladimír Čunát2021-10-25
|\ \ \ \ \ \
| * | | | | | plasma5: fix evaluation with aliases disabled and thunderbolt enabledajs1242021-10-24
| | |_|_|/ / | |/| | | |
* | | | | | nixos/hadoop: add better testillustris2021-10-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The existing tests for HDFS and YARN only check if the services come up and expose their web interfaces. The new combined hadoop test will also test whether the services and roles work together as intended. It spin up an HDFS+YARN cluster and submit a demo YARN application that uses the hadoop cluster for storageand yarn cluster for compute.
* | | | | | nixos/hadoop: fix yarn, add more service configuration optionsillustris2021-10-25
| | | | | |