!UNVBThoJtlIiVwiDjU:nixos.org

Staging

391 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%3Aopen127 Servers

Load older messages


SenderMessageTime
16 Sep 2021
@asbachb:matrix.orgasbachb Finally my bottles changes are in staging-next :D 18:44:21
17 Sep 2021
@vcunat:matrix.orgVladimír Čunát staging-next is contained in master now. 07:02:03
@hexa:lossy.networkhexa
In reply to @hexa:lossy.network
let's all remember that the next staging-next run is reserved for systemd 249
I missed that systemd was rebased and merged into staging
11:40:28
@lukegb:zxcvbnm.ninjalukegb (he/him)so... does that me we can start the next staging-next cycle?11:56:20
@hexa:lossy.networkhexaI believe so.12:12:13
@hexa:lossy.networkhexawould you like to?12:12:18
@lukegb:zxcvbnm.ninjalukegb (he/him) What's the process? Merge staging into staging-next and open a PR? 12:15:09
@lukegb:zxcvbnm.ninjalukegb (he/him)Oh, it's just a FF anyway12:15:41
@lukegb:zxcvbnm.ninjalukegb (he/him)or not12:19:14
@hexa:lossy.networkhexayep12:20:43
@lukegb:zxcvbnm.ninjalukegb (he/him)Oh, I should've merged the opencv fix into staging first12:20:52
@lukegb:zxcvbnm.ninjalukegb (he/him)(https://github.com/NixOS/nixpkgs/pull/138237)12:21:12
@hexa:lossy.networkhexai guess you still can12:21:23
@lukegb:zxcvbnm.ninjalukegb (he/him)it's always fun seeing whatever random package stdenv rebuild steps actually end up attributed to19:16:06
@lukegb:zxcvbnm.ninjalukegb (he/him)this week, it's ssb-patchwork (for x86_64-linux) https://hydra.nixos.org/build/15341709819:16:17
20 Sep 2021
@hexa:lossy.networkhexathis staging-next run is really uneventful, we need more like these :)12:32:45
@vcunat:matrix.orgVladimír ČunátYes, though I can still see a couple thousand build regressions: https://hydra.nixos.org/eval/1706256?compare=trunk13:02:23
@trofi:matrix.orgtrofi nix-review-tools says at least on linux most failures are around qtwayland and hardened_kernel. 13:24:16
@hexa:lossy.networkhexahttps://shells.darmstadt.ccc.de/~hexa/1706256.html16:30:40
@hexa:lossy.networkhexaI'm going to take a look at the python stuff when I come back from the supermarket16:31:12
@vcunat:matrix.orgVladimír ČunátMost of regressions seem to be darwin and linux-hardened.16:47:52
@hexa:lossy.networkhexaIn beautifulsoup4 it complains about not knowing is8859-15 and windows-cp125217:19:40
@hexa:lossy.networkhexathe failing sphinx job I can't find17:19:50
@hexa:lossy.networkhexapytest-timeout … decided to disable two failing tests, because of the value of unblocking 700 more jobs https://github.com/NixOS/nixpkgs/pull/13872617:20:10
@nickhu:matrix.orgNick Hu joined the room.17:22:26
@qyliss:fairydust.spaceAlyssa Ross joined the room.17:26:39
@nickhu:matrix.orgNick Hu I just merged a version update of gdb 10 -> 11; I have tested the binaries myself, and I think it should be fairly non-contentious. The reason it's in staging is mass rebuilds, but I can't see this having a huge knock-on effect on its reverse-dependencies. What's the process for stabilization? 17:26:47
@qyliss:fairydust.spaceAlyssa Rossnickhu: every so often a version of staging becomes the new staging-next. After that, staging next is worked on for a while to fix any regressions, and let a full Hydra build complete, and then it's merged into master and the cycle begins again.17:29:10
@qyliss:fairydust.spaceAlyssa RossSo in a few weeks, your gdb update will land in master after going through this process 17:29:39
@qyliss:fairydust.spaceAlyssa Ross Staging is not a place to get extra testing for a package, or to try something out. Its purpose is to group mass rebuilds together. 17:30:07

Show newer messages


Back to Room ListRoom Version: 6