| 9 Jun 2024 |
 jade_ | alrighty it is fixed | 00:14:39 |
|  lunarequest ⚡️ joined the room. | 03:49:00 |
| jade_ | i have got so deep in the yakshaving stack that i have written a docker image merging tool | 06:42:06 |
 delroth | In reply to @delroth:delroth.net
is there already a hydra fork somewhere which builds with Lix? (or does it build without changes? I doubt so) just asking again before I spend some time porting stuff - since I didn't get any replies really yesterday | 08:44:32 |
| jade_ | In reply to @delroth:delroth.net
just asking again before I spend some time porting stuff - since I didn't get any replies really yesterday i haven't heard of one so far | 08:49:41 |
| jade_ | there is a very limited set of people who would do such a thing | 08:50:05 |
| delroth | I happen to be one of them :) great, I'll get started | 08:52:07 |
| delroth | (really I got started already, it's just I hit the first non trivial hurdle so it was worth checking again...) | 08:52:29 |
| jade_ | https://git.lix.systems/lix-project/hydra has been made and you have write perms, have fun! (maybe worth renaming master->main when you migrate) | 08:55:25 |
| jade_ | * https://git.lix.systems/lix-project/hydra has been made and you have write perms, have fun! (def worth renaming master->main when you migrate) | 08:55:32 |
| delroth | already done so :p | 09:03:36 |
|  shard joined the room. | 09:35:57 |
| shard | Hello everyone, just discovered lix yesterday. I'm wondering if there's already any work started for transitioning to a Rust codebase? I don't see any i the existing repo.
Would love to help if this is something that needs more attention to it - now or in the future | 09:42:13 |
| shard | * Hello everyone, just discovered lix yesterday. I'm wondering if there's already any work started for transitioning to a Rust codebase? I don't see any i the existing repo.
Would love to help if this is something that needs more attention to it - now or in the future (from what I've seen it's probably too early to do any work on the Rust part?) | 09:50:19 |
 @irenes:matrix.org | the switch to the Meson build system is the progress in that direction so far | 09:53:00 |
 ma27 | last week I didn't have time for Lix hacking, so I may be a little out of date, but are you aware of error: 'xonsh-unwrapped' was incorporated into xonsh code; call xonsh directly instead. when opening the devshell?
worked around it by doing what the error told me, but don't really know if that even makes sense (and this was purely to get my env back up), so asking here first :) | 13:24:49 |
 julia | that's a nixpkgs update, not lix | 13:35:27 |
| julia | * that's a nixpkgs update, not lix, see pkgs/top-level/aliases.nix | 13:35:38 |
| delroth | ahhh sorry I bumped the nixpkgs version in the flake and clearly didn't test the devshell | 13:39:14 |
| delroth | that's probably why | 13:39:17 |
 puck | hrm, can we have a list of non-trivial things to check on these kinds of bumps? or maybe add devshell to checks | 13:40:18 |
| delroth | building the devshell in CI sounds like a good idea | 13:40:47 |
| delroth | https://git.lix.systems/lix-project/lix/issues/383 | 13:42:36 |
| puck | (we like being able to get rid of these kinds of footguns ^-^) | 13:43:05 |
| delroth | tbf I also have no clue why xonsh is in the devshell by default | 13:43:15 |
| puck | not sure either; jade_ added it and i suspect it might be to deal with an artifact of how devshells work (Qyriad?) | 13:44:31 |
| delroth | To ssh://gerrit.lix.systems:2022/lix
! [remote rejected] HEAD -> refs/for/main (n/a (unpacker error)) | 13:44:57 |
| delroth | that's a new one | 13:44:59 |
| delroth | error: remote unpack failed: error Missing tree e1aff8ff0d78351e5685efc04641fc558b50c2df | 13:45:30 |
 raitobezarius | Transient? | 13:45:43 |
