| 6 Jun 2026 |
 maralorn | Does this bug still exist? https://git.lix.systems/lix-project/lix/issues/18 | 19:30:16 |
| maralorn | Because I am trying to reproduce the issue on my system without installing a newer lix version globally. | 19:30:38 |
| maralorn | So I thought running my test suite as root would be a quick workaround for debugging. 😄 | 19:31:01 |
 raitobezarius | Yes you need to do NIX_REMOTE=local | 20:10:21 |
| raitobezarius | But this bug has not been fully fixed | 20:10:27 |
| 7 Jun 2026 |
|  define9293 joined the room. | 05:27:55 |
|  CRYSTL ⬡ changed their profile picture. | 05:36:14 |
| CRYSTL ⬡ changed their display name from CRYSTL ⬡ to SUSTL ⬡. | 05:36:24 |
|  @avdhut7009:matrix.org left the room. | 13:47:46 |
|  Baum(she/they) changed their display name from Baum(she/they) 6521@GPN24 to Baum(she/they). | 18:31:56 |
|  zimward changed their display name from zimward @GPN24 to zimward. | 21:06:53 |
|  @out:matrix.org left the room. | 23:16:21 |
| 8 Jun 2026 |
|  marcadia joined the room. | 09:05:24 |
|  @monsterdruide1:matrix.org joined the room. | 14:40:58 |
| @monsterdruide1:matrix.org | If I caught it correctly, the lix-git page had a loop within its anubis setup a few minutes ago, pointing from the anubis checker back onto the checker.
I managed to pull nix flake update during this time, and am now facing broken-ness:
$ nix flake update lix
warning: could not update mtime for file '': No such file or directory
error:
… while updating the lock file of flake 'git+file:///persist/home/monsterdruide1/nixos'
… while updating the flake input 'lix'
… while fetching the input 'git+https://git.lix.systems/lix-project/lix.git'
error: opening file '': No such file or directory
How can I get my flake back on track? I already tried deleting ~/.cache/nix, with no effect.
| 14:44:02 |
| @monsterdruide1:matrix.org | To my understanding, it happens here:
https://git.lix.systems/lix-project/lix/src/branch/main/lix/libfetchers/git.cc#L835-L837
localRefFile is never assigned a value, so it tries doing utimensat with "" as path. | 15:43:31 |
 Lily Foster | In reply to @monsterdruide1:matrix.org
To my understanding, it happens here:
https://git.lix.systems/lix-project/lix/src/branch/main/lix/libfetchers/git.cc#L835-L837
localRefFile is never assigned a value, so it tries doing utimensat with "" as path. that would be the warning, but for the error, would you happen to be on lix 2.94 or lower? (error is probably this line from release-2.94: <https://git.lix.systems/lix-project/lix/src/commit/e3ac0d9c19cff71d166e67d4fe11cbd7b65a1ffe/lix/libfetchers/git.cc#L830>) | 15:49:34 |
| Lily Foster | * that would be the warning, but for the error, would you happen to be on lix 2.94.x or lower? (error is probably this line from release-2.94: https://git.lix.systems/lix-project/lix/src/commit/e3ac0d9c19cff71d166e67d4fe11cbd7b65a1ffe/lix/libfetchers/git.cc#L830) | 15:49:45 |
| @monsterdruide1:matrix.org | Yes, I'm on
nix (Lix, like Nix) 2.94.2
I couldn't update anyways though, because that would require nix flake update lix 🙃 | 15:51:09 |
| Lily Foster | you could nix run nixpkgs#lixPackageSets.lix_2_95.lix -- flake update lix to unstuck yourself probably | 15:52:58 |
| Lily Foster | (i asked about version, because i had hit this and debugged the exact issue a few days ago, from packed-refs-only in lix clone being weird until https://git.lix.systems/lix-project/lix/commit/6bf187537ac094181b25ad96137e83cf31cfa356 inadvertently fixed it/made it only warn and not error and https://github.com/samueldr/lix-gha-installer-action/pull/20 meant my CI was unintentionally getting stuck running an older version of lix that did not have the fix...) | 15:56:53 |
| Lily Foster | * (i asked about version, because i had hit this and debugged the exact issue a few days ago, from packed-refs-only in lix clone being weird until https://git.lix.systems/lix-project/lix/commit/6bf187537ac094181b25ad96137e83cf31cfa356 inadvertently fixed it/made it only warn and not error and bug fixed by https://github.com/samueldr/lix-gha-installer-action/pull/20 meant my CI was unintentionally getting stuck running an older version of lix that did not have the fix...) | 15:57:37 |
| Lily Foster | In reply to @lily:lily.flowers
you could nix run nixpkgs#lixPackageSets.lix_2_95.lix -- flake update lix to unstuck yourself probably (let me know if this works or not! i think it should though) | 15:58:24 |
| @monsterdruide1:matrix.org | Will do once it finishes execution, thanks for the suggestion! | 16:00:04 |
| Lily Foster | (not sure why clones for specifically https://git.lix.systems/lix-project/lix (but not other repos on git.lix.systems) stopped having loose ref files in them (and only packed refs) but that's why the old code started choking on it | 16:01:54 |
| Lily Foster | * (not sure why clones for specifically https://git.lix.systems/lix-project/lix (but not other repos on git.lix.systems) stopped having loose ref files in them (and only packed refs) but that's why the old code started choking on it) | 16:02:03 |
| @monsterdruide1:matrix.org | I shouldn't keep a gdb session with lix open which locks the cache, causing the new command to get stuck, great!
Rebuilding my NixOS after that to apply the change (and going from lixPackageSets.stable to .latest) helped, it's not throwing the error on nix flake update lix anymore!
Just the warning about setting could not update mtime for file '': No such file or directory, which is probably fine then? | 16:15:18 |
| Lily Foster | yeah that warning is fine :) | 16:15:39 |
| @monsterdruide1:matrix.org | Great, just a classic case of "fixed on the latest version already" then, thanks for the help on getting my system back on track! | 16:16:25 |
|  Egor Loskutov joined the room. | 17:32:03 |
