| 17 Mar 2025 |
jade_ | also you might want to take our release notes generator, tbh. it would make changes a lot more portable, and ours both has more features and is simpler :) | 00:26:10 |
jade_ | oh um. https://github.com/nixos/nix/blob/eb7d7780b18bce679639336cfd8ba6af1fe6139d/doc/manual/source/release-notes/meson.build#L9 thats really funny. this code is for calling our release notes generator and i don't think actually works on changelog-d | 00:36:17 |
John Ericson | I'll defer that to Robert Hensing (roberth) who wrote the old one | 00:36:59 |
John Ericson | It appears to be working? | 00:37:42 |
John Ericson | at least manual build is not failing | 00:37:51 |
jade_ | (i mean the real reason we rewrote it was that we wanted haskell out of our closure) | 00:42:00 |
jade_ | * (i mean the real reason we rewrote it was that we wanted haskell out of our closure and we wanted our release notes generator to be in tree) | 00:42:48 |
jade_ | but one of the notable differences is that ours has contributor credits built in | 00:44:53 |
aidetechbot | hi, i forked nixpkgs but I can't seem to do git fetch upstream locally. I seem to get this error:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I know it's not related to my access rights to github because doing ssh git@github.com authenticates me fine. (and i can clone and fetch other repos fine) Anyone know what could be up? I
| 04:20:37 |
aidetechbot | * hi, i forked nixpkgs but I can't seem to do git fetch upstream locally. I seem to get this error:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I know it's not related to my access rights to github because doing ssh git@github.com authenticates me fine. (and i can clone and fetch other repos fine) Anyone know what could be up?
| 04:20:55 |
aidetechbot | * hi, i forked nixpkgs but I can't seem to do git fetch upstream locally. I seem to get this error:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I know it's not related to my access rights to github because doing ssh git@github.com authenticates me fine. (and i can push and fetch other repos fine) Anyone know what could be up?
| 04:21:27 |
aidetechbot | another detail: it hangs for a while before giving me this error so i'm thinking it might be timing out somewhere and obfuscating the error. | 04:22:08 |
jade_ | this is the wrong channel for this. please check out a nixpkgs dev channel or so instead | 05:30:45 |
| egrieco joined the room. | 06:49:11 |
| piegames joined the room. | 08:07:02 |
John Ericson | Robert Hensing (roberth): https://github.com/NixOS/nixpkgs/pull/390479 can we merge this manual backport of your PR to 24.11? | 15:42:50 |
roberth | I would think so, yeah | 15:43:34 |
John Ericson | OK thanks | 15:45:12 |
emily | pkgsStatic.nixVersions.nix_2_26 is still broken | 15:57:48 |
emily | (at eval time) | 15:58:09 |
John Ericson | emily: wait is that new in this PR? | 16:15:18 |
emily | no, I reported it here before | 16:16:34 |
emily | the complicated splicing stuff that I don't understand why it's there is broken | 16:16:47 |
John Ericson | Eelco: So the reason it is not a CanonPath is the symlink target and "location the source tree is for symlink resolution purposes" is an OS path | 16:17:02 |
John Ericson | even more confusing, in the case of remote file systems it might be an OS path of another operating system | 16:17:33 |
John Ericson | I am wary of canonicalizing because we don't want a situation where the symlink points outside the source tree, but then another symlink points back inside, to allow the symlink to be resolved | 16:18:33 |
John Ericson | rather as soon as any intermediate encountered during symlink resolution leaves the source tree, it's game over | 16:19:30 |
John Ericson | Eelco: Also happy with https://github.com/NixOS/nix/pull/12658 now? | 17:18:53 |
emily | (I was just mentioning it wrt bumping nixVersions.latest) | 17:36:36 |
emily | (and that more fixes will need backporting later) | 17:36:45 |