!UKDpaKNNsBpOPfLWfX:zhaofeng.li

Colmena

324 Members
A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena111 Servers

You have reached the beginning of time (for this room).

SenderMessageTime
24 Jun 2022
@hexa:lossy.networkhexa * and colmena seems to upload secrets with uploadAt=post-activation on applies with goal=boot directly after uploading the closure 13:17:07
@hexa:lossy.networkhexaah, reboot handling is part of 0.4.013:22:30
@hexa:lossy.networkhexa
In reply to @linus:schreibt.jetzt
Just reconfigure then :D
lol nope. can't reconfigure interfaces that don't exist, because of missing prerequisites 		15:10:01
@hexa:lossy.networkhexaso restarting networkd it is15:10:05
@zhaofeng:zhaofeng.liZhaofeng Li
In reply to @hexa:lossy.network
and colmena seems to upload secrets with uploadAt=post-activation on applies with goal=boot directly after uploading the closure
Yeah, the behavior of uploadAt=post-activation should probably be special-cased for --reboot 		18:06:02
@hexa:lossy.networkhexastrictly speaking: activation happens at boot time for goal=boot19:18:46
@hexa:lossy.networkhexaso don't upload secrets in that case unless --reboot is given19:19:14
@hexa:lossy.networkhexa * so don't upload post-activiation secrets in that case unless --reboot is given19:19:22
@hexa:lossy.networkhexa * so don't upload post-activiation secrets in that case unless --reboot is given and then post-reboot 😄19:19:26
25 Jun 2022
@winterqt:nixos.devWinter (she/her)

So I'm trying to debug a weird issue.

home-manager revisions, for at least a few months now(???), have failed to build their nmd fetcher derivation when building for x86_64-linux with Colmena's build on target feature, when the system != x86_64-linux. The derivation in question is defined here.

HM commit e66f0ff69a6c0698b35034b842c4b68814440778 suddenly fixes the fetching of this derivation, by merely changing the commit hash. The diff between the failing and the succeeding derivations is just as you'd expect: just the hashes and revisions change, nothing else.

The error that's occurring with these faulty revisions are error: a 'x86_64-linux' with features {} is required to build '/nix/store/7fhf5jvnmz8wpy38v44j5cfn7mgxg7kj-nmd.drv', but I am a 'aarch64-darwin' with features {benchmark, big-parallel, nixos-test} (7f... is failing in the diff). They both have system = x86_64-linux in the derivation, so what's going on?

16:55:50
@zhaofeng:zhaofeng.liZhaofeng LiAnother person [encountered the same thing](https://matrix.to/#/!BgJZHVOYkwVcEKLAyM:nixos.org/$pYUmOSAIpDOIbLl4q2TMc-0iyKrimWZfnFQi4Fdm6RA?via=zhaofeng.li&via=matrix.org&via=matrix.eno.space) in the deployment channel. It's a bit weird that it worked before.20:58:32
@zhaofeng:zhaofeng.liZhaofeng LiIs it possible that the original output was cached somehow?20:58:55

Show newer messages

Back to Room ListRoom Version: 6