!UNVBThoJtlIiVwiDjU:nixos.org

Staging

318 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
12 Oct 2025
@wolfgangwalther:matrix.orgWolfgang WaltherRe-using the existing backport tools; I like. This makes any investments into these pay off in more ways.16:05:50
@emilazy:matrix.orgemilyFWIW, we could still do the fancy "PR with the conflicts up so you can review them before diving in" thing, by making it work for all label-based backports.16:06:35
@emilazy:matrix.orgemilyi.e., a backport label never fails, it just sometimes produces a PR with conflict markers.16:06:43
@emilazy:matrix.orgemilyand then that would also work for backports to release branches, which would be nice.16:06:52
@emilazy:matrix.orgemilyso yeah, I think a backporting approach is strictly more consistent/makes better use of our tooling investments.16:07:12
@wolfgangwalther:matrix.orgWolfgang WaltherSo I guess this will be the first thing to work on. This can be non-blocking and purely informative at first. Once it works, it can be enforced.16:08:40
@emilazy:matrix.orgemilythat seems useful regardless of workflow16:14:49
@emilazy:matrix.orgemily but … it'd be good to know if K900 is thinking of something we're missing here wrt the workflow, too 16:15:07
@emilazy:matrix.orgemily(I am guessing just a communication problem about what the flow would actually be but I could be wrong)16:15:32
@k900:0upti.meK900 I'm at the vet, will write longer words in a bit 16:15:33
@yuka:yuka.devYureka (she/her)I like the idea16:25:30
@yuka:yuka.devYureka (she/her)So, spectrum really needs a fix for pkgsMusl.iproute2 in the current staging-next16:26:31
@yuka:yuka.devYureka (she/her) *

anyways

So, spectrum really needs a fix for pkgsMusl.iproute2 in the current staging-next

16:26:39
@yuka:yuka.devYureka (she/her)it's expensive rebuilds-wise16:26:40
@yuka:yuka.devYureka (she/her)or we can make it conditional and then immediately revert and do a proper fix on staging yada yada16:27:02
@yuka:yuka.devYureka (she/her)this is the high rebuilds solution: https://github.com/NixOS/nixpkgs/pull/45133816:27:11
@yuka:yuka.devYureka (she/her) * or we can make it conditional and then immediately revert and do a proper fix on staging yada yada 16:27:29
@yuka:yuka.devYureka (she/her)someone merged it16:53:56
@yuka:yuka.devYureka (she/her)we can still revert and go the low rebuild count path16:54:18
@yuka:yuka.devYureka (she/her) * 16:54:23
@yuka:yuka.devYureka (she/her) * 16:54:39
@k900:0upti.meK900I've unmerged16:54:53
@k900:0upti.meK900It didn't get through the queue16:54:56
@k900:0upti.meK900We don't really want the 20k rebuilds at this point16:55:21
@yuka:yuka.devYureka (she/her)yep16:55:22
@ihar.hrachyshka:matrix.orgIhar Hrachyshkahow does one estimate when the next staging-next -> master will happen? (e.g. to determine if a temporary fix in master for a build failure is due while we wait for next->master to happen)16:59:54
@matthewcroughan:defenestrate.itmatthewcroughan joined the room.17:00:39
@k900:0upti.meK900Usually just ask here17:01:04
@k900:0upti.meK900I'd say we're looking at middle of next week17:01:22
@k900:0upti.meK900At the earliest17:01:25

Show newer messages


Back to Room ListRoom Version: 6