DevOS | 35 Members | |
| Seeking help and geeking out together on https://github.com/divnix/devos & https://github.com/divnix/digga | 10 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Sep 2021 | ||
Indeed! I would tend to say that would be makes, though. I'm just exploring it these days, but it seems relatively generalizable. For example, I was musing about a scheduler / orchestrator interface, so that "tasks" can ultimately include "production workloads" on one hand or "pipeline jobs" on the other, such as CI jobs, ML jobs or ETL jobs. | 13:35:05 | |
| 15:47:10 | ||
| Hello! Have been trying to get into using DevOS for a little while now, however recently I've run into problems with things apparently not being found. Currently, I'm having an issue where it seems like any command building something (bud build, bud vm, etc.) give an error saying that Aside from that, I'm also having issues where when starting I've tried to dig around and find why these all aren't defined, but I have gotten nowhere in my search so far. I can provide any system information as needed. | 15:52:34 | |
I think I might have actually fixed the problem, and man do I feel stupid. I changed the channel I used from nixos to latest, however in doing that I excluded the overlays containing the stuff that I need, which I think ended up causing those errors. | 17:43:14 | |
| It still seems like there is a bug. You shouldn't have to use a specific channel with bud. Or maybe your nixos channel was just too far behind for bud. | 17:54:30 | |
Nah it was entirely my fault. I set nixos.hostDefaults.channelName = "latest", and the latest input/channel in the flake didn't have the overlays | 17:59:16 | |
I changed that before I realized "I can just change nixos to unstable", but I forgot to change it back, which ended up breaking things since the overlays were missing | 17:59:48 | |
devshell deps are rebuilding after reboots for me, even without me touching the lock file - do you have an idea what could be the reason? I’d like to have the build outputs cached, but it seems they are lost upon reboot. gc? 🤨 | 19:50:44 | |
I tried adding the —delete-older-than 14d option to gc, will see if that helps | 19:52:30 | |
| 16 Sep 2021 | ||
any reason why nix build for a rust package in devos would produce anything? any way to get something more verbose? | 18:55:12 | |
| i'm using nvfetcher | 18:55:16 | |
| trying to use lib.fakeSha256 for CargoSha256 | 18:58:08 | |
| 21:30:43 | ||
| 17 Sep 2021 | ||
teutat3s: it looks like we are still using the use flake directive in .envrc. Are you using direnv to enter the shell? If so, one explanation could be that you don't have nix-direnv properly available and so it's falling back to the old use nix directive which does not add the shell as a gc root and so is frequently garbage collected | 00:38:04 | |
| ultranix: did you mean to ask wouldn't produce anything? I can't make sense of your question otherwise? | 00:39:14 | |
| 18 Sep 2021 | ||
| 20:50:46 | ||
| 19 Sep 2021 | ||
https://github.com/fluidattacks/makes/pull/584 - work on bud was the inspiration. | 19:10:11 | |
| 20 Sep 2021 | ||
| 06:46:43 | ||
| Hi to all,
This is the line 12. | 10:31:53 | |
| If I run
| 10:39:52 | |
I think that the reason is that bud tries to run nixos-rebuild with the --flake option but an version that doesn' | 10:59:11 | |
* I think that the reason is that bud tries to run nixos-rebuild with the --flake option but an version that doesn't support flake. | 10:59:33 | |
| * I think that the reason is that `bud` tries to run `nixos-rebuild` with the `--flake` option but this version that doesn't support flake. | 11:03:53 | |
bud runs commands reproducibly in a complete isolated environment. So the only thing that can cause that, is as you correctly deducted, a variation of the binary itself in the nixpkgs version that bud uses. | 12:07:00 | |
bud.inputs.follows.nixpkgs = "nixos" (as in recent DevOS) instructs to use the same nixpkgs as uses DevOS as nixos input. | 12:08:58 | |
That, in turn is pinned to releas-21.05 by default. | 12:09:42 | |
| If within this setup, it's not working, then it's a bug. 🤕 | 12:10:01 | |
If you're trying to use a different nixos version, it might work if you remove that line with follows since bud itself is pinned to nixos-21.05 if not overridden. | 12:12:06 | |
But that assumes that this nixos-21.05' nicos-rebuild is actually compatible with that other nixos version. I wouldn't give an unconditional guarantee, but probably it is. | 12:13:22 | |
In reply to @blaggacao:matrix.orgThis would work because this way I'm going to use the nixos-21.05 commit inside the bud's flake.lock, right? | 12:14:26 | |