| 31 Aug 2021 |
 Robert Hensing (roberth) | anyway, this is probably going nowhere and I need to get work done, ttyl | 12:30:20 |
| 1 Sep 2021 |
 niksnut | In reply to @roberthensing:matrix.org
nix flake update should be nix registry update? I think? No, nix flake update updates the flake lock file, it doesn't have anything to do with the registry. | 16:37:46 |
| Robert Hensing (roberth) | then I don't know what should have been modified when I used it. Nothing changed. | 16:38:46 |
| niksnut | Maybe there was nothing to update? | 16:39:35 |
| Robert Hensing (roberth) | or maybe it cached the thing I wanted to update | 16:40:13 |
| niksnut | it implies --tarball-ttl 0 so it shouldn't cache anything | 16:42:02 |
| Robert Hensing (roberth) | hmm. That applies to git caching as well right? | 16:42:28 |
| Robert Hensing (roberth) | it was github anyway, so that's a tarball | 16:42:43 |
| niksnut | yes | 16:43:18 |
| Robert Hensing (roberth) | In reply to @roberthensing:matrix.org
nix flake update <inputName> would make most sense to me can it be changed to this? | 16:44:10 |
| Robert Hensing (roberth) | so it's all by default, or the closure of specified inputs | 16:44:49 |
| Robert Hensing (roberth) | you know what, this is probably better to discuss on github, so the discussion is more discoverable | 16:50:54 |
| niksnut | In reply to @roberthensing:matrix.org
can it be changed to this? No because nix flake update takes an optional flakeref (like nix flake update /path) so this would be ambiguous. | 19:48:36 |
| Robert Hensing (roberth) | right. I've never wanted to do that. Most package managers just operate on the working directory | 20:43:41 |
 Las | I never realized that the flake URI parameter to nix flake update was the flake whose inputs you wanted to update, and not the URI of the input you wanted to update... | 20:47:04 |
| Las | This is honestly quite counterintuitive | 20:47:26 |
 Jan Tojnar | yeah, for example npm has --prefix option for that | 23:23:09 |
| Jan Tojnar | * yeah, for example, npm has --prefix option for that | 23:23:20 |
| 2 Sep 2021 |
| niksnut | In reply to @Las:matrix.org
This is honestly quite counterintuitive Except that it's what every other nix command does, so it would be very inconsistent if nix flake update suddenly did something else. | 07:14:57 |
 tomberek | I made a similar mistake in assumption, but the consistency is nice and more powerful once I understood it. Perhaps a warning output clarifying what is being updated? | 07:17:20 |
| Jan Tojnar | yeah consistency is nice but not at the cost of ergonomy | 13:58:53 |
| Jan Tojnar | if 99% of time you want to update stuff in the current directory, the consistency is rather annoying | 13:59:37 |
| 3 Sep 2021 |
|  Rev. CornWallace III (sun/tzu) changed their display name from cw (just got delta) to cw (novus ordo seclorum). | 07:40:59 |
| 6 Sep 2021 |
|  Bramfatur left the room. | 13:31:12 |
 trofi | Does nix implement network sandbox? Updated nixUnstable today and now getting fetch failrues:
nix build -f . libssh2 --keep-going
warning: error: unable to download 'https://www.libssh2.org/download/libssh2-1.10.0.tar.gz': Couldn't resolve host name (6); retrying in 352 ms
6 is probably a ENXIO. I'm not sure which process gets a rejection. Probably a nix-daemon itself? I suspect it's due to systemd resolved's nameserver 127.0.0.53.
| 21:42:53 |
| trofi | Disabling sandbox with sandbox = false fixes downloader. | 22:08:42 |
 sterni | trofi: https://github.com/NixOS/nix/issues/5089 | 23:27:46 |
| 7 Sep 2021 |
| trofi | Aha, thank you! | 06:37:20 |
| Las | In reply to @trofi:matrix.org
Does nix implement network sandbox? Updated nixUnstable today and now getting fetch failrues:
nix build -f . libssh2 --keep-going
warning: error: unable to download 'https://www.libssh2.org/download/libssh2-1.10.0.tar.gz': Couldn't resolve host name (6); retrying in 352 ms
6 is probably a ENXIO. I'm not sure which process gets a rejection. Probably a nix-daemon itself? I suspect it's due to systemd resolved's nameserver 127.0.0.53.
Access to the network has always been restricted, except in fixed-output derivations | 09:15:59 |
| trofi | How that restriction is implemented? Is it some systemd unit magic? Or some in-daemon code? I only found a few seemingly irrelevant filesystem syscall filters. | 10:15:21 |
