!UNVBThoJtlIiVwiDjU:nixos.org

Staging

383 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/124 Servers

Load older messages


SenderMessageTime
18 May 2026
@limwa:matrix.orgAndré Lima Fix for nixosTests.misc: https://github.com/NixOS/nixpkgs/pull/521677 19:25:16
@limwa:matrix.orgAndré Lima Also, regarding the nixosTests.installer.simple test, I'm seeing that the installer can't resolve DNS queries. Is this normal/intended? 21:03:49
@k900:0upti.meK900Yes21:04:37
@k900:0upti.meK900The installer runs fully offline21:04:41
@k900:0upti.meK900The idea is that everything required for the base install is on the image already21:04:50
@k900:0upti.meK900So things that are missing need to be added to the image21:04:56
@limwa:matrix.orgAndré LimaOkay, thank you!21:07:56
19 May 2026
@limwa:matrix.orgAndré LimaI've updated this PR. It now fixes all of the nixosTests failing here: https://hydra.nixos.org/eval/182546400:48:52
@marienz:matrix.org@marienz:matrix.org joined the room.13:31:40
@marienz:matrix.org@marienz:matrix.org changed their display name from Marien Zwart to marienz.13:33:31
@marienz:matrix.org@marienz:matrix.org

regarding the python3Packages.narwhals build failure: https://github.com/marienz/nixpkgs/commit/959bdf4b779161340a00694fd075b91fbc14dc9a makes it build (by applying three upstream commits to tests), but I'm not familiar with that package so I don't know how to test it further. Is it helpful for me to send that as a PR (and if so: directly against staging-next or some other branch first), or better to wait for the maintainer / someone else more familiar with it?

(I'm just keeping an eye on that staging-next merge because it has some other stuff I'm looking forward to)

13:39:13
@grimmauld:m.grimmauld.deGrimmauld (any/all)fixes to things regressed in a cycle go to staging-next, generally13:50:19
@grimmauld:m.grimmauld.deGrimmauld (any/all)there is very few exceptions (e.g. platform specific regressions where one platform already had a successful build we'd be throwing away, then it depends)13:51:00
@marienz:matrix.org@marienz:matrix.orgthanks, sent https://github.com/NixOS/nixpkgs/pull/52195113:59:28
@leona:leona.isleona hydra also agrees that all tests of small's tested are fixed 14:24:06
@tbutter:matrix.orgtbutter joined the room.18:05:13
@uku:rei.uku.moejulie changed their display name from uku to julie.18:23:11
20 May 2026
@r-burns:matrix.orgr-burnshttps://github.com/NixOS/nixpkgs/pull/52213603:20:34
@dramforever:matrix.orgdramforeverlooks like https://github.com/NixOS/nixpkgs/pull/517138 missed the current staging-next04:29:59
@jkarlson:kapsi.fiEmil Thorsøeif this only affects i686 build that has now failed, anything built after that has not been built?04:31:43
@dramforever:matrix.orgdramforeveri think to avoid git troubles we should just merge 26a26d898abd into staging-next04:36:35
@dramforever:matrix.orgdramforever* i think to avoid git troubles we should just merge the head of #517138 namely 26a26d898abd into staging-next04:36:49
@dramforever:matrix.orgdramforever(also posted on pr)04:37:06
@vcunat:matrix.orgvcunatI don't think it helps git merge troubles, but it seemed cleaner not to have duplicate commits in the history of the same branch.05:39:44
@vcunat:matrix.orgvcunatSo I remerged it.05:39:59
@vcunat:matrix.orgvcunat* So I remerged the old commit.05:40:08
@vcunat:matrix.orgvcunat staging-next merged. 11:50:44
@k900:0upti.meK900UHhh11:51:46
@k900:0upti.meK900Abort11:51:47
@k900:0upti.meK900ABORT11:51:50

Show newer messages


Back to Room ListRoom Version: 6