| 17 Jun 2026 |
QuadRadical (Ping) | the mtime warning still happens, but maybe the command succeeds? lets see | 14:12:24 |
QuadRadical (Ping) | ah yes, the command succeeds, it just has that warning | 14:23:27 |
truh | yes I still get the warnings too | 14:36:48 |
zoë (@blokyk) | QuadRadical (Ping): is your flake/repo public, so that we can try to reproduce it? | 14:38:17 |
zoë (@blokyk) | * QuadRadical (Ping): is your flake/repo public, so that others can try to reproduce it? | 14:39:36 |
QuadRadical (Ping) | yep! | 14:40:03 |
QuadRadical (Ping) | the problem repo for me is https://forgejo.ellis.link/continuwuation/continuwuity, which i have as an input in my flake, https://git.federated.nexus/henry-hiles/nixos | 14:40:37 |
| Easy6 joined the room. | 22:27:31 |
| 18 Jun 2026 |
QuadRadical (Ping) | ?ref behavior for flakes seems to be broken on Lix 2.95.2:
quadradical@quadraticpc ~/D/C/q/qhelpdesk (main) [1]> nix build git+https://forgejo.ellis.link/Henry-Hiles/continuwuity?ref=quad/fix/musl-static-builds
warning: could not update mtime for file '': No such file or directory
fetching Git repository 'https://forgejo.ellis.link/Henry-Hiles/continuwuity'fatal: ambiguous argument 'quad/fix/musl-static-builds': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
error:
… while fetching the input 'git+https://forgejo.ellis.link/Henry-Hiles/continuwuity?ref=quad/fix/musl-static-builds'
error: program 'git' failed with exit code 128
| 15:02:18 |
QuadRadical (Ping) | either that or i misunderstand how it should work | 15:06:30 |
Rutile | iirc there was an isssue about this but can't find it rn :/ | 16:23:04 |
Yureka (she/her) | try ref=refs/heads/quad/fix/musl-static-builds | 17:15:31 |
QuadRadical (Ping) | Like this?
quadradical@quadraticpc ~/D/C/continuwuity (quad/feat/musl-static-builds)> nix build git+https://forgejo.ellis.link/Henry-Hiles/continuwuity?ref=refs/heads/quad/fix/musl-static-builds#default-static-x86_64
fatal: couldn't find remote ref refs/heads/quad/fix/musl-static-builds
error:
… while fetching the input 'git+https://forgejo.ellis.link/Henry-Hiles/continuwuity?ref=refs/heads/quad/fix/musl-static-builds'
error: program 'git' failed with exit code 128
| 17:16:16 |
| whispers [& it/fae] changed their display name from whispers [& it/fae] to the void. | 18:45:04 |
| whispers [& it/fae] changed their display name from the void to meow meow. | 18:45:59 |
| whispers [& it/fae] changed their display name from meow meow to whispers [& it/fae]. | 19:11:19 |
| 19 Jun 2026 |
| indium114 joined the room. | 07:15:40 |
| 20 Jun 2026 |
| frahz changed their profile picture. | 06:06:24 |
| Bwop joined the room. | 22:31:03 |
| 22 Jun 2026 |
| @dontblameme:matrix.org left the room. | 12:26:07 |
| @nairou:matrix.org left the room. | 17:30:34 |
| imurx joined the room. | 23:06:40 |
zoë (@blokyk) | ok maybe i'm just too tired but i just got report from a friend i was spreading the gospel of lix to that the lix-installer (from the short url) installed 2.95.2 and not .3, which is kinda weird. but giving a quick glance at the code i'm not even sure what going on because this says 2.95.1? i don't have any machine i can test on right now and am about to go to bed so i'm definitely not spinning up a networked vm just for this, so if anyone wants to confirm/infirm my fear (even by just looking at the code and saying "zoe are you dumb or what," that'd be very welcome :) | 23:13:15 |
zoë (@blokyk) | (also i just noticed that the script says "go to g.l.s/lix-project/lix-installer/releases" but that url doesn't actually exist :p) | 23:13:56 |
| 23 Jun 2026 |
raitobezarius | mmmmm | 10:24:44 |
raitobezarius | this is plausible | 10:24:46 |
Rutile | Yep, it says 2.95.2 while installing | 10:33:58 |
jyrama | In the series of odd things, or misunderstandings, if I run - ‘nix run .#all-dependencies’ a transitive dependency needing GCC can’t find cc, but when running
- ‘nix-shell -p vibe” (to try out new tooling for fun) and then the same ‘nix run .#all-tests’ the cargo now finds the cc and my openssl-sys compiles.
Any clues what might be going on? The gist is that I had been inside the second case for way too long and had broken my builds in some obscure way in the middle but no idea where. Running lix 2.92.2. | 11:00:28 |
jyrama | One shell reload later I lost eg. “which”. Now I wonder if it’s my hardware. 😅 | 11:14:07 |
raitobezarius | 2.92.2 is quite EOL | 11:34:04 |