| 8 Dec 2025 |
 raitobezarius | It seems you have Java applications, what happens if you comment them and rebuild? | 15:01:46 |
 Aijokey | and it helps | 15:38:10 |
| Aijokey | but also i found out something using kotlin and some android tools during building, even after I comment all android/jave pkgs | 15:39:18 |
| raitobezarius | In reply to @aijokey:matrix.org
but also i found out something using kotlin and some android tools during building, even after I comment all android/jave pkgs What is the something? | 15:42:20 |
 crop | https://git.lix.systems/lix-project/lix/issues/1069 | 15:42:24 |
| Aijokey | I dont know | 15:42:35 |
| Aijokey | maven? | 15:42:58 |
| Aijokey | But it also just dependencie not in my config | 15:43:44 |
 goldstein | (feel free to redirect me to the dev channel if it’s more appropriate there)
hi! I’ve found a divergence in behaviour between Lix and CppNix. when using fetchTree with git flakeref + ?ref=refs/tags/something, Lix and CppNix set the resulting .rev differently: Lix sets it to the hash of the tag itself, while CppNix sets it to the hash of the commit behind the tag. on the first glance, CppNix behaviour seems more sensible to me, since rev is usually the commit hash, but I’d like to know if it’s intentional. if it’s not, I’ll try to fix it. | 17:00:28 |
 Rutile (Commentator2.0) feel free to ping | this is known: https://git.lix.systems/lix-project/lix/issues/520 | 17:07:19 |
| goldstein | thanks for the link! | 17:07:45 |
