!UNVBThoJtlIiVwiDjU:nixos.org

Staging

324 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%3Aopen110 Servers

Load older messages


SenderMessageTime
5 Oct 2021
@sandro:supersandro.deSandroI think reducing the merge PRs for release-staging is a good idea but not for normal staging. It will probably cause more merge conflicts.18:27:24
@hexa:lossy.networkhexaworking on it18:51:15
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/14066318:55:49
@trofi:matrix.orgtrofiCross-posting from "Nix* documentation" here as well as it directly touches staging: https://github.com/NixOS/nixpkgs/pull/138052 . WDYT? Does it match your understanding?20:23:50
6 Oct 2021
@rosariopulella:matrix.orgRosario Pulella changed their display name from rosariopulella to Rosuavio.10:38:31
@rosariopulella:matrix.orgRosario Pulella changed their display name from Rosuavio to Rosario Pulella.10:44:57
@hexa:lossy.networkhexaDid we remove darwin jobs on stable? https://hydra.nixos.org/job/nixpkgs/staging-next-21.05/unstable#tabs-constituents14:09:46
@hexa:lossy.networkhexa
[ "x86_64-linux" "aarch64-linux" /"x86_64-darwin"/ ]
14:11:15
@hexa:lossy.networkhexaapparently the jobset was modified to that end?14:11:27
@sternenseemann:systemli.orgsterniI thnik there's a separate jobset for darwin14:13:11
@sternenseemann:systemli.orgsterniah nvm that's an input in the hydra config isn't it14:13:47
@hexa:lossy.networkhexait is14:18:47
@vcunat:matrix.orgVladimír ČunátI think that was temporary due to darwin queue overload.14:24:13
@vcunat:matrix.orgVladimír Čunát * I suspect that was temporary due to darwin queue overload.14:24:28
@vcunat:matrix.orgVladimír Čunát... though that happens regularly.14:24:39
7 Oct 2021
@sternenseemann:systemli.orgsternieven… right now10:26:53
@sternenseemann:systemli.orgsternidarwin seems quite stuck10:26:57
@lukegb:zxcvbnm.ninjalukegb (he/him)hrm, python3 aiohttp seems broken in staging15:47:18
@lukegb:zxcvbnm.ninjalukegb (he/him)(and python3 argh)15:47:55
@sternenseemann:systemli.orgsterni lukegb (he/him): what is the python failure 15:49:46
@sternenseemann:systemli.orgsterni * lukegb (he/him): what is the python3 failure? 15:49:51
@lukegb:zxcvbnm.ninjalukegb (he/him) no, the package argh for python3 15:50:02
@lukegb:zxcvbnm.ninjalukegb (he/him)not "argh! python3 is broken"15:50:08
@sternenseemann:systemli.orgsterniah lol15:50:09
@lukegb:zxcvbnm.ninjalukegb (he/him)(I realise that was ambiguous)15:50:16
@sternenseemann:systemli.orgsterniso I haven't broken it :p15:50:26
@lukegb:zxcvbnm.ninjalukegb (he/him)argh is https://github.com/neithere/argh/issues/14815:51:16
@qyliss:fairydust.spaceAlyssa Rossargh16:24:30
@jonringer:matrix.orgjonringerstill curious why this broke between patch releases, first time I've seen such a failure16:27:49
@trofi:matrix.orgtrofiThe library seems to rely heavily on docstrings to do thing. I found it very fragile as those get discarded (yes?) when python bytecode is optimised.18:00:40

There are no newer messages yet.


Back to Room ListRoom Version: 6