| 1 Feb 2026 |
 BMG | So to be clear, narinfos-nixos-images-2026-01-06T01-13Z.parquet is the proposed deletion, narinfos-nixos-images-dangling-refs-2026-01-06T01-13Z.parquet is anything that referred to the entries in the first file. | 16:57:45 |
| BMG | I'm gonna test with a dry run to be sure there's no issues with the dangling refs format | 16:59:07 |
| BMG | Had to fix a schema issue, pushed an update to the dataset and just tested it with a dry run:
{
"dry_run": true,
"targets": {
"nar_infos": 105944
},
"removed": {
"nars": 105944,
"nar_infos": 105944,
"errors": 0
},
"missing_in_s3": {
"nars": 0,
"nar_infos": 0
}
}
| 17:07:55 |
| 2 Feb 2026 |
 Arian | If you are nervous about correctness we could enable bucket versioning + a Lifecycle rule that moves deleted objects into glacier | 08:30:17 |
| Arian | ```
{
"Rules": [
{
"Id": "archive-deleted-objects",
"Status": "Enabled",
"NoncurrentVersionTransitions": [
{
"NoncurrentDays": 0,
"StorageClass": "GLACIER_IR"
}
]
}
]
}``` | 08:30:25 |
| Arian | @joerg:thalheim.io are you still in Brussels today or tomorrow? | 08:31:22 |
 Mic92 | Arian: I am. | 08:56:48 |
| Mic92 | I am on the guix days. Maybe we can meet in the Numtide venue in the evening? | 08:57:25 |
| Mic92 | * I am on the guix days the next two days. Maybe we can meet in the Numtide venue in the evening? | 08:57:34 |
| Mic92 | I actually wanted to ask regarding the bucket versioning, because the implications are a bit unclear to me yet. | 08:58:04 |
| Mic92 | okay, we might than actually want to remotve the dangling refs dataset before we run the nixos images one. | 09:00:44 |
| Mic92 | * Arian: I am. I will leave on Wednesday | 09:00:50 |
| 4 Feb 2026 |
|  Corngood joined the room. | 00:24:13 |
| Corngood | I've got a couple of build failures due to free space that I'd like to restart:
https://hydra.nixos.org/build/320776458
https://hydra.nixos.org/build/320776631
Is this the right place to ask about that? | 00:28:53 |
 hexa | restarted | 00:37:11 |
| Corngood | Thanks. Those particular builds are now showing as passed, but if I look at a build like https://hydra.nixos.org/build/320776594, it shows a propagated failure from one of those previously failing builds, and it doesn't look like it's queued. Is there anything I need to do about those, or will they sort themselves out? | 14:32:54 |
 Vladimír Čunát | Unfortunately there are two other options I know about
- restart each of these manually
- restart completely all non-succeeding jobs in an eval
| 14:40:24 |
| Vladimír Čunát | * Unfortunately there are only two other options I know about
- restart each of these manually
- restart completely all non-succeeding jobs in an eval
| 14:40:31 |
| Vladimír Čunát | * Unfortunately there are only two other options I know about:
- restart each of these manually
- restart completely all non-succeeding jobs in an eval
| 14:40:34 |
| Vladimír Čunát | (I restarted at least this one in particular now.) | 14:40:54 |
| 5 Feb 2026 |
| Vladimír Čunát | nixos-unstable-small is blocked. Indexing broke due to some xorg changes, apparently. | 07:39:28 |
| Vladimír Čunát | $ nix-channel-index -o /home/hydra-mirror/scratch/release-nixos-unstable-small/nixos-26.05pre940588.d88ce2e37ee0/unpack/nixos-26.05pre940588.d88ce2e37ee0/pr>
+ querying available packageserror: QueryPackages { source: Command("nix-env failed with exit status: 1:\nerror: attribute 'xorg' in selection path 'xorg' no>
Command failed with code (2) errno (0).
| 07:40:06 |
 K900 | Oh balls | 07:52:20 |
| K900 | It's hardcoded in nix-index too | 07:53:03 |
| K900 | Oh wait no it's not | 07:53:58 |
| K900 | Oh wait no it is | 07:54:58 |
| K900 | Balls | 07:54:59 |
| K900 | https://github.com/nix-community/nix-index/blob/master/src/listings.rs#L26 | 07:55:00 |
| K900 | I am very migraine can someone do the dance | 07:55:11 |
| Vladimír Čunát | Deleting that line sounds easy enough. | 07:57:17 |
