| 26 Sep 2022 |
jhillyerd | In reply to @rendakuenthusiast:imperishable.name this is basically a failure of hermeticism, right? the redis build was happening on my system and it has one bit of source code that looks at /usr/bin/pgrep. is there a principled way in nix to make that not visible to derivations being built? Typically you would patch/rewrite the package to not point at /usr/bin, example for regular grep: https://github.com/NixOS/nixpkgs/blob/4e62b94df308e197c1f107564ebdb4318bb80e27/pkgs/development/libraries/nss/generic.nix#L61 | 04:59:20 |
rendakuenthusiast | Winter (she/her): I'm using builtins.fetchTarball to fetch an additional module with some custom modifications I made, from a server I control | 05:00:44 |
rendakuenthusiast | jhillyerd: where does that substituteInPlace function come from? is that supposed to be shell code? | 05:01:59 |
jhillyerd | I believe it is one of the shell functions that mkDerivation provides | 05:05:43 |
Zhaofeng Li | In reply to @rendakuenthusiast:imperishable.name and when colmena tries to deploy from my laptop, I have /usr/bin/pgrep installed at that path in my normal OS Hmm, pgrep should have been added when the tests were enabled in https://github.com/NixOS/nixpkgs/commit/835c3419d9b9 | 19:42:12 |
Zhaofeng Li | In reply to @rendakuenthusiast:imperishable.name Winter (she/her): I'm using builtins.fetchTarball to fetch an additional module with some custom modifications I made, from a server I control I recommend adding a sha256 to the fetchTarball call so it's pinned to the specific version of the module and cached correctly. If you don't have a sha256, Nix itself has some time-based caching (need to look at the expiration - don't know offhand) | 19:44:50 |
Zhaofeng Li | (it's 1 hour and can be controlled with tarball-ttl) | 19:46:53 |
| 27 Sep 2022 |
rendakuenthusiast | In reply to @zhaofeng:zhaofeng.li I recommend adding a sha256 to the fetchTarball call so it's pinned to the specific version of the module and cached correctly. If you don't have a sha256, Nix itself has some time-based caching (need to look at the expiration - don't know offhand) so I updated the file at the url and wanted it to get refetched | 00:58:54 |
rendakuenthusiast | I tried doing the trick of wiping out the sha256, but it just said that the hash of the previously-downloaded version was what the hash had to be | 00:59:16 |
rendakuenthusiast | not the new version I uploaded | 00:59:21 |
rendakuenthusiast | so it's not fetching the new version | 00:59:28 |
Zhaofeng Li | In reply to @rendakuenthusiast:imperishable.name I tried doing the trick of wiping out the sha256, but it just said that the hash of the previously-downloaded version was what the hash had to be If you set sha256 to all zeroes (or lib.fakeSha256) does it force a refetch? | 01:00:20 |
rendakuenthusiast | Zhaofeng Li: that's what i tried, it doesn't force a refresh, it says that it expects the same sha256 that was there before corresponding to the outdated version of the file | 03:50:27 |
| @palo:xaos.space changed their profile picture. | 07:29:30 |
| @palo:xaos.space changed their profile picture. | 07:31:44 |
| @palo:xaos.space changed their profile picture. | 07:35:09 |
| @skamdart:matrix.org joined the room. | 21:40:02 |