!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

416 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.139 Servers

Load older messages


SenderMessageTime
9 Jun 2024
@irenes:matrix.org@irenes:matrix.orgthe switch to the Meson build system is the progress in that direction so far09:53:00
@ma27:nicht-so.sexyma27 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:the-apothecary.clubjuliathat's a nixpkgs update, not lix13:35:27
@julia:the-apothecary.clubjulia * that's a nixpkgs update, not lix, see pkgs/top-level/aliases.nix 13:35:38
@delroth:delroth.netdelrothahhh sorry I bumped the nixpkgs version in the flake and clearly didn't test the devshell13:39:14
@delroth:delroth.netdelroththat's probably why13:39:17
@puck:puck.moepuckhrm, can we have a list of non-trivial things to check on these kinds of bumps? or maybe add devshell to checks13:40:18
@delroth:delroth.netdelrothbuilding the devshell in CI sounds like a good idea13:40:47
@delroth:delroth.netdelrothhttps://git.lix.systems/lix-project/lix/issues/38313:42:36
@puck:puck.moepuck(we like being able to get rid of these kinds of footguns ^-^)13:43:05
@delroth:delroth.netdelrothtbf I also have no clue why xonsh is in the devshell by default13:43:15
@puck:puck.moepuck 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:delroth.netdelrothTo ssh://gerrit.lix.systems:2022/lix ! [remote rejected] HEAD -> refs/for/main (n/a (unpacker error))13:44:57
@delroth:delroth.netdelroththat's a new one13:44:59
@delroth:delroth.netdelrotherror: remote unpack failed: error Missing tree e1aff8ff0d78351e5685efc04641fc558b50c2df13:45:30
@raitobezarius:matrix.orgraitobezariusTransient?13:45:43
@delroth:delroth.netdelrothit repro'd 3 times13:45:54
@ma27:nicht-so.sexyma27 delroth --no-thin helped me. 13:46:05
@raitobezarius:matrix.orgraitobezariusUh-huh13:46:06
@delroth:delroth.netdelrothbut after rebasing on latest main it worked13:46:07
@delroth:delroth.netdelrothhttps://gerrit.lix.systems/c/lix/+/1428 with the caveat that I tested that "nix develop" worked and that "xonsh" starts up in there, but nothing further13:46:29
@puck:puck.moepuck checking error_log, Missing tree e1aff8ff0d78351e5685efc04641fc558b50c2df 13:46:31
@raitobezarius:matrix.orgraitobezariusMaybe git fsck on the FS repo would be good as well or is that unrelated?13:47:01
@puck:puck.moepuck now there's something slightly cursed: that tree exists 13:47:23
@puck:puck.moepuckwait did we get rid of sandbox refs13:48:13
@puck:puck.moepuckthough, let's see13:51:20
@puck:puck.moepuck git fsck says it's fine, with exception of a few dangling commits 13:52:36
@delroth:delroth.netdelrothit's apparently a commonly reported gerrit bug13:54:10
@delroth:delroth.netdelrothso I wouldn't worry about it13:54:13
@puck:puck.moepuck(and a larger pile of unreachable commits)13:54:14

There are no newer messages yet.


Back to Room ListRoom Version: 10