!UNVBThoJtlIiVwiDjU:nixos.org

Staging

388 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/128 Servers

Load older messages


SenderMessageTime
11 May 2026
@hexa:lossy.networkhexanvm, we have backport labels21:59:54
@hexa:lossy.networkhexathx21:59:54
12 May 2026
@eymeric:onyx.ovhEymeric joined the room.06:20:26
@flashonfire:lithium.ovhguillaume joined the room.06:35:58
@uku:rei.uku.moejulie joined the room.07:17:30
@uku:rei.uku.moejuliehi, i have a package i'd like to update, but it now depends on rust 1.95.0. should i wait for this staging cycle to complete and open a draft pr targeting master, or is there some procedure for updates like these?07:20:00
@k900:0upti.meK900You can target staging directly07:20:51
@k900:0upti.meK900Or staging-next, if Rust 1.95.0 is in that07:20:57
@uku:rei.uku.moejulieit is i believe07:21:17
@uku:rei.uku.moejuliethank you!07:21:19
@weethet:catgirl.cloudWeetHetTargeting staging is cursed, you need to build a lot of stuff07:24:21
@vcunat:matrix.orgVladimír ČunátWell, if you need package update which isn't built by Hydra yet, you don't have much choice really.07:30:29
@vcunat:matrix.orgVladimír ČunátBut generally you can put your mass-rebuild commits atop some master commit and select staging as the merge target.07:31:05
@vcunat:matrix.orgVladimír ČunátOf course there's a risk of conflicts, but usually it's not high. And it minimizes the amount of rebuilds done locally.07:31:34
@emilazy:matrix.orgemily @k900:0upti.me do you feel like cross-building some Qt stuff for https://github.com/NixOS/nixpkgs/pull/518539 12:40:08
@emilazy:matrix.orgemily(does Qt exercise Meson anywhere?)12:40:17
@k900:0upti.meK900 Not directly 12:41:10
@k900:0upti.meK900 Qt cross is already a fuck 12:41:16
@k900:0upti.meK900 It's probably fine to make it more fuck 12:41:35
@emilazy:matrix.orgemilyit's more about not knowing whether CMake/Meson cross actually work at all after this yet12:46:48
@emilazy:matrix.orgemily(though they ought to)12:46:51
@k900:0upti.meK900 Cmake cross never works, it usually just happens to kinda do the right thing by complete accident 12:48:13
@emilazy:matrix.orgemilyok but the PR is literally moving around stuff we have to make CMake cross work :P13:28:21
@me:indeednotjames.comemilyI can fix this tomorrow or the day after tomorrow19:58:42
13 May 2026
@emilazy:matrix.orgemily vcunat: just checking on this? not sure when the first 26.11 cycle is due 16:38:32
@leona:leona.isleonaat least not in the next 7-10 days ^^16:42:24
@leona:leona.isleona* at least not in the next 7 days ^^16:42:38
@vcunat:matrix.orgVladimír Čunát The current staging won't reach 26.05, so I guess you can already merge changes in there? 16:47:58
@emilazy:matrix.orgemily but it's already building for x86_64-darwin, right? 16:48:12
@emilazy:matrix.orgemilyso makes sense to do it next cycle instead16:48:15

Show newer messages


Back to Room ListRoom Version: 6