| 4 Jun 2024 |
jakehamilton | This is definitely weird, but I ended up needing this fetcher because it supports some things that the builtin one doesn't (such as marking files executable, unpacking, and output hash info). | 05:08:13 |
@irenes:matrix.org | (and I suggested mentioning it here because it's such astonishing behavior that I thought we might like to look into how important it is) | 05:10:32 |
K900 | corepkgs continues to haunt us | 05:47:00 |
jade_ | In reply to @jakehamilton:auxolotl.org Hey there folks, is anyone familiar with import <nix/fetchurl.nix>? I just found out about this and was confused because I thought that <> referred to NIX_PATH values, but this seemed to work. Notably import <nix> does NOT work. As it turns out, this behavior is custom inside of Nix itself which maps certain known files such as: https://github.com/NixOS/nix/blob/master/src/libexpr/fetchurl.nix it's mentioned in puck's talk :) | 06:19:03 |
jakehamilton | In reply to @jade_:matrix.org it's mentioned in puck's talk :) Oooh I haven't seen or heard that yet. Would you happen to have a link? | 06:19:47 |
jade_ | https://media.ccc.de/v/nixcon-2023-36425-reinventing-the-wheel-with-zilch | 06:20:13 |
jakehamilton | Oh perfect, thank you!! | 06:20:43 |
aloisw | Right now it seems that the thing that closes issues when they are fixed triggers on forks too (for example, https://git.lix.systems/lix-project/lix/issues/365#event-4081). Is this easy to fix or should I stop pushing to my fork? | 06:25:45 |
jade_ | what the heck forgejo | 06:26:10 |
jade_ |  Download image.png | 06:26:57 |
jade_ | we don't close from non-default branches, but clearly it also shouldn't close from forks | 06:27:32 |
aloisw | So I guess I should just rename my branch? | 06:28:55 |
jade_ | oh, is it on main? | 06:29:05 |
jade_ | try not having it on main and see what happens I guess? | 06:29:14 |
aloisw | In reply to @jade_:matrix.org oh, is it on main? It is, sorry for the complications this may have caused. I will push to a different branch in the future. | 06:31:14 |
jade_ | no worries, this is arguably a forgejo bug | 06:31:24 |
jade_ | it's very absurd behaviour imo | 06:31:32 |
jade_ | i understand why it does this on other repos, since we actually do use cross repo issue closing sometimes | 06:31:47 |
jade_ | but being a fork is absurd | 06:31:54 |
aloisw | Well, a fork is another repo, so… | 06:33:41 |
jade_ |  Download image.png | 06:38:39 |
jade_ | https://codeberg.org/forgejo/forgejo/issues/4010 | 06:41:16 |
jade_ | there, filed a forgejo bug about it | 06:41:23 |
K900 | Love that issue title | 06:42:22 |
jade_ | anyway, this kind of absurdity isn't your fault and we should keep filing bugs about these things as we find more of them :) | 06:46:22 |
@irenes:matrix.org | for sure | 06:51:02 |
@irenes:matrix.org | we're honestly doing something novel even just with how we accept contributions in all these ways, we should for sure be leaving a trail so others can follow | 06:51:38 |
| quantumjump joined the room. | 11:11:51 |
| ghpzin joined the room. | 11:13:12 |
| raitobezarius changed their display name from raitobezarius (DECT: 7248) to raitobezarius. | 11:16:29 |