!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

Load older messages


SenderMessageTime
1 Jun 2024
@raitobezarius:matrix.orgraitobezarius Qyriad: jade_ we removed the testing code for multiple versions of Nix mentioned in https://git.lix.systems/lix-project/lix/issues/33 18:05:37
@raitobezarius:matrix.orgraitobezariusare our plans still to restore them somewhat?18:05:43
@raitobezarius:matrix.orgraitobezariusbefore 2.9018:05:46
@raitobezarius:matrix.orgraitobezariusor should we go and release 2.90 given that we have empirical confirmation that they work18:05:56
@raitobezarius:matrix.orgraitobezariusand move this to 2.9118:05:58
@raitobezarius:matrix.orgraitobezarius(a release blocker of 2.91, that is)18:06:04
@k900:0upti.meK900I keep saying that but Gerrit is terrible except for ONE THING it does really well and the fact that people keep using it says a lot about how important the one thing actually is 18:06:04
@k900:0upti.meK900(and how bad literally everyone else is at it, for some reason) 18:06:28
@pennae:matrix.eno.space⚠️ eldritch horrors operating in this area ⚠️ joined the room.18:08:54
@pennae:matrix.eno.space⚠️ eldritch horrors operating in this area ⚠️ changed their display name from pennae to ⚠️ eldritch horrors operating in this area ⚠️.18:09:06
@niko:conduit.rsnyanbinary joined the room.18:21:05
@raitobezarius:matrix.orgraitobezarius jade_: is there anything i can do to help you on the release engineering scripts you are working on? or take some efforts off you? 18:25:29
@raitobezarius:matrix.orgraitobezarius * jade_: is there anything i can do to help you on the release engineering scripts you are working on? or take some load off you? 18:25:38
@jade_:matrix.orgjade_
In reply to @raitobezarius:matrix.org
jade_: is there anything i can do to help you on the release engineering scripts you are working on? or take some load off you?
i am currently busy with guests here, but hm. i think one thing that would be good is if the installer build stuff were somehow nicely integrated into the overall releng scripts. but idk, hard to really point at easily separable tasks.
18:33:54
@draupnir:lix.systems@draupnir:lix.systemschanged room power levels.18:38:10
@jade_:matrix.orgjade_ I would also like to not need an arm mac to build the installer 18:39:38
@jade_:matrix.orgjade_at least for testing18:39:48
@raitobezarius:matrix.orgraitobezarius set the room topic to "(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.".18:51:27
@qyriad:katesiria.orgQyriad
In reply to@kloenk:kloenk.eu
only getting a You do not have the can-perform-mutations buildbot role. I just want to see some log what actually failed
Currently only existing contributors can see the buildbot logs — just becauase buildbot as it is doesn't have any way to allow only certain people to do things like forcibly cancel or restart arbitrary builds, which is something we intend to fix
21:19:19
@kloenk:kloenk.eukloenkah fair. can you tell me what it says? localy the check (only on x86 linux, everything else does not have a test) does succeed. so unsure what to do, or if it's just flakey21:21:54
@qyriad:katesiria.orgQyriadugh, a remote builder failure. restarted the build21:23:52
@qyriad:katesiria.orgQyriaddidn't realize that was your CL; we'll fix your permissions21:24:21
@pennae:matrix.eno.space⚠️ eldritch horrors operating in this area ⚠️the remote builder should get fixed again, sorry <,<21:25:29
@qyriad:katesiria.orgQyriadthere you go; you might have to log out and log back in, but you should have buildbot perms and issue triage perms in forgejo21:25:31
@tim:stratum0.orgdadada joined the room.21:26:25
@kloenk:kloenk.eukloenkah thanks works. good to hear that it's nothing with my change :)21:48:59
@qyriad:katesiria.orgQyriadas heads up, your change will probably be deferred until after we finish 2.9021:49:36
@kloenk:kloenk.eukloenkNo worries. I waited 4 years in nixcpp :p22:06:15
@charles:computer.surgeryCharles joined the room.22:31:41
@ma27:nicht-so.sexyma27

Question: is there any way in a DerivationGoal to find out whether you're in a daemon or in a nix-build as a root? I'm a little out of ideas since the store is always a LocalStore here and I didn't manage to write dynamic_cast<SimpleLogger> since that's not implemented in any of the headers.

Context: a while ago I submitted https://gerrit.lix.systems/c/lix/+/913 to get SSH errors in the stderr of a nix-build and I think I found a nicer solution than this (using logger->log basically in DerivationGoal::tryBuildHook).
THe idea is to still use writeStderr (to have errors actually appear in nix-daemon stderr) and to use logger to make it appear in the client's stderr. Then we can probably get rid of the log-fd=4 thingy, at least for ssh-ng (for legacy ssh tests are breaking badly and I'm not entirely sure why yet).

Any ideas? Or is my idea even reasonable?

22:46:03

Show newer messages


Back to Room ListRoom Version: 10