!UNVBThoJtlIiVwiDjU:nixos.org

Staging

349 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/113 Servers

Load older messages


SenderMessageTime
24 Feb 2026
@makefu:fairydust.spacemakefuis staging-next more "fresh" than master?17:38:26
@k900:0upti.meK900No17:39:36
@k900:0upti.meK900staging-next is currently behind master, as Hydra is building staging-25.1117:39:45
@k900:0upti.meK900We should have the next staging-next cycle probably somewhere around the end of the week17:40:02
@makefu:fairydust.spacemakefu the issue still exists in master when trying to build calibre 17:52:33
@k900:0upti.meK900Yes, and the fix is in staging17:52:51
@k900:0upti.meK900Not staging-next17:52:52
@k900:0upti.meK900Which is ahead of master17:52:55
@makefu:fairydust.spacemakefuah!!!17:53:06
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#staging17:53:13
@makefu:fairydust.spacemakefuokay thanks, that makes more sense17:53:13
@vcunat:matrix.orgvcunatIt's unlikely to happen this week.17:55:59
@makefu:fairydust.spacemakefu so when i am checking build failures in unstable because i did nix flake update nixpkgs and now my system does not build i should generally check both channels, staging and master if the package builds? or was calibre special that it needed fixing via the staging branch? 17:59:49
@vcunat:matrix.orgvcunat staging tends to be hard to check. You'd be doing lots of building work. 18:01:12
@vcunat:matrix.orgvcunatAnd it more often breaks things than fixes 😅18:01:51
@k900:0upti.meK900 Calibre wasn't special, but qmake in general was 18:01:53
@weethet:catgirl.cloudWeetHetYou can always overlay the package to fix the build yourself (worst case use it from an earlier nixpkgs instance) and wait for the fix to propagate to unstable and realistically that's all you need to care about if you're not interested in contributing big changes that would touch staging18:04:10
@fabianhjr:matrix.orgFabián Heredia
In reply to @k900:0upti.me
Calibre wasn't special, but qmake in general was
How many rebuilds is the qmake fix currently in staging?
18:04:49
@k900:0upti.meK900 About 5k 18:09:03
@weethet:catgirl.cloudWeetHetDid the effort to make stdenv non-cc by default die out?18:18:54
@weethet:catgirl.cloudWeetHetAnd make cc just a normal package18:19:21
@vcunat:matrix.orgvcunatRedacted or Malformed Event18:22:55
@ar:is-a.catari ❄ joined the room.18:41:30
@makefu:fairydust.spacemakefui will do it like this then, i am mostly only trying to keep my maintained packages working. This is why i would like to know if there are big fixes ongoing in staging to avoid duplicate work or effort which cannot realistically be fixed on package level19:18:02
@fabianhjr:matrix.orgFabián HerediaI feel like it would be acceptable to go directly to unstable if it is mostly unbreaking19:40:34
@fabianhjr:matrix.orgFabián Herediato avoid the wait for the next staging-next cycle19:40:47
@k900:0upti.meK900Very little of it is unbreaking19:49:55
@k900:0upti.meK900qmake on qt6 is something only terminally insane people use19:50:03
@makefu:fairydust.spacemakefuunfortunately nixpkgs is not yet in the position to dictate build systems20:01:20
@k900:0upti.meK900Fortunately20:01:42

There are no newer messages yet.


Back to Room ListRoom Version: 6