!UNVBThoJtlIiVwiDjU:nixos.org

Staging

317 Members
Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen109 Servers

Load older messages


SenderMessageTime
3 Nov 2025
@k900:0upti.meK900 ^ 12:20:31
@k900:0upti.meK900 I think the correct resolution is to move the newly added version check down to meta.broken as Jo did in their big commit 12:21:02
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)Can't we just cherry-pick https://github.com/NixOS/nixpkgs/commit/89fd9025cfae7cab49ea36134640952ad553c4fa to staging-next individually and then accept the staging-next version explicitly for the conflicting files?12:21:04
@k900:0upti.meK900And the rest already applies cleanly12:21:47
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/commit/89fd9025cfae7cab49ea36134640952ad553c4fa#diff-87747fec8c7dfe5d924b47da9425f32fdc332203161b00ff7f754389d86b66be is the only change that doesn't12:22:06
@stepbrobd:matrix.orgStepBroBD problem solved? 12:22:23
@stepbrobd:matrix.orgStepBroBD scared me for a bit 12:22:30
@k900:0upti.meK900Well the problem will be solved if you agree this is the correct thing to do12:22:49
@k900:0upti.meK900And then I can just commit and push it12:22:54
@stepbrobd:matrix.orgStepBroBD yes 12:23:01
@k900:0upti.meK900OK cool12:23:05
@k900:0upti.meK900Thanks12:23:05
@stepbrobd:matrix.orgStepBroBD thank you for your service 12:23:16
@stepbrobd:matrix.orgStepBroBD hope i dont mess up again 12:23:22
@k900:0upti.meK900Again you did not mess up12:23:30
@k900:0upti.meK900This is normal staging process12:23:35
@stepbrobd:matrix.orgStepBroBD first time joining staging workflow
i'll keep lurk around here 👀
12:24:20
@k900:0upti.meK900 @Wolfgang Walther had some ideas in mind to reorganize the process so that there's no manual conflict resolution involved on our part 12:24:25
@k900:0upti.meK900And instead you have to submit another PR to staging branches with the conflicts resolved correctly12:24:42
@mtvkxsw9tngk:matrix.orgmtvkxsw9tngk joined the room.12:24:43
@wolfgangwalther:matrix.orgWolfgang WaltherEmily had those ideas and I just kept nodding.12:25:38
@k900:0upti.meK900But nothing implemented yet and honestly I am not super convinced it's the way to go because it's going to really confuse folks who are not familiar with staging and I'm getting carried away12:25:43
@k900:0upti.meK900Anyway all merged now and the automated trains can resume running cleanly, thanks for the help12:26:15
@ivy:faggot.shivyhow long does a staging cycle normally take?12:27:05
@k900:0upti.meK900Depends on how broken things are12:27:29
@k900:0upti.meK900And how much work ends up being scrapped due to some underlying changes being broken12:27:44
@k900:0upti.meK900Usually a week or so for a full world rebuild where nothing goes horribly wrong12:28:00
@k900:0upti.meK900Maybe a bit more these days since we build more things and also don't have quite as much capacity12:28:38
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) did you say coreutils rebuild because less is broken? 12:34:24
@k900:0upti.meK900I think the worst one we've had was a GCC rebuild like a week into a cycle?12:34:51

Show newer messages


Back to Room ListRoom Version: 6