!UNVBThoJtlIiVwiDjU:nixos.org

Staging

191 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-24.05 | Review Reports: https://malob.github.io/nix-review-tools-reports/73 Servers

Load older messages


SenderMessageTime
28 Jun 2021
@thom:uint.onetomcur joined the room.19:45:28
@thom:uint.onetomcur changed their display name from Thom to tomcur.19:45:46
@sandro:supersandro.deSandro joined the room.20:41:07
@ryantm:matrix.orgryantm joined the room.21:15:49
@server_stats:nordgedanken.devServer Stats Discoverer (traveler bot) joined the room.23:07:42
30 Jun 2021
@0x4a6f:matrix.org[0x4A6F] joined the room.06:13:14
5 Jul 2021
@spacesbot:nixos.devspacesbot - keeps a log of public NixOS channels joined the room.19:20:24
@hexa:lossy.networkhexastaging-next was merged 10m ago19:34:53
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/129360 should go in before the next staging-next runs19:35:26
@hexa:lossy.networkhexa * https://github.com/NixOS/nixpkgs/pull/129360 should go in before the next staging-next runs, talking to you jonringer :P 19:41:03
@jonringer:matrix.orgjonringersounds good to me19:41:21
@jonringer:matrix.orgjonringerI don't have my server up and running currently19:41:34
@spacesbot:nixos.devspacesbot - keeps a log of public NixOS channels 19:49:36
@hexa:lossy.networkhexaFrom the python-unstable branch we have a fixup commit that should've been squashed. Can/should we still squash that on staging, or is that too late?21:16:02
@hexa:lossy.networkhexaRedacted or Malformed Event21:16:32
@hexa:lossy.networkhexa
a2c9f048495 fixup! python3: 3.8 -> 3.9
21:16:51
@vcunat:matrix.orgVladimír Čunát I suspect that staging is better kept fast-forward. 21:28:29
@hexa:lossy.networkhexayeah, I somewhat feel the same, it's no biggie21:30:37
@jonringer:matrix.orgjonringer I don't think it's a major issue. If it was just named doc/python: update python3 references then it would have been fine 21:52:50
6 Jul 2021
@hexa:lossy.networkhexaanother library update incoming, libexr. will be ready in an hour or so.14:26:33
@hexa:lossy.networkhexahydra seems somewhat idle, hovering around 20k darwin builds, so we could start another staging-next run14:26:51
@hexa:lossy.networkhexaI assume you killed the glibc job eval?14:27:08
@vcunat:matrix.orgVladimír ČunátYes, I just canceled the glibc-2.33 jobset and merged it into staging.14:27:13
@hexa:lossy.networkhexagreat14:27:26
@hexa:lossy.networkhexa * another library security update incoming, libexr. will be ready in an hour or so.14:27:58
@vcunat:matrix.orgVladimír Čunát OK, I assume we'll wait for libexr and then immediately go for the next staging-next. 14:31:24
@hexa:lossy.networkhexaRedacted or Malformed Event14:32:06
@hexa:lossy.networkhexa * another library security update incoming, openexr. will be ready in an hour or so.14:32:52
@hexa:lossy.networkhexahttps://github.com/AcademySoftwareFoundation/openexr/commit/6442fb71a86c09fb0a8118b6dbd93bcec4883a3c doesn't apply any more, seeing as it wasn't upstreamed 😞16:12:12
@hexa:lossy.networkhexaI don't understand enough of cmake to update openexr it seems16:18:06

Show newer messages


Back to Room ListRoom Version: 6