| 11 Sep 2021 |
|  dusk changed their profile picture. | 16:32:35 |
| 14 Sep 2021 |
 baloo | I really don't understand why I can't get a merge on https://github.com/NixOS/nixpkgs/pull/137197 | 16:41:30 |
| baloo | why are we waiting on eelco when he merged upstream PR himself | 16:43:28 |
 tomberek | is it an issue of wanting the fix to be a release vice a patch? | 18:30:53 |
| baloo | I mean, there was a couple call for a new release of nix, so far unsuccessful | 18:53:33 |
| baloo | I don't understand why a patch would be bad, since we have such easy ability to patch upstreams | 18:54:02 |
| baloo | the ability to patch upstream is one of the best thing there is about nix, I don't get why people would attach important to an upstream release | 18:54:51 |
| baloo | like, by merging the patch upstream, there is some "acceptance" (wrong word) the patch is needed. So it feels like a pure philosophical limitation ... and I don't get it. | 18:57:04 |
| baloo | (just trying to understand things going on here, not trying to be an ass or something) | 18:57:46 |
| tomberek | i don't know, i think it'd be fine for most, but Nix is a bit special and so a lot of the normal committers are hesitating. I'm not aware of any expressed objections. | 18:58:47 |
| baloo | I've been chasing the issue for a month now, and seeing it drag when it should be fixed. I don't know, bothers me | 18:58:51 |
| tomberek | We can post it in "Nix Hackers" | 18:59:39 |
| 15 Sep 2021 |
| tomberek | baloo: This indicates that more than that PR is needed: https://github.com/NixOS/nix/issues/5089#issuecomment-917606674 | 01:01:13 |
| baloo | i mean | 01:02:32 |
| baloo | sure | 01:02:33 |
| baloo | still trying to manage my frustration here :) | 01:03:10 |
|  @Las:matrix.org joined the room. | 20:46:38 |
| 17 Sep 2021 |
|  @geowy:matrix.org joined the room. | 11:26:27 |
| 18 Sep 2021 |
| @geowy:matrix.org left the room. | 00:09:46 |
| 19 Sep 2021 |
|  Artturin changed their display name from artturin to Artturin. | 04:46:52 |
|  @shadowninja55:matrix.org left the room. | 13:05:48 |
| 22 Sep 2021 |
|  @bew:matrix.org joined the room. | 22:24:11 |
| @bew:matrix.org | Hello, I'm reading https://github.com/wmertens/rfcs/blob/master/rfcs/0017-intensional-store.md and there's something I don't understand:
In the part A note about reproducibility, it says:
There is no need for a given $out to always generate the same $cas. [...] There is no obligation that a single $out only stores a single $cas entry.
| 22:26:23 |
| @bew:matrix.org | How is that possible? | 22:26:33 |
| @bew:matrix.org | How can a single $out generate multiple $cas ? | 22:27:35 |
| @bew:matrix.org | (if there's a better room for this question, please tell me 🙏) | 22:28:07 |
| tomberek | bew: Basically that is saying that the builds don't have to be reproducible for the intentional store to work. (of course it helps) | 23:07:25 |
| tomberek | You and I can build the same $out, but get different $cas's. This isn't ideal, but that's why there is a mapping from 1 $out to possible multiple $cas's. | 23:09:12 |
| 23 Sep 2021 |
 afontain | what's $cas ? | 10:14:18 |
| afontain | or is it $cas's ? | 10:14:31 |
