8 Nov 2024 |
diniamo | Nop, it's still trying to build it even if I use a local ref | 20:50:11 |
Acid Bong | I specified the commit and it warned me that i'm not a trusted user for that operation | 20:52:38 |
Acid Bong | your remote repo seems to work | 20:52:47 |
@aloisw:kde.org | In reply to @acidbong:envs.net I specified the commit and it warned me that i'm not a trusted user for that operation If you're not trusted user, adding substituters client-side is not going to work. | 20:56:21 |
Acid Bong | In reply to @aloisw:kde.org If you're not trusted user, adding substituters client-side is not going to work. i meant it finally recognized that the flake sets additional substituters | 21:00:04 |
diniamo | welp, updated lix, and still no | 21:01:02 |
diniamo | no clue what to do at this point | 21:01:07 |
diniamo | it works on nixpkgs lix as well | 21:19:50 |
diniamo | could it be the stupid patch I use | 21:19:53 |
9 Nov 2024 |
@aloisw:kde.org | What is the patch? | 04:44:58 |
@aloisw:kde.org | I see you already reported a bug and it's a regression I introduced, so I will look into it. | 05:00:48 |
Ramses 🇵🇸 | I noticed that the lix-daemon is not properly exiting when a machine gets shut down, systemd prints a message all the way at the end of the boot process, that it's waiting for the process to exit | 06:40:05 |
Ramses 🇵🇸 | Download 21632.jpg | 06:40:24 |
Ramses 🇵🇸 | It forcefully kills it eventually, but this slows down reboots considerably | 06:41:05 |
Acid Bong | In reply to @rvdp:infosec.exchange sent an image. what version and did you install it from source or from nixpkgs? | 07:10:18 |
diniamo | In reply to @aloisw:kde.org I see you already reported a bug and it's a regression I introduced, so I will look into it. Thanks a lot. Yeah, the patch is irrelevant, I can reproduce it on the latest commit, and could clearly bisect it. | 08:13:27 |
Ramses 🇵🇸 | In reply to @acidbong:envs.net what version and did you install it from source or from nixpkgs? I'm building from main. I update more or less daily, but this process might have been running for a while. The last time I rebooted was a week ago, so it must be running a commit from the last week on main | 08:48:52 |
Ramses 🇵🇸 | This is on NixOS | 08:49:52 |
aidalgol | In reply to @sigmasquadron:matrix.org i like nixd This is really good. Thanks for the recommendation. | 19:45:58 |
olivia | is this situation a bug?
1. I bump the flake lockfile in repo A 2. I update flake.nix in repo B to point to local repo A (with a bumped lockfile) instead of remote 3. trying to build things in repo B uses the old versions of transitive dependencies through repo A rather than the new ones 4. nix flake update B in repo A fixes it | 22:50:54 |
olivia | (I'm not using inputs.A.follows in B) | 22:53:31 |
olivia | is this situation a bug?
1. I bump the flake lockfile in repo A 2. I update flake.nix in repo B to point to local repo A (with a bumped lockfile) instead of remote 3. trying to build things in repo B uses the old versions of transitive dependencies through repo A rather than the new ones 4. nix flake update A in repo B fixes it | 22:53:38 |
aidalgol | Are you committing after step 1? | 22:57:56 |
olivia | yes | 22:58:19 |
aidalgol | I think nix flake update A fixes it because updating the input in repo B's flake.nix will only bump the rev for that input, but the locked transitive dependencies will be left unchanged. | 23:00:51 |
olivia | In reply to@aidalgol:matrix.org I think nix flake update A fixes it because updating the input in repo B's flake.nix will only bump the rev for that input, but the locked transitive dependencies will be left unchanged. yeah, that is what appeared to happen | 23:01:09 |
aidalgol | I'm not sure whether that's a bug or by design. Heck, I'm not sure anyone knows what's by design in flakes at this stage. :P | 23:01:15 |
olivia | lol | 23:01:20 |
olivia | yeah I asked because wasn't sure whether this was by design :( | 23:02:19 |