!UNVBThoJtlIiVwiDjU:nixos.org

Staging

311 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%3Aopen107 Servers

Load older messages


SenderMessageTime
20 Sep 2021
@qyliss:fairydust.spaceAlyssa Rosshttps://marc.info/?l=nix-dev&m=140361361202553&w=217:53:48
@superherointj:matrix.orgsuperherointj joined the room.18:21:19
@vcunat:matrix.orgVladimír ČunátThat's from time when there were only a handful of active contributors (and also users, presumably).18:29:06
21 Sep 2021
@sternenseemann:systemli.orgsterniis anyone aware of any reasons we may need to do a staging-next run in the coming time for 21.05? Seems quiet currently10:30:22
@sternenseemann:systemli.orgsterniI have some haskell changes with a small chance of breaking things lined up, so ideally there would be a staging-next run focused on that 10:31:14
@sternenseemann:systemli.orgsternisince usually the chance of haskell packages breaking in staging-next is very slim10:31:28
@sternenseemann:systemli.orgsterni * since usually the chance of haskell packages breaking in staging-next is very slim, so I don't want to impose that on anyone doing it for other changes ideally10:31:46
@vcunat:matrix.orgVladimír ČunátI'm not aware. I just see https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+base%3Astaging-21.05+is%3Aopen+11:02:23
@vcunat:matrix.orgVladimír ČunátIt sounds fine to me to do the pair about now. Hydra is relatively idle currently.11:02:44
@sternenseemann:systemli.orgsterniokay, then I'll try to finish up my PR later11:03:09
@sternenseemann:systemli.orgsternihow is the staging-next branch-off usually done? by merging staging into staging-next?13:05:31
@lukegb:zxcvbnm.ninjalukegb (he/him)Yeah. If you're lucky it becomes a fastforward13:17:58
@hexa:lossy.networkhexado we want to iterate further on the regressions on staging-next or merge?13:59:37
@lukegb:zxcvbnm.ninjalukegb (he/him)What regressions do we have left14:34:26
@hexa:lossy.networkhexahttps://shells.darmstadt.ccc.de/~hexa/1706497.html14:44:48
@hexa:lossy.networkhexahttps://hydra.nixos.org/eval/1706497?compare=trunk14:46:32
@hexa:lossy.networkhexa1739 jobs, 516 linux hardened failures14:48:34
@hexa:lossy.networkhexa
error: unused option: DEBUG_INFO_BTF
14:49:12
@vcunat:matrix.orgVladimír Čunát I'd prefer that trunk-combined evaluation gets fixed before the merge. 18:05:11
@vcunat:matrix.orgVladimír ČunátIt's been stuck for about three days now.18:05:39
@lukegb:zxcvbnm.ninjalukegb (he/him)Makes sense. I'll try and look at the Linux hardened breakages this evening if I can muster the will18:05:55
@sternenseemann:systemli.orgsterni Vladimír Čunát: wow what happened to it? 18:38:47
@vcunat:matrix.orgVladimír ČunátI don't know; I typically can't immediately see the problem in similar cases. This happens from time to time.18:39:38
@lukegb:zxcvbnm.ninjalukegb (he/him)yeah, it's the json error18:47:40
@lukegb:zxcvbnm.ninjalukegb (he/him)22004f7e8febc6ae6553c44ecd8bf9da9ddc5260 is the first bad commit20:18:32
@vcunat:matrix.orgVladimír Čunát Hmm, I don't get it yet. When I tried hydra-eval-jobs nixos/release-combined.nix -I . it also started to build during the evaluation at some point, so perhaps some IFD is there (as well?) 21:41:24
@lukegb:zxcvbnm.ninjalukegb (he/him)Hmm, I don't think I had any builds, although I also stopped paying attention22:42:09
@lukegb:zxcvbnm.ninjalukegb (he/him)changing the options.setuid default from "true" to "false" fixes it for reasons unknown23:31:12
22 Sep 2021
@j-k:matrix.orgj-k joined the room.15:49:55
@lukegb:zxcvbnm.ninjalukegb (he/him)Going to merge staging-next once this eval finished, unless it all goes horribly wrong; Linux hardened is now broken on master anyway (new kernel bump, hardened patchset hasn't updated yet), but I fixed the one(?) remaining working version ;)23:05:00

Show newer messages


Back to Room ListRoom Version: 6