| 20 Oct 2025 |
 Vladimír Čunát | aah, on the central Hydra machine (mimas). | 05:58:38 |
| Vladimír Čunát | But if I run the same on the builder itself, I do see a newer log. | 05:58:56 |
| Vladimír Čunát | 🤔 maybe that's how Hydra behaves normally on failure retries? But it's annoying. | 06:00:49 |
| Vladimír Čunát | I think I've seen this test derivation fail in three places already. | 07:42:39 |
| Vladimír Čunát | This test has 5 .meta.maintainers 😏 | 08:12:43 |
| Vladimír Čunát | I'll open a GitHub issue with the logs attached. | 08:12:53 |
| Vladimír Čunát | https://github.com/NixOS/nixpkgs/issues/453782 | 08:49:09 |
| Vladimír Čunát | ooh, it fails also on x86_64-linux | 08:57:35 |
| Vladimír Čunát | I just confused opensshTest with nixosTests.openssh 😕 | 08:57:50 |
 K900 | Are those not the same thing | 08:58:40 |
| K900 | Oh it's openssh's own tests | 08:59:13 |
| Vladimír Čunát | The failure got triggered just by openssh update. Well, details on that issue. | 09:45:14 |
| Vladimír Čunát | BTW, I generally wonder why maintainers relevant to a PR/package so often don't finish their backports and just leave the backport PR hanging indefinitely. | 11:53:28 |
 ElvishJerricco | heh, this is kinda funky. I based my 258.1 branch on my staging-next fix yesterday since it reverts the commit. Now that that commit has gone staging-next -> staging, github still shows it as one of the commits for the 258.1 branch in the PR. Weird. | 12:10:30 |
| ElvishJerricco | ah, just pushing an update to the commit timestamps of the two new commits fixed that | 12:14:09 |
| Vladimír Čunát | Yes, you need to force-push via git or rebase in the UI or something to make it refresh the commit list. | 12:15:46 |
|  eveeifyeve joined the room. | 12:41:30 |
| eveeifyeve | does anyone know when the next merge of staging to staging next is? | 12:42:00 |
| Vladimír Čunát | I don't think so 😅 | 12:44:09 |
| Vladimír Čunát | Why are you interested in that? | 12:44:25 |
| Vladimír Čunát | (maybe we can answer that) | 12:44:33 |
| eveeifyeve | I am trying to track when https://github.com/NixOS/nixpkgs/pull/453489 gets built by hydra. | 12:44:34 |
 dramforever | when we're done merging this staging-next to master | 12:44:55 |
| Vladimír Čunát | Well... there's also staging-next-25.05 possible. | 12:45:12 |
| Vladimír Čunát | I mean, we will have to do it at some point at least once. | 12:45:23 |
| Vladimír Čunát | And I don't think there will every be a "perfect moment". | 12:46:23 |
| Vladimír Čunát | * And I don't think there will ever be a "perfect moment". | 12:46:27 |
| Vladimír Čunát | (I'm even tempted to start it today.) | 12:46:49 |
| eveeifyeve | Well I was trying to build staging deps in a devshell and found this to be an issue with libedit:
error: builder for '/nix/store/hp66qyxi3s4y682xxhphz81hjmc0nm38-libedit-20251016-3.1.tar.gz.drv' failed with exit code 1;
last 12 log lines:
>
> trying https://thrysoee.dk/editline/libedit-20251016-3.1.tar.gz
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0curl: (6) Could not resolve host: thrysoee.dk
> Warning: Problem : timeout. Will retry in 1 second. 3 retries left.
> curl: (6) Could not resolve host: thrysoee.dk
> Warning: Problem : timeout. Will retry in 1 second. 2 retries left.
> curl: (6) Could not resolve host: thrysoee.dk
> Warning: Problem : timeout. Will retry in 1 second. 1 retry left.
> curl: (6) Could not resolve host: thrysoee.dk
> error: cannot download libedit-20251016-3.1.tar.gz from any mirror
For full logs, run:
nix log /nix/store/hp66qyxi3s4y682xxhphz81hjmc0nm38-libedit-20251016-3.1.tar.gz.drv
| 12:47:19 |
| Vladimír Čunát | I don't have that issue. | 12:48:23 |
