| 30 Jun 2026 |
 K900 | Ughhhhh the varlink interface works | 09:53:22 |
| K900 | But we can't rely on it | 09:53:24 |
| K900 | ❯ sudo varlinkctl call /run/systemd/io.systemd.BootControl io.systemd.BootControl.Install '{"operation":"update"}'
Method call io.systemd.BootControl.Install() failed: Stale file handle
{
"origin" : "linux",
"errno" : 116,
"errnoName" : "ESTALE"
}
| 09:54:25 |
| K900 | ESTALE here means "nothing to do" | 09:54:34 |
| K900 | I wonder if it makes sense to just do varlink | 09:56:23 |
| K900 | And fall back to a direct bootctl invocation | 09:56:30 |
| K900 | The only situation it should matter is in a chroot | 09:57:03 |
| K900 | ElvishJerricco need your thonk | 09:59:03 |
| K900 | Also anyone else want to bash their head against paperless | 10:00:16 |
| K900 | Or should I just rip a bisect | 10:00:20 |
| K900 | And get back to you in 3-5 business days | 10:00:27 |
 guillaume | I can start a bisect | 10:21:24 |
| K900 | Ahead of you | 10:21:43 |
| K900 | 
Download Unfortunately, | 10:21:59 |
 cSanthiago | I don't wanna bother, I see you are doing a lot of work on this merge, this is the first one I am trying to follow up... I am failing to understand how you pick the packages to fix.
I try to look on asnible, but at the end it looks like is failing just becouse one dependancy in queued, and ansible is missing it.
If it is a complex answer I can ask again after the merge is done.
| 10:40:36 |
| K900 | The answer is mostly "things that break a lot of other things" | 10:41:04 |
| K900 | And also, realistically, "things we personally use" | 10:41:13 |
| cSanthiago | (L)
| 10:41:30 |
| K900 | https://malob.github.io/nix-review-tools-reports/ has autogenerated statistics for what packages block the most other things | 10:41:59 |
| cSanthiago | Last one, for python stuff it looks like works on eventual consistency, is it correct? at some point the dependacies will be built and the package build will not fail
| 10:43:09 |
| K900 | Generally, the package should not start being built | 10:43:23 |
| K900 | Until all of its dependencies are | 10:43:27 |
| K900 | If it complains about a dependency being missing, that's likely a garbage collector race condition that we're still trying to track down | 10:43:51 |
| cSanthiago | got it, thank you
| 10:44:23 |
| cSanthiago | I looked at this link several times, but went directly to x86, I blinded myself
| 10:45:11 |
 Grimmauld (any/all) | My server config just finished building on my rock | 11:02:13 |
| Grimmauld (any/all) | we'll see whether it works after a reboot | 11:02:26 |
| cSanthiago | I will be quite after this one: https://hydra.nixos.org/build/333537138#tabs-buildsteps, hydra has two build steps for python httpio, one failed and one succeed, when hydra tries to build ansible it fails because httpio reported the failed status https://hydra.nixos.org/build/333512105.
is this assumption correct?
| 11:05:00 |
| K900 | No, that's a queue runner bug | 11:08:14 |
| K900 | Anyway, you should not worry about it right now | 11:08:21 |
